[BUG] `/example.com/` does not resolve to `/example.com/index.html` in development.

Bug Report Quick Checklist

• I am on the latest version of Snowpack & all plugins.
• I use package manager 7.15.0
• I run Snowpack on macOS 10.15.7
• I run Snowpack on node v16.2.0

Describe the bug

localhost:8080/example.com/ does not resolve localhost:8080/example.com/index.html in development. The presence of .com in the folder seems to trigger a heuristic for file extensions:

[18:19:57] [snowpack] Error: /Users/lgarron/Code/git/github.com/lgarron/snowpack-url-folders/public/example.com/index.html - Requested content ".com" but only built .html
[18:19:57] [snowpack] [500] /example.com/

To Reproduce

https://github.com/lgarron/snowpack-url-folders has a repro with two folders that each contain a simple index.html:

• public/example/
• public/example.com/

Repro steps:

git clone https://github.com/lgarron/snowpack-url-folders && cd snowpack-url-folders
npm install

npx snowpack dev

# This works
open http://localhost:8080/example/
# This doesn't work:
open http://localhost:8080/example.com/

Expected behavior

Whether a path resolves a folder to its index.html does not depend on whether any containing folders contain a period.

Anything else?

This comes about in practice because we have source/demo code for multiple sites in the same project, and the folders for those demos contain the domains for those sites:

https://experiments.cubing.net/cubing.js/twizzle.net/ https://experiments.cubing.net/cubing.js/alg.cubing.net/

[lgarron]

Anyways, give snowpack@next a try if you’d like to try the fix.

🥳😍

Thanks, that seems to work perfectly! My current work involves such a folder, and it’s delightful to see it load directly. 😊

[lgarron]

Bugfix here: #3509

Thanks! I just tried it out. 😄

Good news: This seems to serve the correct body content.

Sad news: The content is served with application/octet-stream, which prevents the page from being loaded in a browser and triggers a download instead. 😦