Upgrade sass-loader: 8.0.2 → 10.0.3 (major)

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?

✳️ sass-loader (8.0.2 → 10.0.3) · Repo · Changelog

Release Notes

10.0.3

10.0.3 (2020-10-09)

Chore

update schema-utils

10.0.2

10.0.2 (2020-09-03)

Bug Fixes

source maps generation (#886) (8327d55)

10.0.0

10.0.0 (2020-08-24)

Bug Fixes

handle absolute windows path in source maps

See notes for https://github.com/webpack-contrib/sass-loader/releases/tag/v10.0.0-rc.0 release

9.0.3

9.0.3 (2020-08-05)

Bug Fixes

resolution algorithm (#875) (ea73cfa)

9.0.2

9.0.2 (2020-07-07)

Bug Fixes

resolution algorithm for node-sass (#866) (4584c90)

9.0.1

9.0.1 (2020-07-03)

Bug Fixes

do not crash on errors (#860) (e854933)

9.0.0

9.0.0 (2020-07-02)

⚠ BREAKING CHANGES

minimum supported Nodejs version is 10.13

prefer sass (dart-sass) by default, it is strongly recommended to migrate on sass (dart-sass)

the prependData option was removed in favor the additionalData option, see docs

when the sourceMap is true, sassOptions.sourceMap, sassOptions.sourceMapContents, sassOptions.sourceMapEmbed, sassOptions.sourceMapRoot and sassOptions.omitSourceMapUrl will be ignored.

Features

pass the loader context to custom importers under the this.webpackLoaderContext property (#853) (d487683)

supports for process.cwd() resolution logic by default (#837) (0c8d3b3)

supports for SASS-PATH env variable resolution logic by default (#836) (8376179)

supports for the sass property for the exports field from package.json (conditional exports, for more information read docs)

Bug Fixes

avoid different content on different os (#832) (68dd278)

resolution logic when the includePaths option used was improved (#827) (cbe5ad4)

resolution logic for file:// scheme was improved (17832fd)

resolution logic for absolute paths and server relative URLs was improved

source maps generation was improved

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 60 commits:

👉 No CI detected

You don't seem to have any Continuous Integration service set up!

Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.

This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:

* [Circle CI](https://circleci.com), [Semaphore ](https://semaphoreci.com) and [Travis-CI](https://travis-ci.com) are all excellent options. * If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github. * If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with `depfu/`.

Depfu Status

Depfu 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

@depfu rebase
Rebases against your default branch and redoes this update

@depfu recreate
Recreates this PR, overwriting any edits that you've made to it

@depfu merge
Merges this PR once your tests are passing and conflicts are resolved

@depfu close
Closes this PR and deletes the branch

@depfu reopen
Restores the branch and reopens this PR (if it's closed)

@depfu pause
Ignores all future updates for this dependency and closes this PR

@depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR

@depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)

xsoulspace / sheets_manager_excel_addin