Subfolders with pika CDN about snowpack HOT 4 CLOSED

Also htm/preact from @developit

from snowpack.

This is a great question that I'm thinking through now myself. There's no agreed upon path forward yet, but from talking to different people I'm starting to see some rough alignment forming around:

• Create React App and others are now compiling node_modules, so package authors are starting to feel comfortable publishing latest ES2019 spec at the "module" entrypoint. Package consumers can then compile as needed.
• Importing from within packages by file name (import x from "pkg/lib/some/path/to/file.js";) works in some scenarios but not all, especially when a package has multiple distributions ("main", "module", etc.) Not to mention, files can move around packages internally without being considered a breaking change by authors.
• What @developit has started doing, which I tend to like, is using nested packages. So:
  • preact is a folder with a package.json manifest
  • preact contains a ./hooks sub-folder with it's own package.json manifest
  • import via preact/hooks, and you can still allow the bundler/Node to resolve to the correct file.

This feels more friendly to my personally but is also great the CDN, because it means that tooling gets an explicit idea of what a packages entrypoints are (all non-test sub-folders with a package.json manifest). A problem with "any file is potentially an entrypoint" is that it would be impossible for the CDN to support this reliably, since we try to bundle packages into as few files as possible.

/cc @developit @MylesBorins

from snowpack.

is it possible that the pika cdn could generate bundles for any .js file as an entrypoint?

from snowpack.

🚚 This feature request has been moved!
Continue the discussion on our new message board:
https://www.pika.dev/packages/@pika/web/discuss/1091

🆕 Pika Discuss: A Q&A discussion board for your JavaScript packages

from snowpack.