Question 1

How do I set up cyclic-router with switch-path in my Cycle.js app?

Accepted Answer

Install cyclic-router, @cycle/history, and switch-path via npm, then wrap your main function with routerify and configure the history driver. The README provides a basic usage example with code snippets for integration.

Question 2

What's the difference between cyclic-router and using @cycle/history directly?

Accepted Answer

Cyclic-router builds on @cycle/history by adding a routerify wrapper for higher-level routing abstraction, including route matching and component injection, while @cycle/history alone offers raw history driver functionality without these conveniences.

Question 3

Can cyclic-router handle nested or parameterized routes?

Accepted Answer

Yes, through the injected route matcher like switch-path, which supports nested patterns and parameter extraction. Parameters can be passed to components via sources, as demonstrated in the route parameters section.

Question 4

How do I programmatically navigate or change routes in cyclic-router?

Accepted Answer

Emit actions in the router sink, such as paths or history commands like goBack, using xstream merges. The dynamic routing example in the README shows how to map DOM events to these actions.

Question 5

Is cyclic-router compatible with TypeScript or server-side rendering?

Accepted Answer

TypeScript is supported with @types/history installation, but server-side rendering isn't addressed in the README, likely limiting it to client-side SPAs within the Cycle.js context.

Question 6

How to migrate from cyclic-router V4 to V5?

Accepted Answer

V5 shifts from a driver to a wrapper approach; consult the old README for V4 and refactor code to use routerify instead, updating driver interactions and route handling accordingly.

cyclic-router

What is cyclic-router?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions