Http-server: wasm does not need charset and does not work on firefox chrome
https://www.youtube.com/watch?v=n6hIa-fPx0M&t=618s
whole google episode about your server :)
frank-dspeed
All 7 comments
Huh, that's pretty cool. Thanks for linking that, it definitely shouldn't have charset!
thornjad
on 6 Apr 2020
@thornjad in general every binary file does not have a charset. charset is for text file formats.
frank-dspeed
on 6 Apr 2020
Finally had some time to investigate this, and this is actually coming from a dependency, ecstatic. I'm currently working on removing that dependency, and will be able to fix this after that.
thornjad
on 27 Apr 2020
@thornjad you should consider express static as a replacement that is maintained.
frank-dspeed
on 28 Apr 2020
I've switched to local-web-server as a workaround for now.
npm i local-web-server --global
ws
RobLoach
on 24 May 2020
@RobLoach
https://open-wc.org/developing/es-dev-server.html
npm i --save-dev es-dev-server
for people (like me) looking for a drop in replacement for this that serves wasm files correctly, but also handles extensions nicely (as this does), npx serve is a fine replacement, as is npx local-web-server (theres a commandline option for setting default extension). these both fit all the needs I had for http-server, before I started needing to serve wasm, and they seem to serve wasm files with the correct content type.
es-dev-server will give a 404 if you omit the .html in file names (which differs from http-server and there does not appear to be a commandline arg to change it) and is also very slow. I don't know what it's doing but it takes a solid several seconds to quit after a ctrl-c (or multiple) and is just generally slow to use.
phi-fell
on 17 Sep 2020
Related issues
dKab
路
7Comments
rgladwell
路
7Comments
jondlm
路
6Comments
arthurkhlghatyan
路
3Comments
daGaiGuanYu
路
5Comments
Most helpful comment
for people (like me) looking for a drop in replacement for this that serves wasm files correctly, but also handles extensions nicely (as this does),
npx serveis a fine replacement, as isnpx local-web-server(theres a commandline option for setting default extension). these both fit all the needs I had forhttp-server, before I started needing to serve wasm, and they seem to serve wasm files with the correct content type.es-dev-serverwill give a 404 if you omit the.htmlin file names (which differs from http-server and there does not appear to be a commandline arg to change it) and is also very slow. I don't know what it's doing but it takes a solid several seconds to quit after a ctrl-c (or multiple) and is just generally slow to use.