Export Map Support (#539)
Snowpack now supports export maps! As of Node v12 (LTS) package authors have the chance to define an explicit set of file entrypoints inside of their package. Snowpack will now respect these export maps, and warn if you try to import a file outside of them. `import 'preact/some-private-package-file.js' will now throw an error to match Node.js behavior.
See Node's official documentation for more: https://nodejs.org/api/esm.html#esm_package_entry_points
Optimized Build Dependencies (#526)
As a part of your production build, Snowpack now scans your build output to optimize your dependencies. Previously, Snowpack would tree-shake by scanning your source code, which gave less accurate results. This new feature gives you an even better-optimized tree-shaking result, and fixes issues where your build pipeline actually adds/removes imports.
Other Features & Fixes
- @snowpack/plugin-webpack v1.4.0 released with logging and polyfill improvements.
- Enable livereload when HMR is not supported for the file type (ex: HTML file change) (#540) f29b9fe
- Fix: Fallback to HTTP1 when using proxies (#536) 5653cdf
- Fix: Allow baseUrl to be remote (#531) 5e6fc22
- Fix: Resolve JS imports inside of HTML script tags (#527) 641cc81
- Fix: Import a folder with trailing slash on the path (#529) 55fb04c
- Fix (
externalPackage
): now matches deep imports within an external package (#533) f60ae3d - (Internal, use at your own risk!)
import {unstable_installCommand} from 'snowpack';
(#525) d203b02 - (Internal only) Add standard file interface (#541) b538d68
- (Internal only) Swap Chalk for Kleur (#520) e7d67ff
PS: Our webpack plugin
v2.5.4...v2.6.0