Router usage

Hi guys! I’m loving this framework, many compliments!

Unfortunately at the moment I’m experiencing a strange problem, I cannot make the router work. This is my code:

'use strict'

const choo = require('choo')
const html = require('choo/html')

const view1 = (state, prev, send) => {
  return html`<h1>Hello!</h1>`
}

const view2 = (state, prev, send) => {
  return html`<h1>World!</h1>`
}

const app = choo()
app.router([
  ['/', view1],
  ['/world', view2]
])

const tree = app.start()
document.body.appendChild(tree)

If I go into the brawser at the url everything is ok, If I go to url/world I get a 404. Even if I set a default route (I tried both budo and bankai to compile the code). Probably I’m lost in a glass of water, can you help me? Thanks!

[josephluck]

@delvedor - this isn’t a choo specific issue, but an issue for single page apps in general. http://jaketrent.com/post/pushstate-webpack-dev-server/ there’s a good article explaining how to use webpack dev server.

Personally I’ve found budo --pushstate more than adequate during dev, and a simple express server catching all routes to serve index.html for production.

[JRJurman]

Using budo, I was able to get it to work by passing in the option --pushstate. This causes budo to always serve index.html (and not 404). I don’t know if there’s a way for choo to expose the routes to budo, but what I’ve done in the past is have my build scripts build an index.html at each route (e.g. /index.html, /hello/index.html, /world/index.html)

I’ve run into this issue in React as well, not sure if this is the best solution, but meh, it works.