Why Fresh is Deno's official web framework

Introduction

Fresh is Deno's official web framework because it makes building fast and simple web apps easy without extra setup. It uses modern JavaScript and Deno features to give you a smooth developer experience.

You want to build a web app quickly with minimal configuration.

You want to use Deno's latest features like TypeScript support and native ES modules.

You want a framework that renders pages fast with no client-side JavaScript by default.

You want to build server-rendered apps that load instantly and are SEO-friendly.

You want to avoid complex build steps and bundlers.

Syntax

Deno

import { serve } from "fresh/server.ts";

serve(async (req) => {
  return new Response("Hello from Fresh!");
});

Fresh uses Deno's native ES module system, so you import directly from URLs or local files.

The serve function starts a web server that handles requests simply.

Examples

A minimal Fresh server that responds with a welcome message.

Deno

import { serve } from "fresh/server.ts";

serve(() => new Response("Welcome to Fresh!"));

Fresh server with simple routing based on URL path.

Deno

import { serve } from "fresh/server.ts";

serve(async (req) => {
  const url = new URL(req.url);
  if (url.pathname === "/") {
    return new Response("Home page");
  }
  return new Response("Not found", { status: 404 });
});

Sample Program

This program starts a Fresh server that responds with "Hello from Fresh!" to every request.

Deno

import { serve } from "fresh/server.ts";

serve(() => new Response("Hello from Fresh!"));

Important Notes

Fresh uses server-side rendering by default, so pages load fast and work well for SEO.

It avoids client-side JavaScript unless you add it explicitly, keeping apps lightweight.

Fresh integrates tightly with Deno, so you get fast startup and native TypeScript support.

Summary

Fresh is Deno's official web framework for building fast, simple web apps.

It uses modern Deno features and server-side rendering for speed and ease.

Fresh apps need little setup and avoid heavy client-side code by default.

Practice

1. What is the main reason Fresh is Deno's official web framework?

easy

A. It uses modern Deno features and server-side rendering for speed.

B. It requires heavy client-side JavaScript for interactivity.

C. It is designed only for mobile app development.

D. It depends on third-party Node.js packages.

Solution

1. Step 1: Understand Fresh's design goals

   Fresh focuses on speed and simplicity by using Deno's modern features and server-side rendering.

2. Step 2: Compare options with Fresh's characteristics

   Options B, C, and D contradict Fresh's lightweight and server-side approach.

3. Final Answer:

   It uses modern Deno features and server-side rendering for speed. -> Option A

4. Quick Check:

   Fresh = modern Deno + server-side rendering [OK]

Hint: Fresh is fast because it uses server-side rendering [OK]

Common Mistakes:

• Thinking Fresh needs heavy client-side code
• Confusing Fresh with mobile-only frameworks
• Assuming Fresh depends on Node.js packages

2. Which of the following is the correct way to create a new Fresh project using Deno?

easy

A. deno run -A https://fresh.deno.dev/init my-app

B. deno create fresh my-app

C. fresh new my-app

D. deno fresh init my-app

Solution

1. Step 1: Recall Fresh's official project creation command

   Fresh projects are created by running a Deno script from fresh.deno.dev with permissions.

2. Step 2: Match the command syntax

   deno run -A https://fresh.deno.dev/init my-app matches the official command format: deno run -A https://fresh.deno.dev/init my-app.

3. Final Answer:

   deno run -A https://fresh.deno.dev/init my-app -> Option A

4. Quick Check:

   Fresh project init uses deno run -A URL [OK]

Hint: Fresh uses deno run -A with fresh.deno.dev URL [OK]

Common Mistakes:

• Using 'deno create' which doesn't exist
• Trying 'fresh new' without installing Fresh CLI
• Assuming 'deno fresh init' is valid

3. Given this Fresh component code snippet, what will be rendered in the browser?

export default function Home() {
  return (
    <main>
      <h1>Welcome to Fresh</h1>
      <p>Fast and simple web apps</p>
    </main>
  );
}

medium

A. A syntax error preventing rendering

B. An empty page with no content

C. Only the <h1> tag content is shown

D. <main><h1>Welcome to Fresh</h1><p>Fast and simple web apps</p></main>

Solution

1. Step 1: Understand Fresh component rendering

   Fresh components return JSX-like HTML elements that render as HTML in the browser.

2. Step 2: Analyze the returned JSX

   The component returns a <main> element containing <h1> and <p> tags with text content.

3. Final Answer:

   <main><h1>Welcome to Fresh</h1><p>Fast and simple web apps</p></main> -> Option D

4. Quick Check:

   JSX returns full HTML structure [OK]

Hint: Fresh renders returned JSX as HTML in browser [OK]

Common Mistakes:

• Expecting no output or empty page
• Thinking JSX causes syntax errors in Fresh
• Assuming partial rendering of tags

4. Identify the error in this Fresh route handler code:

export const handler = {
  GET(req) {
    return new Response('Hello from Fresh!');
  }
};

medium

A. The handler should be a default export, not a named export.

B. The GET method should return a JSON object, not a Response.

C. The handler object must use async functions for HTTP methods.

D. The Response constructor is missing a status code.

Solution

1. Step 1: Review Fresh handler method requirements

   Fresh expects HTTP method handlers like GET to be async functions returning a Response.

2. Step 2: Check the GET method definition

   The GET method is synchronous here, missing async keyword, which can cause issues.

3. Final Answer:

   The handler object must use async functions for HTTP methods. -> Option C

4. Quick Check:

   Fresh handlers = async functions [OK]

Hint: Fresh HTTP handlers must be async functions [OK]

Common Mistakes:

• Omitting async keyword in handler methods
• Returning plain strings instead of Response
• Confusing default and named exports

5. You want to build a Fresh app that loads data from an API on the server and renders it without client-side JavaScript. Which Fresh feature helps achieve this efficiently?

hard

A. Using client-side React components for all UI

B. Server-side rendering with Islands architecture

C. Adding heavy client-side state management libraries

D. Disabling server rendering to speed up load

Solution

1. Step 1: Understand Fresh's Islands architecture

   Fresh uses Islands architecture to render most UI on the server and hydrate only small interactive parts on the client.

2. Step 2: Match the requirement to Fresh features

   Server-side rendering with Islands allows loading data on server and minimal client JS, fitting the requirement.

3. Final Answer:

   Server-side rendering with Islands architecture -> Option B

4. Quick Check:

   Fresh Islands = server render + minimal client JS [OK]

Hint: Use Islands for server data and minimal client JS [OK]

Common Mistakes:

• Thinking all UI must be client-side React
• Adding heavy client-side libraries unnecessarily
• Disabling server rendering which slows load