Difference of behaviour between serve and http-server

[eric-burel]

Hi, we have noticed some discrepancies between serve and http-server when opening a Storybook static export.
Issue is described here: storybookjs/storybook#10933

To sum it up, with http-server the first story opens correctly, but not with serve, which seems a bit less reliable for yet unknown reasons.

While you should get this (this is the result with http-server):

It sounds like a failing redirection but I have no log message.

I have a reproduction, but not minimal, in Vulcan Next. That may still help to debug.

git clone https://github.com/VulcanJS/vulcan-next.git
cd vulcan-next
yarn
yarn build:storybook
serve storybook-static # this will mostly work but not reliably, while http-server will work ok

[theKashey]

serve needs at least cleanUrl:false option

[eric-burel]

cleanUrls seems to break everything for me:

[eric-burel]

See vercel/next.js#18775 for a reproducible minimal example

[baptisteArno]

Any update on this @eric-burel? We can't use http-server because it doesn't compress files.

I can't think of other solutions 🤔

[eric-burel]

Haven't checked in a while! Do you still have this issue? You'll probably want to access the right URL directly, maybe smth like "/index.html".

[baptisteArno]

Yep, problem still exists! We ended up using static-web-server.

[Wxh16144]

I'm curious what the difference is between serve and https-server🤔

[bchewy]

can be resolved with

serve.json

{
    "cleanUrls": false
    ,
    "rewrites": [
        { "source": "/", "destination": "/index.html" }
    ]
}