-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tests on path resolution fail #2
Comments
Add version detection and use deprecated `new Buffer(<string>)`, if the new Buffer API isn't supported by runtime. See nodejs/node#7562.
@clarmso Thanks for report! You're right, I totally missed that Commit 32604ba contains a fix for older node versions. Expect a patch-release later today. |
…overage (#2) Revert version-check from previous commit 32604ba, and use Buffer constructor for converting HTML-formatted string. Looks like, nodejs isn't emitting a deprecation warning any more since v7.2.1 (nodejs/node#9529). Mocking/Stubbing `process.version` is not only super ugly, but also super tricky. Until 8.x is released, no further changes should be necessary.
@macedigital It was my bad that I did not include the version of Node.js in my report. It's good that you figured out the error is related to my old Node install. Once the patch release is available, I'll try it with both of my old and new Node installation. |
@clarmso No problem 😄 Release v1.2.1 is out, let me know if it works for you now. |
All tests passed on Node v4.2.2 and v6.10.0 😄 |
Cool, happy to help 😃 |
All tests with path resolution fail. Here's the test result given by "npm test":
gulp-sri-hash
plugin
✓ should know it's name
✓ should be callable
plugin()
✓ should pass through null files
✓ should throw on streams
✓ should bail on unsupported hashing algorithm
✓ should ignore missing external files
✓ should ignore existing
integrity
attributewith absolute path resolution
1) should apply integrity hash sha256
2) should apply integrity hash sha384
3) should apply integrity hash sha512
4) should apply custom selectors
5) should apply hashing to whitelisted prefixes
with relative path resolution
6) should apply integrity hash sha256
7) should apply integrity hash sha384
8) should apply integrity hash sha512
9) should apply custom selectors
Here is the error message for one of the failed tests. All failed tests start with "Uncaught TypeError: this is not a typed array.".
The text was updated successfully, but these errors were encountered: