chore(deps-dev): bump the npm-dev-dependencies group with 8 updates

[dependabot]

Bumps the npm-dev-dependencies group with 8 updates:

Package	From	To
@vitest/coverage-v8	2.0.0	2.1.1
esbuild	0.20.2	0.24.0
eslint	8.57.0	8.57.1
eslint-plugin-react	7.34.1	7.37.0
sass	1.76.0	1.79.4
stylelint	16.4.0	16.9.0
stylelint-config-standard	36.0.0	36.0.1
vitest	2.0.0	2.1.1

Updates @vitest/coverage-v8 from 2.0.0 to 2.1.1

Release notes

Sourced from @​vitest/coverage-v8's releases.

v2.1.1

   🐞 Bug Fixes

• browser:
  • Make example test callbacks async  -  by @​aqandrew in vitest-dev/vitest#6484 (16aa7)
  • Optimize vitest-browser-vue correctly  -  by @​sheremet-va in vitest-dev/vitest#6490 (5cbb0)
• workspace:
  • Resolve glob pattern once to avoid name collision  -  by @​sheremet-va in vitest-dev/vitest#6489 (36b5a)

    View changes on GitHub

v2.1.0

This release makes another big change to the Browser Mode by introducing locators API:

test('renders blog posts', async () => {
  const screen = page.render(<Blog />)
await expect.element(screen.getByRole('heading', { name: 'Blog' })).toBeInTheDocument()
const [firstPost] = screen.getByRole('listitem').all()
await firstPost.getByRole('button', { name: 'Delete' }).click()
expect(screen.getByRole('listitem').all()).toHaveLength(3)
})

You can use either vitest-browser-vue, vitest-browser-svelte or vitest-browser-react to render components and make assertions using locators. Locators are also available on the page object from @vitest/browser/context.

Potential Breaking Change

• workspace:
  • Correctly resolve workspace globs and file paths  -  by @​sheremet-va in vitest-dev/vitest#6316 (afdcb)
  • This changes how the custom glob pattern in the workspace config is treated. Any file matching the glob is considered a Vitest config file. Any folder matching the glob pattern is treated as a workspace project and is subject to the regular config resolution (single vitest.config.ts or vite.config.ts inside the folder)
  • For example, projects/* will match anything inside the projects folder. If it's a folder, we try to find the config inside that folder (if there is none, it is still treated as a project with the default config). If it's a file, it will be treated as a Vitest config. projects/**/* previously would assume that you only wanted to have folders as projects, but now it will match every single file insideprojects.
  • This change doesn't affect non-glob usage.

   🚀 Features

• api:
  • Make spec into a class instead of a tuple  -  by @​sheremet-va in vitest-dev/vitest#6355 (874a1)
• browser:
  • Move page.config to server.config, add more docs  -  by @​sheremet-va in vitest-dev/vitest#6252 (af2b8)
  • Make iframe scalable, improve documentation  -  by @​sheremet-va in vitest-dev/vitest#6257 (74ca1)
  • Introduce built-in locators  -  by @​sheremet-va in vitest-dev/vitest#6084 (3347f)
  • Support v8 coverage  -  by @​AriPerkkio in vitest-dev/vitest#6273 (34199)
  • Support userEvent.upload in playwright provider  -  by @​sheremet-va in vitest-dev/vitest#6442 (cf148)
  • Support --inspect  -  by @​AriPerkkio in vitest-dev/vitest#6433 (0499a)
  • Support --inspect-brk  -  by @​AriPerkkio in vitest-dev/vitest#6434 (7ab0f)

... (truncated)

Commits

