webpack-subresource-integrity - npm Package Compare versions

Comparing version 1.0.0-rc.1 to 1.0.0

index.js

		@@ -229,4 +229,4 @@ var crypto = require('crypto');
		compilation,
		'Chunks loaded by HMR are unprotected. ' +
		'Consider disabling webpack-subresource-integrity in development mode.'
		'webpack-subresource-integrity may interfere with hot reloading. ' +
		'Consider disabling this plugin in development mode.'
		);
		@@ -233,0 +233,0 @@ }

package.json

		{
		"name": "webpack-subresource-integrity",
		"version": "1.0.0-rc.1",
		"version": "1.0.0",
		"description": "Webpack plugin for enabling Subresource Integrity",
		@@ -54,5 +54,5 @@ "engines": {
		"mocha": "^3.1.2",
		"nyc": "^10.0.0",
		"nyc": "^11.0.0",
		"soupselect": "^0.2.0",
		"style-loader": "^0.17.0",
		"style-loader": "^0.18.0",
		"tmp": "^0.0.31",
		@@ -59,0 +59,0 @@ "travis-after-all": "^1.4.4",

README.md

		@@ -16,3 +16,3 @@ # webpack-subresource-integrity
		- Support for code splitting (integrity for lazy-loaded chunks)
		- Compatible with Webpack 1.x and 2.x
		- Compatible with Webpack 1.x, 2.x and 3.x

		@@ -168,8 +168,12 @@ ## Installation

		### Hot Module Replacement
		### Hot Reloading

		Chunks loaded via Hot Module Replacement (HMR) are not currently
		protected. This shouldn't be a problem because HMR is usually used
		only in development mode where SRI is not normally needed.
		This plugin can interfere with hot reloading and therefore should be
		disabled when using tools such as `webpack-dev-server`. This shouldn't
		be a problem because hot reloading is usually used only in development
		mode where SRI is not normally needed.

		For testing SRI without setting up a full-blown web server, consider
		using a tool such as [`http-server`](https://github.com/indexzero/http-server).

		## Further Reading
		@@ -176,0 +180,0 @@

New alerts