Worker-Deno Project Setup
Configure a project that combines Deno for local development and Cloudflare Workers for deployment.
Worker-Deno Project Setup is a free Edge Computing with Cloudflare Workers & Deno lesson on CoddyKit — lesson 2 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the Edge Computing with Cloudflare Workers & Deno learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.
Deno & Workers: Best of Both
Welcome! In this lesson, we'll learn how to set up a project that uses Deno for local development and Cloudflare Workers for deployment to the edge.
This powerful combination lets you leverage the best features of both platforms.
Why Combine Deno & Workers?
Deno offers a fantastic local developer experience with its built-in tools for formatting, linting, and testing. Cloudflare Workers, on the other hand, provide a serverless platform to deploy your code globally, close to your users.
A combined setup allows you to:
- Develop and test locally with Deno's robust tooling.
- Deploy your application to Cloudflare's low-latency edge network.
- Reuse core application logic across both environments.
Organizing Your Hybrid Project
A typical project structure for Deno and Workers involves separating entry points while sharing core logic. Here's a common layout:
src/: Contains your shared Deno-compatible logic.worker-entry.ts: The main entry point for your Cloudflare Worker.deno-local.ts: A script to run your application locally using Deno.wrangler.toml: Cloudflare Worker configuration file.
This keeps things tidy and manageable.
Cloudflare Worker Setup
We'll assume you have the Wrangler CLI installed and configured from previous lessons. This tool is essential for developing and deploying Cloudflare Workers.
Your wrangler.toml file will define how your Worker builds and deploys. For Deno projects, it often points to a bundled JavaScript output file.
Basic Deno Project Init
For local Deno development, you simply create your .ts or .js files. Deno doesn't require a package.json or a node_modules folder like Node.js.
You can also use a deno.json file to configure project-specific settings, like tasks, formatting rules, and imports.
Writing Reusable Code
The key to a successful hybrid project is writing core application logic that can run in both Deno and Worker environments.
- Use standard Web APIs (e.g.,
Request,Response,URL). - Avoid Node.js-specific APIs.
- Place this shared logic in a common directory, like
src/.
This ensures your code works seamlessly in both contexts.
Deno Local Server Example
Here's how you might set up a basic Deno server to run your shared logic locally. This allows for quick testing and iteration without deploying to the edge.
import { serve } from "https://deno.land/std/http/server.ts";
// This function would typically be imported from a shared 'src/' file.
function handleLocalRequest(request: Request): Response {
const url = new URL(request.url);
if (url.pathname === "/local-greet") {
return new Response("Hello from Deno local server!", { status: 200 });
}
return new Response("Not Found", { status: 404 });
}
console.log("Deno server running on http://localhost:8000/");
serve(handleLocalRequest, { port: 8000 });
Cloudflare Worker Entry Point
Your Cloudflare Worker's entry point (e.g., worker-entry.ts) will import and use the same shared logic. Wrangler will then bundle this Deno-compatible code into a single JavaScript file for deployment.
export default {
async fetch(request: Request): Promise<Response> {
const url = new URL(request.url);
// Imagine importing and using a shared function here
// import { handleRequest } from './src/handler.ts';
// return handleRequest(request);
// For this example, we'll use a simplified inline logic
if (url.pathname === "/edge-greet") {
return new Response("Hello from Cloudflare Worker!", { status: 200 });
}
return new Response("Not Found", { status: 404 });
},
};
Bundling Deno for Workers
Cloudflare Workers execute standard JavaScript. Since Deno often uses TypeScript and a URL-based module system, your Deno code needs to be transpiled (converted to JavaScript) and bundled into a single file.
Wrangler handles this process automatically if configured correctly, often using tools like esbuild internally. This ensures your Deno logic runs efficiently at the edge.
Project Setup Check
When setting up a project to use Deno for local development and Cloudflare Workers for deployment, what is a primary benefit of this hybrid approach?
Project Setup Recap
In this lesson, we explored how to structure a project that utilizes Deno for local development and Cloudflare Workers for edge deployment. We discussed the benefits of this approach, how to organize shared code, and saw examples of Deno local server and Worker entry points.
Next, we'll dive into implementing shared utility functions and business logic that can be reused across both environments.
Frequently asked questions
Is the “Worker-Deno Project Setup” lesson free?
Yes — the full text of “Worker-Deno Project Setup” is free to read here on the web, and the Edge Computing with Cloudflare Workers & Deno course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the Edge Computing with Cloudflare Workers & Deno course, upgrade to CoddyKit PRO.
What will I learn in “Worker-Deno Project Setup”?
Configure a project that combines Deno for local development and Cloudflare Workers for deployment. You practise Edge Computing with Cloudflare Workers & Deno with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.
Do I need any experience to start Edge Computing with Cloudflare Workers & Deno?
No prior experience is required. Edge Computing with Cloudflare Workers & Deno on CoddyKit is structured for beginners through advanced learners; this is — lesson 2 of 4, so you can start here or from the beginning and move at your own pace.
How long does the “Worker-Deno Project Setup” lesson take?
Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.
Can I write and run code in this Edge Computing with Cloudflare Workers & Deno lesson?
Yes. Every Edge Computing with Cloudflare Workers & Deno lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.
All lessons in this course
- Deno on Cloudflare Workers
- Worker-Deno Project Setup
- Shared Logic & Utilities
- Deploying & Debugging the Integrated Stack