• 699055e chore: release v2.1.1
• 9f1fd18 chore: release v2.1.0
• b2be23e chore: release v2.1.0-beta.7
• 8ac7011 chore: release v2.1.0-beta.6
• da52d23 fix(coverage): use project specific vitenode for uncovered files (#6044)
• 5932a7f feat(coverage): add --exclude-after-remap (#6309)
• 34199bd feat(browser): support v8 coverage (#6273)
• 72056b5 chore: release v2.1.0-beta.5
• 91dea8c fix(coverage): v8 to warn instead of crash when conversion fails (#6318)
• 1f6cb59 fix(coverage): v8 to support source maps with multiple sources (#6120)
• Additional commits viewable in compare view

Updates esbuild from 0.20.2 to 0.24.0

Release notes

Sourced from esbuild's releases.

v0.24.0

This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.23.0 or ~0.23.0. See npm's documentation about semver for more information.

• Drop support for older platforms (#3902)

  This release drops support for the following operating system:

  • macOS 10.15 Catalina

  This is because the Go programming language dropped support for this operating system version in Go 1.23, and this release updates esbuild from Go 1.22 to Go 1.23. Go 1.23 now requires macOS 11 Big Sur or later.

  Note that this only affects the binary esbuild executables that are published to the esbuild npm package. It's still possible to compile esbuild's source code for these older operating systems. If you need to, you can compile esbuild for yourself using an older version of the Go compiler (before Go version 1.23). That might look something like this:

  git clone https://github.com/evanw/esbuild.git
  cd esbuild
  go build ./cmd/esbuild
  ./esbuild --version
  

• Fix class field decorators in TypeScript if useDefineForClassFields is false (#3913)

  Setting the useDefineForClassFields flag to false in tsconfig.json means class fields use the legacy TypeScript behavior instead of the standard JavaScript behavior. Specifically they use assign semantics instead of define semantics (e.g. setters are triggered) and fields without an initializer are not initialized at all. However, when this legacy behavior is combined with standard JavaScript decorators, TypeScript switches to always initializing all fields, even those without initializers. Previously esbuild incorrectly continued to omit field initializers for this edge case. These field initializers in this case should now be emitted starting with this release.

• Avoid incorrect cycle warning with tsconfig.json multiple inheritance (#3898)

  TypeScript 5.0 introduced multiple inheritance for tsconfig.json files where extends can be an array of file paths. Previously esbuild would incorrectly treat files encountered more than once when processing separate subtrees of the multiple inheritance hierarchy as an inheritance cycle. With this release, tsconfig.json files containing this edge case should work correctly without generating a warning.

• Handle Yarn Plug'n'Play stack overflow with tsconfig.json (#3915)

  Previously a tsconfig.json file that extends another file in a package with an exports map could cause a stack overflow when Yarn's Plug'n'Play resolution was active. This edge case should work now starting with this release.

• Work around more issues with Deno 1.31+ (#3917)

  This version of Deno broke the stdin and stdout properties on command objects for inherited streams, which matters when you run esbuild's Deno module as the entry point (i.e. when import.meta.main is true). Previously esbuild would crash in Deno 1.31+ if you ran esbuild like that. This should be fixed starting with this release.

  This fix was contributed by @​Joshix-1.

v0.23.1

• Allow using the node: import prefix with es* targets (#3821)

  The node: prefix on imports is an alternate way to import built-in node modules. For example, import fs from "fs" can also be written import fs from "node:fs". This only works with certain newer versions of node, so esbuild removes it when you target older versions of node such as with --target=node14 so that your code still works. With the way esbuild's platform-specific feature compatibility table works, this was added by saying that only newer versions of node support this feature. However, that means that a target such as --target=node18,es2022 removes the node: prefix because none of the es* targets are known to support this feature. This release adds the support for the node: flag to esbuild's internal compatibility table for es* to allow you to use compound targets like this:

  // Original code
  import fs from 'node:fs'
  fs.open
  // Old output (with --bundle --format=esm --platform=node --target=node18,es2022)
  import fs from "fs";

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.24.0

This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.23.0 or ~0.23.0. See npm's documentation about semver for more information.

• Drop support for older platforms (#3902)

  This release drops support for the following operating system:

  • macOS 10.15 Catalina

  This is because the Go programming language dropped support for this operating system version in Go 1.23, and this release updates esbuild from Go 1.22 to Go 1.23. Go 1.23 now requires macOS 11 Big Sur or later.

  Note that this only affects the binary esbuild executables that are published to the esbuild npm package. It's still possible to compile esbuild's source code for these older operating systems. If you need to, you can compile esbuild for yourself using an older version of the Go compiler (before Go version 1.23). That might look something like this:

  git clone https://github.com/evanw/esbuild.git
  cd esbuild
  go build ./cmd/esbuild
  ./esbuild --version
  

• Fix class field decorators in TypeScript if useDefineForClassFields is false (#3913)

  Setting the useDefineForClassFields flag to false in tsconfig.json means class fields use the legacy TypeScript behavior instead of the standard JavaScript behavior. Specifically they use assign semantics instead of define semantics (e.g. setters are triggered) and fields without an initializer are not initialized at all. However, when this legacy behavior is combined with standard JavaScript decorators, TypeScript switches to always initializing all fields, even those without initializers. Previously esbuild incorrectly continued to omit field initializers for this edge case. These field initializers in this case should now be emitted starting with this release.

• Avoid incorrect cycle warning with tsconfig.json multiple inheritance (#3898)

  TypeScript 5.0 introduced multiple inheritance for tsconfig.json files where extends can be an array of file paths. Previously esbuild would incorrectly treat files encountered more than once when processing separate subtrees of the multiple inheritance hierarchy as an inheritance cycle. With this release, tsconfig.json files containing this edge case should work correctly without generating a warning.

• Handle Yarn Plug'n'Play stack overflow with tsconfig.json (#3915)

  Previously a tsconfig.json file that extends another file in a package with an exports map could cause a stack overflow when Yarn's Plug'n'Play resolution was active. This edge case should work now starting with this release.

• Work around more issues with Deno 1.31+ (#3917)

  This version of Deno broke the stdin and stdout properties on command objects for inherited streams, which matters when you run esbuild's Deno module as the entry point (i.e. when import.meta.main is true). Previously esbuild would crash in Deno 1.31+ if you ran esbuild like that. This should be fixed starting with this release.

  This fix was contributed by @​Joshix-1.

0.23.1

• Allow using the node: import prefix with es* targets (#3821)

  The node: prefix on imports is an alternate way to import built-in node modules. For example, import fs from "fs" can also be written import fs from "node:fs". This only works with certain newer versions of node, so esbuild removes it when you target older versions of node such as with --target=node14 so that your code still works. With the way esbuild's platform-specific feature compatibility table works, this was added by saying that only newer versions of node support this feature. However, that means that a target such as --target=node18,es2022 removes the node: prefix because none of the es* targets are known to support this feature. This release adds the support for the node: flag to esbuild's internal compatibility table for es* to allow you to use compound targets like this:

  // Original code
  import fs from 'node:fs'
  fs.open

... (truncated)

Commits

• d34e79e publish 0.24.0 to npm
• 045a87f fix #3887: omit dead export warning for default
• 6e049b8 fix #3913: useDefineForClassFields and decorators
• 9c26f98 lower decorators for useDefineForClassFields #3913
• 46fdb68 fix #3898: incorrect cyclic tsconfig.json warning
• b500443 fix #3917: running esbuild cli with deno
• b125e62 run make update-compat-table
• 112b9aa fix #3915: stack overflow with yarn + tsconfig
• ed5a555 wasm: catch and rethrow stack overflows (#3915)
• 11d3196 fix #3902: update go 1.22.5 => 1.23.1
• Additional commits viewable in compare view

Updates eslint from 8.57.0 to 8.57.1

Release notes

Sourced from eslint's releases.

v8.57.1

Bug Fixes

• a19072f fix: add logic to handle fixTypes in the lintText() method (#18900) (Francesco Trotta)
• 04c7188 fix: Don't lint same file multiple times (#18899) (Francesco Trotta)
• 87ec3c4 fix: do not throw when defining a global named __defineSetter__ (#18898) (Francesco Trotta)
• 60a1267 fix: Provide helpful error message for nullish configs (#18889) (Milos Djermanovic)
• a0dea8e fix: allow name in global ignores, fix --no-ignore for non-global (#18875) (Milos Djermanovic)
• 3836bb4 fix: do not crash on error in fs.walk filter (#18886) (Milos Djermanovic)
• 2dec349 fix: skip processor code blocks that match only universal patterns (#18880) (Milos Djermanovic)

Documentation

• 6a5add4 docs: v8.x Add EOL banner (#18744) (Amaresh S M)
• b034575 docs: v8.x add version support page to the dropdown (#18731) (Amaresh S M)
• 760ef7d docs: v8.x add version support page in the side navbar (#18740) (Amaresh S M)
• 428b7ea docs: Add Powered by Algolia label to the search (#18658) (Amaresh S M)
• c68c07f docs: version selectors synchronization (#18265) (Milos Djermanovic)

Build Related

• 35d366a build: Support updates to previous major versions (#18870) (Milos Djermanovic)

Chores

• 140ec45 chore: upgrade @​eslint/js@​8.57.1 (#18913) (Milos Djermanovic)
• bcdfc04 chore: package.json update for @​eslint/js release (Jenkins)
• 3f6ce8d chore: pin [email protected] (#18910) (Milos Djermanovic)
• 9f07549 chore: ignore /docs/v8.x in link checker (#18660) (Milos Djermanovic)

Changelog

Sourced from eslint's changelog.

v8.57.1 - September 16, 2024

• 140ec45 chore: upgrade @​eslint/js@​8.57.1 (#18913) (Milos Djermanovic)
• bcdfc04 chore: package.json update for @​eslint/js release (Jenkins)
• 3f6ce8d chore: pin [email protected] (#18910) (Milos Djermanovic)
• a19072f fix: add logic to handle fixTypes in the lintText() method (#18900) (Francesco Trotta)
• 04c7188 fix: Don't lint same file multiple times (#18899) (Francesco Trotta)
• 87ec3c4 fix: do not throw when defining a global named __defineSetter__ (#18898) (Francesco Trotta)
• 60a1267 fix: Provide helpful error message for nullish configs (#18889) (Milos Djermanovic)
• 35d366a build: Support updates to previous major versions (#18870) (Milos Djermanovic)
• a0dea8e fix: allow name in global ignores, fix --no-ignore for non-global (#18875) (Milos Djermanovic)
• 3836bb4 fix: do not crash on error in fs.walk filter (#18886) (Milos Djermanovic)
• 2dec349 fix: skip processor code blocks that match only universal patterns (#18880) (Milos Djermanovic)
• 6a5add4 docs: v8.x Add EOL banner (#18744) (Amaresh S M)
• b034575 docs: v8.x add version support page to the dropdown (#18731) (Amaresh S M)
• 760ef7d docs: v8.x add version support page in the side navbar (#18740) (Amaresh S M)
• 428b7ea docs: Add Powered by Algolia label to the search (#18658) (Amaresh S M)
• 9f07549 chore: ignore /docs/v8.x in link checker (#18660) (Milos Djermanovic)
• c68c07f docs: version selectors synchronization (#18265) (Milos Djermanovic)

v9.10.0 - September 6, 2024

• 24c3ff7 chore: upgrade to @​eslint/js@​9.10.0 (#18866) (Francesco Trotta)
• 1ebdde1 chore: package.json update for @​eslint/js release (Jenkins)
• 301b90d feat: Add types (#18854) (Nicholas C. Zakas)
• bee0e7a docs: update README (#18865) (Milos Djermanovic)
• bcf0df5 feat: limit namespace import identifier in id-length rule (#18849) (ChaedongIm)
• 45c18e1 feat: add requireFlag option to require-unicode-regexp rule (#18836) (Brett Zamir)
• 5d80b59 docs: specify that ruleId can be null in custom formatter docs (#18857) (Milos Djermanovic)
• 156b1c3 docs: Update README (GitHub Actions Bot)
• e8fc5bd chore: update dependency @​eslint/core to ^0.5.0 (#18848) (renovate[bot])
• 343f992 refactor: don't use node.value when removing unused directives (#18835) (Milos Djermanovic)
• 183b459 feat: add error message for duplicate flags in no-invalid-regexp (#18837) (Tanuj Kanti)
• f6fdef9 docs: Update README (GitHub Actions Bot)
• c69b406 feat: report duplicate allowed flags in no-invalid-regexp (#18754) (Tanuj Kanti)
• a20c870 docs: Update README (GitHub Actions Bot)
• 90e699b docs: Update README (GitHub Actions Bot)
• 3db18b0 refactor: Extract FileContext into class (#18831) (Nicholas C. Zakas)
• 931d650 refactor: Use @​eslint/plugin-kit (#18822) (Nicholas C. Zakas)
• ed5cf0c chore: update dependency @​eslint/json to ^0.4.0 (#18829) (Milos Djermanovic)
• d1f0831 chore: added missing ids (#18817) (Strek)
• ec92813 refactor: Config class (#18763) (Nicholas C. Zakas)

v9.9.1 - August 23, 2024

• b0c34d0 chore: upgrade to @​eslint/js@​9.9.1 (#18809) (Francesco Trotta)
• cd5a0da chore: package.json update for @​eslint/js release (Jenkins)
• 4840930 docs: Update README with version support and clean up content (#18804) (Nicholas C. Zakas)
• f61f40d docs: Update globals examples (#18805) (Nicholas C. Zakas)
• e112642 refactor: Extract parsing logic from Linter (#18790) (Nicholas C. Zakas)

... (truncated)

Commits

• 5b9414c 8.57.1
• f66806d Build: changelog update for 8.57.1
• 140ec45 chore: upgrade @​eslint/js@​8.57.1 (#18913)
• bcdfc04 chore: package.json update for @​eslint/js release
• 3f6ce8d chore: pin [email protected] (#18910)
• a19072f fix: add logic to handle fixTypes in the lintText() method (#18900)
• 04c7188 fix: Don't lint same file multiple times (#18899)
• 87ec3c4 fix: do not throw when defining a global named __defineSetter__ (#18898)
• 60a1267 fix: Provide helpful error message for nullish configs (#18889)
• 35d366a build: Support updates to previous major versions (#18870)
• Additional commits viewable in compare view

Updates eslint-plugin-react from 7.34.1 to 7.37.0

Release notes

Sourced from eslint-plugin-react's releases.

v7.37.0

Added

• add type generation (#3830[] @​voxpelli)
• [no-unescaped-entities]: add suggestions (#3831[] @​StyleShit)
• [forbid-component-props]: add allowedForPatterns/disallowedForPatterns options (#3805[] @​Efimenko)
• [no-unstable-nested-components]: add propNamePattern to support custom render prop naming conventions (#3826[] @​danreeves)

Changed

• [readme] flat config example for react 17+ (#3824[] @​GabenGar)

#3805: jsx-eslint/eslint-plugin-react#3805 #3824: jsx-eslint/eslint-plugin-react#3824 #3826: jsx-eslint/eslint-plugin-react#3826 #3830: jsx-eslint/eslint-plugin-react#3830 #3831: jsx-eslint/eslint-plugin-react#3831 [forbid-component-props]: docs/rules/forbid-component-props.md [no-unescaped-entities]: docs/rules/no-unescaped-entities.md [no-unstable-nested-components]: docs/rules/no-unstable-nested-components.md

v7.36.1

Fixed

• no-is-mounted: fix logic in method name check (#3821[] @​Mathias-S)
• jsx-no-literals: Avoid crashing on valueless boolean props (#3823[] @​reosarevok)

#3823: jsx-eslint/eslint-plugin-react#3823 #3821: jsx-eslint/eslint-plugin-react#3821

v7.36.0

Added

• [no-string-refs]: allow this.refs in > 18.3.0 (#3807[] @​henryqdineen)
• jsx-no-literals Add elementOverrides option and the ability to ignore this rule on specific elements (#3812[] @​Pearce-Ropion)
• [forward-ref-uses-ref]: add rule for checking ref parameter is added (#3667[] @​NotWoods)

Fixed

• [function-component-definition], [boolean-prop-naming], [jsx-first-prop-new-line], [jsx-props-no-multi-spaces], propTypes: use type args (#3629[] @​HenryBrown0)
• JSX pragma: fail gracefully (#3632[] @​ljharb)
• [jsx-props-no-spreading]: add explicitSpread option to schema (#3799[] @​ljharb)

Changed

• [Tests] add @​typescript-eslint/parser v6 (#3629[] @​HenryBrown0)
• [Tests] add @​typescript-eslint/parser v7 and v8 (#3629[] @​hampustagerud)
• [Docs] [no-danger]: update broken link (#3817[] @​lucasrmendonca)
• [types] add jsdoc type annotations (#3731[] @​y-hsgw)
• [Tests] button-has-type: add test case with spread (#3731[] @​y-hsgw)

#3799: jsx-eslint/eslint-plugin-react#3799

... (truncated)

Changelog

Sourced from eslint-plugin-react's changelog.

[7.37.0] - 2024.09.26

Added

• add type generation (#3830[] @​voxpelli)
• [no-unescaped-entities]: add suggestions (#3831[] @​StyleShit)
• [forbid-component-props]: add allowedForPatterns/disallowedForPatterns options (#3805[] @​Efimenko)
• [no-unstable-nested-components]: add propNamePattern to support custom render prop naming conventions (#3826[] @​danreeves)

Changed

• [readme] flat config example for react 17+ (#3824[] @​GabenGar)

#3831: jsx-eslint/eslint-plugin-react#3831 #3830: jsx-eslint/eslint-plugin-react#3830 #3826: jsx-eslint/eslint-plugin-react#3826 #3824: jsx-eslint/eslint-plugin-react#3824 #3805: jsx-eslint/eslint-plugin-react#3805

7.36.1 - 2024.09.12

Fixed

• [no-is-mounted]: fix logic in method name check (#3821[] @​Mathias-S)
• [jsx-no-literals]: Avoid crashing on valueless boolean props (#3823[] @​reosarevok)

#3823: jsx-eslint/eslint-plugin-react#3823 #3821: jsx-eslint/eslint-plugin-react#3821

7.36.0 - 2024.09.12

Added

• [no-string-refs]: allow this.refs in > 18.3.0 (#3807[] @​henryqdineen)
• [jsx-no-literals] Add elementOverrides option and the ability to ignore this rule on specific elements (#3812[] @​Pearce-Ropion)
• [forward-ref-uses-ref]: add rule for checking ref parameter is added (#3667[] @​NotWoods)

Fixed

• [function-component-definition], [boolean-prop-naming], [jsx-first-prop-new-line], [jsx-props-no-multi-spaces], propTypes: use type args (#3629[] @​HenryBrown0)
• JSX pragma: fail gracefully (#3632[] @​ljharb)
• [jsx-props-no-spreading]: add explicitSpread option to schema (#3799[] @​ljharb)

Changed

• [Tests] add @​typescript-eslint/parser v6 (#3629[] @​HenryBrown0)
• [Tests] add @​typescript-eslint/parser v7 and v8 (#3629[] @​hampustagerud)
• [Docs] [no-danger]: update broken link (#3817[] @​lucasrmendonca)
• [types] add jsdoc type annotations (#3731[] @​y-hsgw)
• [Tests] button-has-type: add test case with spread (#3731[] @​y-hsgw)

#3799: jsx-eslint/eslint-plugin-react#3799 #3632: jsx-eslint/eslint-plugin-react#3632

... (truncated)

Commits

• ec27e20 Update CHANGELOG and bump version
• 0cc5b7a [meta] fix release workflow
• 744135b [readme] flat config example for react 17+
• a1273d5 [New] no-unstable-nested-components: add propNamePattern to support custo...
• 3073214 [New] forbid-component-props: add allowedForPatterns/`disallowedForPatter...
• 95297ed [New] no-unescaped-entities: add suggestions
• 7f3ac1b [New] add type generation
• 4ecf034 [Dev Deps] update eslint-plugin-import, gfm-footnotes
• 9668ee0 [meta] fix release workflow
• 59ef14c Update CHANGELOG and bump version
• Additional commits viewable in compare view

Updates sass from 1.76.0 to 1.79.4

Release notes

Sourced from sass's releases.

Dart Sass 1.79.4

To install Sass 1.79.4, download one of the packages below and add it to your PATH, or see the Sass website for full installation instructions.

Changes

JS API

• Fix a bug where passing green or blue to color.change() for legacy colors would fail.

See the full changelog for changes in earlier releases.

Dart Sass 1.79.3

To install Sass 1.79.3, download one of the packages below and add it to your PATH, or see the Sass website for full installation instructions.

Changes

• Update the $channel parameter in the suggested replacement for color.red(), color.green(), color.blue(), color.hue(), color.saturation(), color.lightness(), color.whiteness(), and color.blackness() to use a quoted string.

See the full changelog for changes in earlier releases.

Dart Sass 1.79.2

To install Sass 1.79.2, download one of the packages below and add it to your PATH, or see the Sass website for full installation instructions.

Changes

• Add a $space parameter to the suggested replacement for color.red(), color.green(), color.blue(), color.hue(), color.saturation(), color.lightness(), color.whiteness(), and color.blackness().

• Update deprecation warnings for the legacy JS API to include a link to relevant documentation.

See the full changelog for changes in earlier releases.

Dart Sass 1.79.1

To install Sass 1.79.1, download one of the packages below and add it to your PATH, or see the Sass website for full installation instructions.

Changes

... (truncated)

Changelog

Sourced from sass's changelog.

1.79.4

JS API

• Fix a bug where passing green or blue to color.change() for legacy colors would fail.

1.79.3

• Update the $channel parameter in the suggested replacement for color.red(), color.green(), color.blue(), color.hue(), color.saturation(), color.lightness(), color.whiteness(), and color.blackness() to use a quoted string.

1.79.2

• Add a $space parameter to the suggested replacement for color.red(), color.green(), color.blue(), color.hue(), color.saturation(), color.lightness(), color.whiteness(), and color.blackness().

• Update deprecation warnings for the legacy JS API to include a link to relevant documentation.

1.79.1

• No user-visible changes.

1.79.0

• Breaking change: Passing a number with unit % to the $alpha parameter of color.change(), color.adjust(), change-color(), and adjust-color() is now interpreted as a percentage, instead of ignoring the unit. For example, color.change(red, $alpha: 50%) now returns rgb(255 0 0 / 0.5).

• Potentially breaking compatibility fix: Sass no longer rounds RGB channels to the nearest integer. This means that, for example, rgb(0 0 1) != rgb(0 0 0.6). This matches the latest version of the CSS spec and browser behavior.

• Potentially breaking compatibility fix: Passing large positive or negative values to color.adjust() can now cause a color's channels to go outside that color's gamut. In most cases this will currently be clipped by the browser and end up showing the same color as before, but once browsers implement gamut mapping it may produce a different result.

• Add support for CSS Color Level 4 [color spaces]. Each color value now tracks its color space along with the values of each channel in that color space. There are two general principles to keep in mind when dealing with new color spaces:

... (truncated)

Commits

• f84e867 Fix JS API legacy SassColor.change (#2368)
• 72612c4 Bump bufbuild/buf-setup-action in /.github/util/initialize (#2363)