Question 1

How to configure custom redirects with serve?

Accepted Answer

Create a serve.json file in your public folder and use the 'redirects' option from serve-handler documentation to define path-based redirects, allowing flexible routing for SPAs or static sites.

Question 2

Serve vs http-server: which is better for local development?

Accepted Answer

Serve offers a prettier directory UI and simpler zero-config setup, while http-server is more minimal and faster for basic serving. Choose Serve for enhanced visuals and ease, http-server for lightweight needs.

Question 3

Can serve handle single-page application routing properly?

Accepted Answer

Yes, by configuring 'rewrites' in serve.json to redirect all requests to index.html, enabling client-side routing. This leverages serve-handler's options for SPA support as mentioned in the configuration section.

Question 4

How to change the port when using serve?

Accepted Answer

Use the -p or --port flag when running the command, e.g., 'serve -p 8080' to serve on port 8080. This is listed in the help options available via 'serve --help'.

Question 5

Is serve suitable for serving files over HTTPS?

Accepted Answer

No, serve does not natively support HTTPS; you need to set up a reverse proxy or use serve-handler in a custom Node.js server with HTTPS configuration, which adds complexity for secure local testing.

Question 6

What are good alternatives to serve for static file serving?

Accepted Answer

Alternatives include http-server for minimalism, Python's SimpleHTTPServer for no-Node environments, and Vercel or Netlify for production-ready static hosting with more features like CDN integration.

serve

What is serve?

Overview

Use Cases

Best For

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions