Upgrade node-sass to version 5.0.0 #438
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ node-sass (^4.13.1 → ^5.0.0) · Repo · Changelog
Release Notes
5.0.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 42 commits:
chore: Add Node 15 support (#2983)Add a deprecation message to the readme (#3011)chore: Don't upload artifacts on PRschore: Only run coverage on main repobuild(deps): update actions/setup-node requirement to v2.1.2build(deps-dev): bump rimraf from 2.7.1 to 3.0.2chore: Don't double build DependaBot PRschore: Add weekly DependaBot updatesRemove deprecated process.sass APIReplace lodash/assign in favor of the native Object.assignRemove workarounds for old Node.js versionschore: Remove second NPM badgechore: Remove Slack badgechore: Cleanup status badgeschore: Bump minimum engine version to v10chore: Add basic Node version support policychore: Bump node-gyp to 7.1.0chore: Bump cross-spawn to v7.0.3chore: Update Istanbul to NYCchore: Bump mocha to v8.1.3chore: Skip constructor tests on v14.6+chore: Hoist test ESLint configchore: Remove disabled and recommended rulesfix: Bump ESLint to 7.10 and fix new issueschore: Use strict assertchore: Drop object-merge used by old sass-specfix: Read fixture as utf-8fix: assert.deepEqual to strictDeepEqualtypo: corectly -> correctlyfix: Depreciate Assert equal to strictEqualFix tests that have always been brokechore: Add GitHub Coverallschore: Drop sass-spec testingchore: Use action/upload-artifact@v2 for Alpinechore: Move macOS to GitHub Actionschore: Move Linux testing to GitHub Actionschore: Move Coverage to GitHub Actionschore: Move Linting to GitHub Actionschore: Move Windows x64 to GitHub Actionschore: Remove CI for unsupported Node versionsimproved language to be more sensitive to less privileged populations (#2944)fix: Flatten sourceMap folder detectionDepfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase.All Depfu comment commands