Hey everyone, quick question about the `Navigo` ro...

# kvision

[sigmadelta]

Hey everyone, quick question about the Navigo routing for KVision. I’m currently trying to use the Navigo module to set up the routing withing my fullstack application, and whilst the “old” hash-based method works, I would prefer it to be without the hash and simple something in the odds of localhost:16097/login instead of localhost:16097/#/login for example.

The problem is however that I can’t seem to get it working without the hash-system at all. As soon as I try to turn it off, the pages aren’t found anymore and I’m greeted with a 404. I’ve noticed that the example applications all use the hash-based approach as well: https://github.com/rjaros/kvision-realworld-example-app-fullstack/blob/master/src/frontendMain/kotlin/io/realworld/ConduitManager.kt#L22

Is the History API based method not compatible with KVision or are there additional settings or setups required?

[Robert Jaros]

Please check this thread:
https://kotlinlang.slack.com/archives/CL4C1SLKC/p1662321374232579

[sigmadelta]

Worked like a charm, thanks @Robert Jaros!

[sigmadelta]

For future reference or anyone needing help with this issue, the core thing to do is:

• Add config.devServer.historyApiFallback = true to webpack.config.d/webpack.js
• Remove all # from your links if you used the legacy “hash” navigation method beforehand