browser is now downloading files in dev instead of showing them

[cekvenich2]

I updated to latest version and... the browser is now downloading the files instead of showing them. I am using pug plugin in but that used to work. HELP?

[cekvenich2]

It works w/ 3.7.0. Problem is that I have people using snowpack with npx that loads latest version.

[bdunklau]

me too, I have the same bug

[cekvenich2]

Build works, but not dev, must be a mime issue.

[jacty]

Could you be more specific on which kind of files have been downloaded, plz?

[sanmai-NL]

I have the same problem.

*   Trying 127.0.0.1:8080...
* Connected to localhost (127.0.0.1) port 8080 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*  CAfile: /etc/ssl/certs/ca-certificates.crt
*  CApath: none
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
...
*  SSL certificate verify result: unable to get local issuer certificate (20), continuing anyway.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Using Stream ID: 1 (easy handle 0x7f8c47a29a90)
> HEAD / HTTP/2
> Host: localhost:8080
> user-agent: curl/7.77.0
> accept: */*
> 
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 4294967295)!
< HTTP/2 200 
HTTP/2 200 
< accept-ranges: bytes
accept-ranges: bytes
< access-control-allow-origin: *
access-control-allow-origin: *
< content-type: application/octet-stream
content-type: application/octet-stream
< etag: W/"4ba0-HVBjD4+jieT7uDQj1MgPw4ksr6I"
etag: W/"4ba0-HVBjD4+jieT7uDQj1MgPw4ksr6I"
< vary: Accept-Encoding
vary: Accept-Encoding
< date: Thu, 15 Jul 2021 10:42:00 GMT
date: Thu, 15 Jul 2021 10:42:00 GMT

< 
* Connection #0 to host localhost left intact

The content-type header is set wrong for this /index.html path.

[cekvenich2]

[cekvenich2]

Nope, not fixed: #3577

[cekvenich2]

bump?

[cekvenich2]

OK, I found the where the problem is in the snowpack source code. It is in:
In dev.ts - req: http.IncomingMessage

Workaround is to use build with watch: true.

Back to the issue in dev.ts req:
When you say /path/index.html it works.
But that is a dirty link. The links are /path1 or /path2 w/o index.html!
When you build it works. When you dev it download /path1 or /path2 since it defaults to octet mime.
It needs if(!req.path.includes('.')) {
res.setHeader('content-type', res.type('html')) // => 'text/html'

Since if there is not '.' it must be index.html!!!!!
I'm not sure what area of dev.ts to fix to check to see if there is no extension to set it to text/html.

[cekvenich2]

#3687

Until PR is published you can: npm i -g snowpack4

[joyfuI]

thank you. I had the same problem, but solved it by using snowpack4 instead.