Question 1

How do I enable HTTPS with Denoliver?

Accepted Answer

You need to generate self-signed certificates using external tools like the provided bash script, then specify files with --certFile and --keyFile flags or in denoliver.json. It doesn't auto-generate certs, adding manual steps.

Question 2

Can I use Denoliver with TypeScript projects?

Accepted Answer

Yes, Denoliver itself is written in TypeScript and can serve .ts files, but it won't compile them; you'll rely on Deno's native TypeScript support for execution, and interceptors support TypeScript functions.

Question 3

Denoliver vs servor or other static servers: which is better?

Accepted Answer

Denoliver is optimized for Deno with zero dependencies and modern APIs, while servor works across runtimes but may have fewer Deno-specific features. Choose Denoliver for pure Deno dev, servor for cross-runtime flexibility.

Question 4

How to add custom request interceptors in Denoliver?

Accepted Answer

Create a before.ts or after.ts file exporting functions that modify the Request object, then use --before or --after CLI flags or configure in denoliver.json. Interceptors must return the request, allowing logic injection.

Question 5

Is Denoliver good for deploying static sites?

Accepted Answer

No, it's intended for development only; the disclaimer warns against production use. For deployment, consider Deno Deploy or other hosting services with security and scalability features.

Question 6

What permissions does Denoliver require and why?

Accepted Answer

It needs --allow-net for serving, --allow-read for file access, --allow-write for boilerplating, and --allow-run for live reload. These are standard Deno security flags, but the list can be verbose for new users.

denoliver

What is denoliver?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions