Question 1

Should I use preact-router or preact-iso for a new Preact project?

Accepted Answer

The README recommends preact-iso for new projects because it's actively maintained and offers better integration with Suspense and lazy loading. preact-router is stable but deprecated, so it's better for legacy applications.

Question 2

How do I implement lazy loading with preact-router?

Accepted Answer

Lazy loading isn't built-in; you need to use the preact-async-route module. Import AsyncRoute and use it in your Router with a getComponent function that returns a promise from dynamic imports, as shown in the lazy loading example.

Question 3

Does preact-router support server-side rendering?

Accepted Answer

No, preact-router is designed for client-side routing only. For server-side rendering, consider alternatives like preact-iso or other solutions that integrate with Preact's SSR capabilities, as it lacks built-in SSR support.

Question 4

How can I handle 404 pages in preact-router?

Accepted Answer

Use a component with the `default` prop in the Router to catch unmatched routes. For example, add a component like <NotFound default /> to render a 404 page when no other routes match, as implied in the handling URLs section.

Question 5

What are the main limitations of preact-router?

Accepted Answer

Key limitations include its deprecated status, lack of advanced features like built-in lazy loading, and simplicity that may not scale for complex applications with nested routing or view composition needs.

Question 6

How to redirect programmatically in preact-router?

Accepted Answer

Use the `route()` function provided by the library. Call `route('/new-path')` to navigate and push a history entry, or `route('/path', true)` to replace the current entry, as detailed in the programmatic navigation section.

Preact Router

What is Preact Router?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions