Skip to content
This repository was archived by the owner on Oct 19, 2022. It is now read-only.

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Oct 1, 2022

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
sass-loader 8.0.2 -> 13.1.0 age adoption passing confidence

Release Notes

webpack-contrib/sass-loader

v13.1.0

Compare Source

Features
13.0.2 (2022-06-27)
Bug Fixes
13.0.1 (2022-06-24)
Bug Fixes

v13.0.2

Compare Source

v13.0.1

Compare Source

v13.0.0

Compare Source

⚠ BREAKING CHANGES
  • minimum supported Node.js version is 14.15.0 (#​1048)
  • emit @warn at-rules as webpack warnings by default, if you want to revert behavior please use the warnRuleAsWarning option (#​1054) (58ffb68)
Bug Fixes

v12.6.0

Compare Source

Features
  • added support for automatic loading of sass-embedded (#​1025) (c8dae87)

v12.5.0

Compare Source

Features
  • added support for sass-embedded (faster than node-sass), feel free to feedback
  • added the api option (modern api is experimental and currently doesn't support built-in webpack resolver) (afbe114)

v12.4.0

Compare Source

Features

v12.3.0

Compare Source

Features

v12.2.0

Compare Source

Features

v12.1.0

Compare Source

Features
  • allow String value for the implementation option (382a3ca)

v12.0.0

Compare Source

⚠ BREAKING CHANGES
  • minimum supported Node.js version is 12.13.0
Bug Fixes
  • crash in custom importers with worker threads (#​958) (67aa139)
  • resolving _index.import.scss/index.import.scss in packages (#​906) (6641a16)
11.1.1 (2021-05-13)
Bug Fixes
  • disabled auto importing fiber on node >= 16 due incompatibility problems (#​950) (4ca004b)

v11.1.1

Compare Source

v11.1.0

Compare Source

Features
11.0.1 (2021-02-08)
Bug Fixes
  • compatibility with custom importers for node-sass (#​927) (af5a072)

v11.0.1

Compare Source

v11.0.0

Compare Source

Notes
  • using ~ is deprecated and can be removed from your code (we recommend it), but we still support it for historical reasons.

Why you can removed it?
The loader will first try to resolve @import/@use as relative, if it cannot be resolved, the loader will try to resolve @import/@use inside node_modules.
Using ~ means looking for files in node_modules or resolve.alias or resolve.fallback.

⚠ BREAKING CHANGES
  • minimum supported webpack version is 5
Features
  • supported the resolve.byDependency option, you can setup { resolve: { byDependency: { sass: { mainFiles: ['custom', '...'] } } } }

v10.3.1

Compare Source

10.3.1 (2022-07-06)
Bug Fixes

v10.3.0

Compare Source

Features

v10.2.1

Compare Source

10.2.1 (2022-01-14)
Bug Fixes
  • backported disabled auto importing fiber on node >= 16 (#​1014) (f4234e4)

v10.2.0

Compare Source

Features
10.1.1 (2021-01-11)
Bug Fixes
  • problem with resolving and the includePaths option (#​913) (cadc75e)

v10.1.1

Compare Source

v10.1.0

Compare Source

Features
10.0.5 (2020-11-02)
Bug Fixes
10.0.4 (2020-10-22)
Bug Fixes
10.0.3 (2020-10-09)
Chore
  • update schema-utils
10.0.2 (2020-09-03)
Bug Fixes
10.0.1 (2020-08-25)
Chore
  • update deps

v10.0.5

Compare Source

v10.0.4

Compare Source

v10.0.3

Compare Source

v10.0.2

Compare Source

v10.0.1

Compare Source

v10.0.0

Compare Source

Bug Fixes
  • handle absolute windows path in source maps

v9.0.3

Compare Source

v9.0.2

Compare Source

v9.0.1

Compare Source

v9.0.0

Compare Source

⚠ 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
8.0.2 (2020-01-13)
Bug Fixes
8.0.1 (2020-01-10)
Bug Fixes

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Mend Renovate. View repository job log here.

@renovate
Copy link
Contributor Author

renovate bot commented Oct 1, 2022

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: frontend/package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @vue/cli-plugin-babel@4.5.13
npm ERR! Found: @vue/cli-service@5.0.1
npm ERR! node_modules/@vue/cli-service
npm ERR!   dev @vue/cli-service@"5.0.1" from the root project
npm ERR!   peer @vue/cli-service@"^3.0.0 || ^4.0.0 || ^5.0.0-0" from @vue/cli-plugin-router@5.0.8
npm ERR!   node_modules/@vue/cli-service/node_modules/@vue/cli-plugin-router
npm ERR!     @vue/cli-plugin-router@"^5.0.1" from @vue/cli-service@5.0.1
npm ERR!   1 more (@vue/cli-plugin-vuex)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @vue/cli-service@"^3.0.0 || ^4.0.0-0" from @vue/cli-plugin-babel@4.5.13
npm ERR! node_modules/@vue/cli-plugin-babel
npm ERR!   dev @vue/cli-plugin-babel@"4.5.13" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: @vue/cli-service@4.5.19
npm ERR! node_modules/@vue/cli-service
npm ERR!   peer @vue/cli-service@"^3.0.0 || ^4.0.0-0" from @vue/cli-plugin-babel@4.5.13
npm ERR!   node_modules/@vue/cli-plugin-babel
npm ERR!     dev @vue/cli-plugin-babel@"4.5.13" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate-cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate-cache/others/npm/_logs/2022-10-06T22_31_50_499Z-debug-0.log

@renovate renovate bot force-pushed the renovate/sass-loader-13.x branch from a335b82 to a076244 Compare October 6, 2022 22:32
@ju-c ju-c closed this Oct 19, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants