@@ -123,6 +123,18 @@ When this value is falsy, the plugin doesn't run and no integrity
123123values are calculated. It is recommended to disable the plugin in
124124development mode.
125125
126+ ## Exporting ` integrity ` values
127+
128+ You might want to export generated integrity hashes, perhaps for use
129+ with SSR. We recommend
130+ [ webpack-assets-manifest] ( https://github.com/webdeveric/webpack-assets-manifest )
131+ for this purpose. When configured with option ` integrity: true ` it
132+ will include the hashes generated by this plugin in the manifest
133+ (requires webpack-assets-manifest version >= 3 which in turn requires
134+ Webpack >= 4.)
135+
136+ [ Example usage with webpack-assets-manifest] ( examples/webpack-assets-manifest/ ) .
137+
126138## Caveats
127139
128140### Proxies
@@ -165,12 +177,12 @@ using a tool such as [`http-server`](https://github.com/indexzero/http-server).
165177
166178### Safari and Assets that Require Cookies
167179
168- As detailed in [ Webpack Issue
169- #6972 ] ( https://github.com/webpack/webpack/issues/6972 ) , the
170- ` crossOrigin ` attribute can break loading of assets in certain edge
171- cases due to a bug in Safari. Since SRI requires the ` crossOrigin `
172- attribute to be set, you may run into this case even when source URL
173- is same-origin with respect to the asset.
180+ As detailed in
181+ [ Webpack Issue #6972 ] ( https://github.com/webpack/webpack/issues/6972 ) ,
182+ the ` crossOrigin ` attribute can break loading of assets in certain
183+ edge cases due to a bug in Safari. Since SRI requires the
184+ ` crossOrigin ` attribute to be set, you may run into this case even
185+ when source URL is same-origin with respect to the asset.
174186
175187## Further Reading
176188
0 commit comments