npm @rspack/core 0.1.12
v0.1.12

latest releases: 1.1.0, 1.1.0-beta.0, 1.0.14...
17 months ago

Core features

Breaking Changes

In the previous release, Rspack incorrectly supported [ext] in output.filename, we are removing [ext] support in output.filename in 0.1.12 to align with webpack, which may be a breaking change for applications using [ext] in output.filename. see #3270 (comment) for migration guide from previous release.

Support resolve.exportsFields

Support set exportsFields in package.json that are used for resolving module requests

module.exports = {
  //...
  resolve: {
    exportsFields: ['source', '...'],
  },
};

Support https://github.com/TypeStrong/fork-ts-checker-webpack-plugin

you can use fork-ts-checker-webpack-plugin directly in rspack to typecheck your codebase.

Support dataURI

import a from 'data:text/javascript,export default "a";';
expect(a).toBe("a");

What's Changed

Performance Improvements ⚡

Exciting New Features 🎉

  • feat(core): support webpack-manifest-plugin by @hardfist in #3163
  • feat(library): support system.js by @suxin2017 in #3124
  • feat(resolve): support custom exports fields by @bvanjoi in #3186
  • feat: add output.hotUpdateMainFilename & output.hotUpdateChunkFilename by @underfin in #3188
  • feat: data uri support by @ahabhgk in #3220
  • feat(types): support string or object in copy.patterns array by @9aoy in #3218
  • feat: add scheme, mimetype, and resourceFragment rule condition by @ahabhgk in #3238
  • feat: normal module factory after resolve hooks by @IWANABETHATGUY in #3060
  • feat: add support for Rule.loader and Rule.options by @h-a-n-a in #3246
  • feat(module_optional): support require.resolve and require.resolveWeak by @suxin2017 in #3237
  • feat: add afterCompile hook by @edusperoni in #3235

Bug Fixes 🐞

Other Changes

New Contributors

Full Changelog: v0.1.11...v0.1.12

Don't miss a new core release

NewReleases is sending notifications on new releases.