Releases: waysact/webpack-subresource-integrity
Releases · waysact/webpack-subresource-integrity
v5.2.0-rc.1
- Performance optimizations for big projects (#189)
- Add ES module distribution (CommonJS still available)
- Internal refactoring
- Dev dependency upgrades
v5.1.0
- Allow deferred loading of hashes. Specifying the new option
hashLoading: "lazy"
will cause integrity hashes for any given asset to be defined in its direct parents in the chunk graph. This can lead to duplication of hashes across assets, but can significantly reduce the size of entry chunk(s) when there are a large number of async chunks. (#171)
v5.0.0
No changes compared to v5.0.0-rc.1.
Changes compared to v1.5.2:
BREAKING CHANGES
(See migrating from v1 to v5.)
- Drop compatibility with Webpack < 5.12.0.
- Drop compatibility with Node < 10.
- Drop compatibility with html-webpack-plugin < 5.0.0-beta.1.
- Drop default export, new named export
SubresourceIntegrityPlugin
. - When integrity for an asset cannot be determined this now emits an error. Previously, a warning was emitted.
- Option
enabled
now defaults to"auto"
, which enables the plugin in all Webpack modes except fordevelopment
. Previously, the plugin was disabled by default in all modes.
Other Changes
- Compatibility with html-webpack-plugin 5 and new Webpack 5 asset processing pipeline.
- Option
hashFuncNames
now has a default:["sha384"]
. - All code has been rewritten in TypeScript. We now include TypeScript type definitions inside the package.
- No longer imports webpack (#150)
- Warn when using dangerous filename hashes (#162)
v5.0.0-rc.1
- Warn when using dangerous filename hashes (#162)
- Minor non-functional changes
v5.0.0-alpha.5
- Fix handling of chunks with multiple files (#154)
- Fix stats factory when using real content hash
v5.0.0-alpha.4
- Fix real content hash generation (#152)
v5.0.0-alpha.3
-
Do not import webpack (#150)
Adds compatibility with Next.js 10.0.6. Please note that installing this plugin in Next.js is not enough to gain integrity since top-level assets will remain unprotected.
v5.0.0-alpha.2
- Fix error when a processed tag has no attributes (#147)
v5.0.0-alpha.1
BREAKING CHANGES
- Drop compatibility with Webpack < 5.12.0.
- Drop compatibility with Node < 10.
- Drop compatibility with html-webpack-plugin < 5.0.0-beta.1.
- Drop default export, new named export
SubresourceIntegrityPlugin
. - When integrity for an asset cannot be determined this now emits an error. Previously, a warning was emitted.
- Option
enabled
now defaults to"auto"
, which enables the plugin in all Webpack modes except fordevelopment
. Previously, the plugin was disabled by default in all modes.
Other Changes
- Compatibility with html-webpack-plugin 5 and new Webpack 5 asset processing pipeline.
- Option
hashFuncNames
now has a default:["sha384"]
. - All code has been rewritten in TypeScript. We now include TypeScript type definitions inside the package.