Bump sass from 1.71.1 to 1.74.1 in /webapp
Bumps sass from 1.71.1 to 1.74.1.
Release notes
Sourced from sass's releases.
Dart Sass 1.74.1
To install Sass 1.74.1, download one of the packages below and add it to your PATH, or see the Sass website for full installation instructions.
Changes
- No user-visible changes.
See the full changelog for changes in earlier releases.
Dart Sass 1.72.0
To install Sass 1.72.0, download one of the packages below and add it to your PATH, or see the Sass website for full installation instructions.
Changes
Support adjacent
/
s without whitespace in between when parsing plain CSS expressions.Allow the Node.js
pkg:
importer to load Sass stylesheets forpackage.json
exports
field entries without extensions.When printing suggestions for variables, use underscores in variable names when the original usage used underscores.
JavaScript API
- Properly resolve
pkg:
imports with the Node.js package importer when arguments are passed to the JavaScript process.See the full changelog for changes in earlier releases.
Changelog
Sourced from sass's changelog.
1.74.1
- No user-visible changes.
1.74.0
JS API
Add a new top-level
deprecations
object, which contains variousDeprecation
objects that define the different types of deprecation used by the Sass compiler and can be passed to the options below.Add a new
fatalDeprecations
compiler option that causes the compiler to error if any deprecation warnings of the provided types are encountered. You can also pass in aVersion
object to treat all deprecations that were active in that Dart Sass version as fatal.Add a new
futureDeprecations
compiler option that allows you to opt-in to certain deprecations early (currently justimport
).Add a new
silenceDeprecations
compiler option to ignore any deprecation warnings of the provided types.Command-Line Interface
Add a new
--silence-deprecation
flag, which causes the compiler to ignore any deprecation warnings of the provided types.Previously, if a future deprecation was passed to
--fatal-deprecation
but not--future-deprecation
, it would be treated as fatal despite not being enabled. Both flags are now required to treat a future deprecation as fatal with a warning emitted if--fatal-deprecation
is passed without--future-deprecation
, matching the JS API's behavior.Dart API
The
compile
methods now take in asilenceDeprecations
parameter, which causes the compiler to ignore any deprecation warnings of the provided types.Add
Deprecation.obsoleteIn
to match the JS API. This is currently null for all deprecations, but will be used once some deprecations become obsolete in Dart Sass 2.0.0.Potentially breaking bug fix: Fix a bug where
compileStringToResultAsync
ignoredfatalDeprecations
andfutureDeprecations
.The behavior around making future deprecations fatal mentioned in the CLI section above has also been changed in the Dart API.
1.73.0
... (truncated)
Commits
-
1137797
Fix bulma and release 1.74.1 (#2210) -
d9220d9
Complete implementation the deprecations API (#2207) -
783c248
Fix typo in function documentation (#2205) -
c8d0643
Better handle filesystem importers when load paths aren't necessary (#2203) -
9302b35
Add support for nesting in plain CSS (#2198) -
772280a
Support linux-riscv64 and windows-arm64 (#2201) -
ce16b35
Cut a release (#2194) -
9af6bbf
Properly handlepkg:
imports with args (#2193) -
0330491
Update to node 20 (#2192) -
48e2d0c
Preserve underscores inVariableExpression.toString()
(#2185) - Additional commits viewable in compare view
Dependabot commands
You can trigger Dependabot actions by commenting on this MR
-
$dependabot recreate
will recreate this MR rewriting all the manual changes and resolving conflicts