ember-cli-sri
Advanced tools
ember-cli-sri - npm Package Compare versions
Comparing version 2.0.0 to 2.1.0
@@ -0,1 +1,9 @@ | ||
| # 2.1.0 | ||
| - bump broccoli-sri-hash to 2.1.0 | ||
| - Add fingerprintCheck option and documentation | ||
| - lock jQuery to 1.11.3 to [fix Travis and AppVery issues](http://emberjs.com/blog/2016/01/15/ember-2-3-released.html#toc_removing-the-jquery-version-assertion) | ||
| # 2.0.0 | ||
| - Disable paranoiaCheck by default | ||
| # 1.1.0 | ||
@@ -2,0 +10,0 @@ - Enable by default paranoiaCheck |
@@ -30,2 +30,10 @@ /* jshint node: true */ | ||
| } | ||
| if (!('paranoiaCheck' in this.options)) { | ||
| this.options.paranoiaCheck = false; | ||
| } | ||
| if (!('fingerprintCheck' in this.options)) { | ||
| this.options.fingerprintCheck = false; | ||
| } | ||
| }, | ||
@@ -32,0 +40,0 @@ postprocessTree: function(type, tree) { |
| { | ||
| "name": "ember-cli-sri", | ||
| "version": "2.0.0", | ||
| "version": "2.1.0", | ||
| "description": "SRI generation for Ember CLI", | ||
@@ -49,3 +49,3 @@ "directories": { | ||
| "dependencies": { | ||
| "broccoli-sri-hash": "^2.0.0" | ||
| "broccoli-sri-hash": "^2.1.0" | ||
| }, | ||
@@ -52,0 +52,0 @@ "ember-addon": { |
@@ -70,3 +70,4 @@ # Ember-cli-sri | ||
| - **enabled** - default: true | ||
| - **paranoiaCheck** - default: true | ||
| - **paranoiaCheck** - default: false | ||
| - **fingerprintCheck** - default: false | ||
| - **fingerprint** | ||
@@ -125,11 +126,19 @@ - **prepend** - resources with a full path will only get an applied integrity if the md5 checksum passes | ||
| **This addon will always take the default pain free stance; so this has been enabled by default until the issue is resolved.** | ||
| There was an encoding issue based on certain characters when using Chrome, the fix for which [landed](https://code.google.com/p/chromium/issues/detail?id=527286) in Chrome 46. | ||
| This check fails if there is any non ASCII characters. On failure the file won't have an integrity attribute added. | ||
| Currently, it defaults to false (i.e. this check is disabled). You can reenable it if you wish to remain compatible with | ||
| versions of Chrome < 46. | ||
| Currently there is an encoding issue based on certain characters which is [still being debugged](https://code.google.com/p/chromium/issues/detail?id=527286) when using Chrome. | ||
| This check fails if there is any non ASCII characters. On failure the file won't have a integrity attribute added. | ||
| **Please note** this will be removed as a default in the future; with the desire to remove all of the checking code too. | ||
| ### 'fingerprintCheck' | ||
| If you are fingerprinting your assets and/or prepending a URL (e.g. to your static web server or CDN), you will likely want | ||
| to disable this check. Otherwise, if your assets include other assets, they will fail the check and the file won't have an | ||
| integrity attribute added. | ||
| Currently, it defaults to false (i.e. this check is disabled). You can reenable it for a little extra confidence that the | ||
| correct files are being hashed, but only if you are not fingerprinting or prepending your assets and have no plans to in the | ||
| future. | ||
| ## Browser support | ||
| - Chrome 45 | ||
| - Chrome 46 | ||
| - Firefox 43 | ||
@@ -136,0 +145,0 @@ |
New alerts
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
Fixed alerts
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
Improved metrics
- Total package byte prevSize
- increased by6.6%
15985
- Lines of code
- increased by8.45%
77
- Number of lines in readme file
- increased by6.29%
152
Dependency changes
Updatedbroccoli-sri-hash@^2.1.0