You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Revert "feat(html-loader): replace file-loader with type: asset/resource for HTML assets" (7961a2b)
Revert "feat(tsconfig): compile TypeScript to ES2020 modules" (f9eda5b)
Revert "feat(assets): use Asset Modules in place of file-loader" (98b3676)
Revert "fix(deps): delete file-loader from bundled dependencies" (322a553)
BREAKING CHANGES
dev-server: webpack-dev-server 4.x is now required. webpack-dev-server 3.x is no longer
supported.
node: node ^13 || ^15 are no longer supported.
Modules are now resolved according to ESM module rules. File imports must specify
the path to the file including file extension, and in particular imports of TypeScript files must
specify the path to the file but with the ".js" extension instead of ".ts" or ".tsx". See https://gist.github.com/sindresorhus/a39789f98801d908bbc7ff3ecc99d99c.
This software now requires node >= 12.
tsconfig: TypeScript is now configured to emit ESM modules instead of CommonJS modules. See
advice for migrating to ESM at https://gist.github.com/sindresorhus/a39789f98801d908bbc7ff3ecc99d99c. Here we go again. The
node/JS/TypeScript/webpack ecosystem should actually be ready for this now.
TypeScript >= 4.2 is now required
assets: Asset modules (*.html, *.jpg, *.mp3, etc) are now exposed as CommonJS modules, not
ES Modules. This is for forwards compatibility with native webpack Asset Modules
(https://webpack.js.org/guides/asset-modules/) when we are able to start using them.
html-loader: This may break compatibility with downstream projects that use the customize
callback to customize rules for loading HTML files.
html-loader: Various upstream breaking changes may affect downstream consumers who use the
customize callback to customize the webpack config. See
deps: Consuming projects must upgrade ts-loader to v8.x.
target: webpack will generate code that uses ES2017 syntax. This breaks compatibility with
Node < 8.10 and with very old browsers that do not support ES2017 syntax. If you need to support
these older systems, we recommend you stay with webpack-config v3.x.
deps: Downstream projects must upgrade to webpack 5 when upgrading to this version of
webpack-config. There are some breaking changes in webpack 5. Most notably the Buffer and process
APIs from node are no longer shimmed by webpack when building for the web. See the webpack
documentation.
tsconfig: TypeScript code now compiles to ES2017. This breaks compatibility with Node < 8.10
and with very old browsers that do not support ES2017 syntax. If you need to support these older
systems either override "compilerOptions": { "target": "es5" }, or use Babel to compile ES6+ code
down to ES5.