chore(deps): update all non-major dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@storybook/testing-library	0.2.0 -> 0.2.2
@testing-library/user-event	14.4.3 -> 14.5.2
@types/lodash-es (source)	4.17.8 -> 4.17.12
@types/react (source)	18.2.20 -> 18.3.3
@types/react-dom (source)	18.2.7 -> 18.3.0
@vitejs/plugin-react (source)	4.0.4 -> 4.3.0
classnames	2.3.2 -> 2.5.1
interactjs (source)	1.10.18 -> 1.10.27
prettier (source)	3.0.1 -> 3.2.5
react (source)	18.2.0 -> 18.3.1
react-dom (source)	18.2.0 -> 18.3.1
rimraf	5.0.1 -> 5.0.7
sass	1.65.1 -> 1.77.2
ts-pattern	5.0.5 -> 5.1.2
typescript (source)	5.1.6 -> 5.4.5

---

Release Notes

storybookjs/testing-library (@​storybook/testing-library)

v0.2.2

Compare Source

🐛 Bug Fix

• Revert: Temporarily fix user-event to 14.4.0 to avoid compatibility issues #​57 (@​yannbf)

Authors: 1

• Yann Braga (@​yannbf)

v0.2.1

Compare Source

🎉 This release contains work from a new contributor! 🎉

Thank you, Valentin Palkovic (@​valentinpalkovic), for all your work!

🐛 Bug Fix

• Temporarily fix user-event to 14.4.0 to avoid compatibility issues #​53 (@​yannbf)

Authors: 2

• Valentin Palkovic (@​valentinpalkovic)
• Yann Braga (@​yannbf)

testing-library/user-event (@​testing-library/user-event)

v14.5.2

Compare Source

Bug Fixes

• remove interop and deep DTL imports (6a3c896)

v14.5.1

Compare Source

Bug Fixes

• incorrect default import from @​testing-library/dom (#​1162) (d7483f0)

v14.5.0

Compare Source

Bug Fixes

• exports: add a named export for userEvent (4019cee), closes #​1146

Features

• types: Add additional type exports for UserEvent & Options (#​1112) (da00e8d)

vitejs/vite-plugin-react (@​vitejs/plugin-react)

v4.3.0

Compare Source

Fix support for React compiler

Don't set retainLines: true when the React compiler is used. This creates whitespace issues and the compiler is modifying the JSX too much to get correct line numbers after that. If you want to use the React compiler and get back correct line numbers for tools like vite-plugin-react-click-to-component to work, you should update your config to something like:

export default defineConfig(({ command }) => {
  const babelPlugins = [['babel-plugin-react-compiler', {}]]
  if (command === 'serve') {
    babelPlugins.push(['@​babel/plugin-transform-react-jsx-development', {}])
  }

  return {
    plugins: [react({ babel: { plugins: babelPlugins } })],
  }
})

Support HMR for class components

This is a long overdue and should fix some issues people had with HMR when migrating from CRA.

v4.2.1

Compare Source

Remove generic parameter on Plugin to avoid type error with Rollup 4/Vite 5 and skipLibCheck: false.

I expect very few people to currently use this feature, but if you are extending the React plugin via api object, you can get back the typing of the hook by importing ViteReactPluginApi:

import type { Plugin } from 'vite'
import type { ViteReactPluginApi } from '@​vitejs/plugin-react'

export const somePlugin: Plugin = {
  name: 'some-plugin',
  api: {
    reactBabel: (babelConfig) => {
      babelConfig.plugins.push('some-babel-plugin')
    },
  } satisfies ViteReactPluginApi,
}

v4.2.0

Compare Source

Update peer dependency range to target Vite 5

There were no breaking change that impacted this plugin, so any combination of React plugins and Vite core version will work.

Align jsx runtime for optimized dependencies

This will only affect people using internal libraries that contains untranspiled JSX. This change aligns the optimizer with the source code and avoid issues when the published source don't have React in the scope.

Reminder: While being partially supported in Vite, publishing TS & JSX outside of internal libraries is highly discouraged.

v4.1.1

Compare Source

• Enable retainLines to get correct line numbers for jsxDev (fix #​235)

v4.1.0

Compare Source

• Add @types/babel__cores to dependencies (fix #​211)
• Improve build perf when not using Babel plugins by lazy loading @babel/core #​212
• Better invalidation message when an export is added & fix HMR for export of nullish values #​215
• Include non-dev jsx runtime in optimizeDeps & support HMR for JS files using the non dev runtime #​224
• The build output now contains a index.d.cts file so you don't get types errors when setting moduleResolution to node16 or nodenext in your tsconfig (we recommend using bundler which is more close to how Vite works)

JedWatson/classnames (classnames)

v2.5.1

Compare Source

• Remove workspaces field from package (#​350)

v2.5.0

Compare Source

• Restore ability to pass a TypeScript interface (#​341)
• Add exports field to package (#​342)

v2.4.0

Compare Source

• Use string concatenation to increase performance thanks Jon Koops (#​336)

v2.3.3

Compare Source

• Fix default export, thanks Remco Haszing (#​301)
• Fix types for read-only arrays, thanks Ben Thompson (#​307)
• Replace README examples with functional-style components, thanks JoeDGit (#​303)

taye/interact.js (interactjs)

v1.10.27

Compare Source

• fix(types): fix issues with skipLibCheck: false

v1.10.26

Compare Source

• fix: improve build; check output for ES2018 compatibility

v1.10.25

Compare Source

• fix: bundle to ES5 syntax

v1.10.24

Compare Source

• chore: generate api docs

v1.10.23

Compare Source

• fix: transform nullish coalescing; fix symbol-tree build

v1.10.22

Compare Source

• fix(actions/gesture): fix error when inertia is enabled for gestures #​995

v1.10.21

Compare Source

• fix(actions/drop): fix regression with drop event targets #​1016

v1.10.20

Compare Source

• fix(types): import plugins for module augmentations #​933

v1.10.19

Compare Source

• fix(core/scope): remove duplicate Interactable super.unset
• fix(utils/pointerExtend): skip all vendor-prefixed props. Close #​978

prettier/prettier (prettier)

v3.2.5

Compare Source

diff

Support Angular inline styles as single template literal (#​15968 by @​sosukesuzuki)

Angular v17 supports single string inline styles.

// Input
@​Component({
  template: `<div>...</div>`,
  styles: `h1 { color: blue; }`,
})
export class AppComponent {}

// Prettier 3.2.4
@&#8203;Component({
  template: `<div>...</div>`,
  styles: `h1 { color: blue; }`,
})
export class AppComponent {}

// Prettier 3.2.5
@&#8203;Component({
  template: `<div>...</div>`,
  styles: `
    h1 {
      color: blue;
    }
  `,
})
export class AppComponent {}

Unexpected embedded formatting for Angular template (#​15969 by @​JounQin)

Computed template should not be considered as Angular component template

// Input
const template = "foobar";

@​Component({
  [template]: `<h1>{{       hello }}</h1>`,
})
export class AppComponent {}

// Prettier 3.2.4
const template = "foobar";

@&#8203;Component({
  [template]: `<h1>{{ hello }}</h1>`,
})
export class AppComponent {}

// Prettier 3.2.5
const template = "foobar";

@&#8203;Component({
  [template]: `<h1>{{       hello }}</h1>`,
})
export class AppComponent {}

Use "json" parser for tsconfig.json by default (#​16012 by @​sosukesuzuki)

In v2.3.0, we introduced "jsonc" parser which adds trialing comma by default.

When adding a new parser we also define how it will be used based on the linguist-languages data.

tsconfig.json is a special file used by TypeScript, it uses .json file extension, but it actually uses the JSON with Comments syntax. However, we found that there are many third-party tools not recognize it correctly because of the confusing .json file extension.

We decide to treat it as a JSON file for now to avoid the extra configuration step.

To keep using the "jsonc" parser for your tsconfig.json files, add the following to your .pretterrc file

{
  "overrides": [
    {
      "files": ["tsconfig.json", "jsconfig.json"],
      "options": {
        "parser": "jsonc"
      }
    }
  ]
}

v3.2.4

Compare Source

diff

Fix incorrect parser inference (#​15947 by @​fisker)

Files like .eslintrc.json were incorrectly formatted as JSONC files.

// Input
prettier --file-info .eslintrc.json
{ "ignored": false, "inferredParser": "jsonc" }

// Prettier 3.2.4
prettier --file-info .eslintrc.json
{ "ignored": false, "inferredParser": "json" }

v3.2.3

Compare Source

diff

Throw errors for invalid code (#​15881 by @​fisker, @​Josh-Cena, @​auvred)

// Input
1++;

// Prettier 3.2.2
1++;

// Prettier 3.2.3
SyntaxError: Invalid left-hand side expression in unary operation (1:1)
> 1 | 1++;
    | ^

// Input
try {} catch (error = 1){}

// Prettier 3.2.2
try {
} catch (error) {}

// Prettier 3.2.3
SyntaxError: Catch clause variable cannot have an initializer. (1:23)
> 1 | try {} catch (error = 1){}
    |                       ^

Fix parser inference (#​15927 by @​fisker)

// Prettier 3.2.2
prettier --file-info tsconfig.json
{ "ignored": false, "inferredParser": "json" }

// Prettier 3.2.3
prettier --file-info tsconfig.json
{ "ignored": false, "inferredParser": "jsonc" }

v3.2.2

Compare Source

diff

Fix crash when parsing template literal CSS in a JSX style tag using a spread attribute (#​15896 by @​eelco)

For example this code would crash before:

<style {...spread}>{`.{}`}</style>

Fix formatting error on optional call expression and member chain (#​15920 by @​sosukesuzuki)

// Input
a(() => {}, c?.d());

// Prettier 3.2.1
TypeError: Cannot read properties of undefined (reading 'type')

// Prettier 3.2.2
a(() => {}, c?.d());

v3.2.1

Compare Source

diff

Fix formatting error on member chain (#​15915 by @​sosukesuzuki)

// Input
test().test2().test2(thing?.something);

// Prettier 3.2.0
TypeError: Cannot read properties of undefined (reading 'type')

// Prettier 3.2.1
test().test2().test2(thing?.something);

v3.2.0

Compare Source

diff

🔗 Release Notes

v3.1.1

Compare Source

diff

Fix config file search (#​15363 by @​fisker)

Previously, we start search for config files from the filePath as a directory, if it happened to be a directory and contains config file, it will be used by mistake.

├─ .prettierrc
└─ test.js         (A directory)
  └─ .prettierrc

// Prettier 3.1.0
await prettier.resolveConfigFile(new URL("./test.js", import.meta.url));
// <CWD>/test.js/.prettierrc

// Prettier 3.1.1
await prettier.resolveConfigFile(new URL("./test.js", import.meta.url));
// <CWD>/.prettierrc

Skip explicitly passed symbolic links with --no-error-on-unmatched-pattern (#​15533 by @​sanmai-NL)

Since Prettier v3, we stopped following symbolic links, however in some use cases, the symbolic link patterns can't be filtered out, and there is no way to prevent Prettier from throwing errors.

In Prettier 3.1.1, you can use --no-error-on-unmatched-pattern to simply skip symbolic links.

Consistently use tabs in ternaries when useTabs is true (#​15662 by @​auvred)

// Input
aaaaaaaaaaaaaaa
	? bbbbbbbbbbbbbbbbbb
	: ccccccccccccccc
	  ? ddddddddddddddd
	  : eeeeeeeeeeeeeee
	    ? fffffffffffffff
	    : gggggggggggggggg;

// Prettier 3.1.0
aaaaaaaaaaaaaaa
	? bbbbbbbbbbbbbbbbbb
	: ccccccccccccccc
	  ? ddddddddddddddd
	  : eeeeeeeeeeeeeee
	    ? fffffffffffffff
	    : gggggggggggggggg;

// Prettier 3.1.1
aaaaaaaaaaaaaaa
	? bbbbbbbbbbbbbbbbbb
	: ccccccccccccccc
		? ddddddddddddddd
		: eeeeeeeeeeeeeee
			? fffffffffffffff
			: gggggggggggggggg;

Improve config file search (#​15663 by @​fisker)

The Prettier config file search performance has been improved by more effective cache strategy.

Fix unstable and ugly formatting for comments in destructuring patterns (#​15708 by @​sosukesuzuki)

// Input
const {
  foo,
  // bar
  // baz
}: Foo = expr;

// Prettier 3.1.0
const {
  foo1,
} // bar
// baz
: Foo = expr;

// Prettier 3.1.0 second output
const {
  foo1, // bar
} // baz
: Foo = expr;

// Prettier 3.1.1
const {
  foo1,
  // bar
  // baz
}: Foo = expr;

Support "Import Attributes" (#​15718 by @​fisker)

TypeScript 5.3 supports the latest updates to the import attributes proposal.

import something from "./something.json" with { type: "json" };

Fix false claim in docs that cursorOffset is incompatible with rangeStart/rangeEnd (#​15750 by @​ExplodingCabbage)

The cursorOffset option has in fact been compatible with rangeStart/rangeEnd for over 5 years, thanks to work by @​ds300. However, Prettier's documentation (including the CLI --help text) continued to claim otherwise, falsely. The documentation is now fixed.

Keep curly braces and from keyword in empty import statements (#​15756 by @​fisker)

// Input
import { } from 'foo';
import { /* comment */ } from 'bar';

// Prettier 3.1.0
import {} from "foo";
import /* comment */ "bar";

// Prettier 3.1.1
import {} from "foo";
import {} from /* comment */ "bar";

Keep empty import attributes and assertions (#​15757 by @​fisker)

// Input
import foo from "foo" with {};
import bar from "bar" assert {};

// Prettier 3.1.0
import foo from "foo";
import bar from "bar";

// Prettier 3.1.1
import foo from "foo" with {};
import bar from "bar" assert {};

v3.1.0

Compare Source

diff

🔗 Release Notes

v3.0.3

Compare Source

diff

Add preferUnplugged: true to package.json (#​15169 by @​fisker and @​so1ve)

Prettier v3 uses dynamic imports, user will need to unplug Prettier when Yarn's PnP mode is enabled, add preferUnplugged: true to package.json, so Yarn will install Prettier as unplug by default.

Support shared config that forbids require() (#​15233 by @​fisker)

If an external shared config package is used, and the package exports don't have require or default export.

In Prettier 3.0.2 Prettier fails when attempt to require() the package, and throws an error.

Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: No "exports" main defined in <packageName>/package.json

Allow argument of require() to break (#​15256 by @​fisker)

// Input
const plugin = require(
  global.STANDALONE
    ? path.join(__dirname, "../standalone.js")
    : path.join(__dirname, "..")
);

// Prettier 3.0.2
const plugin = require(global.STANDALONE
  ? path.join(__dirname, "../standalone.js")
  : path.join(__dirname, ".."));

// Prettier 3.0.3
const plugin = require(
  global.STANDALONE
    ? path.join(__dirname, "../standalone.js")
    : path.join(__dirname, "..")
);

Do not print trailing commas in arrow function type parameter lists in ts code blocks (#​15286 by @​sosukesuzuki)

<!-- Input -->
```ts
const foo = <T>() => {}
```

<!-- Prettier 3.0.2 -->
```ts
const foo = <T,>() => {}
```

<!-- Prettier 3.0.3 -->
```ts
const foo = <T>() => {}
```

Support TypeScript 5.2 using / await using declaration (#​15321 by @​sosukesuzuki)

Support for the upcoming Explicit Resource Management feature in ECMAScript. using / await using declaration

{
   using foo = new Foo();
   await using bar = new Bar();
}

v3.0.2

Compare Source

diff

Break after = of assignment if RHS is poorly breakable AwaitExpression or YieldExpression (#​15204 by @​seiyab)

// Input
const { section, rubric, authors, tags } = await utils.upsertCommonData(mainData);

// Prettier 3.0.1
const { section, rubric, authors, tags } = await utils.upsertCommonData(
  mainData,
);

// Prettier 3.0.2
const { section, rubric, authors, tags } =
  await utils.upsertCommonData(mainData);

Do not add trailing comma for grouped scss comments (#​15217 by @​auvred)

/* Input */
$foo: (
	'property': (),
	// comment 1
	// comment 2
)

/* Prettier 3.0.1 */
$foo: (
  "property": (),
  // comment 1
  // comment 2,
);

/* Prettier 3.0.2 */
$foo: (
  "property": (),
  // comment 1
  // comment 2
);

Print declare and export keywords for nested namespace (#​15249 by @​sosukesuzuki)

// Input
declare namespace abc1.def {}
export namespace abc2.def {}

// Prettier 3.0.1
namespace abc1.def {}
namespace abc2.def {}

// Prettier 3.0.2
declare namespace abc1.def {}
export namespace abc2.def {}

facebook/react (react)

v18.3.1

Compare Source

v18.3.0

Compare Source

facebook/react (react-dom)

v18.3.1

Compare Source

v18.3.0

Compare Source

isaacs/rimraf (rimraf)

v5.0.7

Compare Source

v5.0.6

Compare Source

v5.0.5

Compare Source

v5.0.4

Compare Source

v5.0.3

Compare Source

v5.0.2

Compare Source

sass/dart-sass (sass)

v1.77.2

Compare Source

• Don't emit deprecation warnings for functions and mixins beginning with __.

• Allow user-defined functions whose names begin with _ and otherwise look
  like vendor-prefixed functions with special CSS syntax.

Command-Line Interface

• Properly handle the --silence-deprecation flag.

• Handle the --fatal-deprecation and --future-deprecation flags for
  --interactive mode.

v1.77.1

Compare Source

• Fix a crash that could come up with importers in certain contexts.

v1.77.0

Compare Source

• Don't throw errors for at-rules in keyframe blocks.

v1.76.0

Compare Source

• Throw errors for misplaced statements in keyframe blocks.

• Mixins and functions whose names begin with -- are now deprecated for
  forwards-compatibility with the in-progress CSS functions and mixins spec.
  This deprecation is named css-function-mixin.

v1.75.0

Compare Source

• Fix a bug in which stylesheet canonicalization could be cached incorrectly
  when custom importers or the Node.js package importer made decisions based on
  the URL of the containing stylesheet.

JS API

• Allow importer to be passed without url in StringOptionsWithImporter.

v1.74.1

Compare Source

• No user-visible changes.

v1.72.0

Compare Source

• Support adjacent /s without whitespace in between when parsing plain CSS
  expressions.

• Allow the Node.js pkg: importer to load Sass stylesheets for package.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.

v1.71.1

Compare Source

Command-Line Interface

• Ship the musl Linux release with the proper Dart executable.

JavaScript API

• Export the NodePackageImporter class in ESM mode.

• Allow NodePackageImporter to locate a default directory even when the
  entrypoint is an ESM module.

Dart API

• Make passing a null argument to NodePackageImporter() a static error rather
  than just a runtime error.

Embedded Sass

• In the JS Embedded Host, properly install the musl Linux embedded compiler
  when running on musl Linux.

v1.71.0

Compare Source

For more information about pkg: importers, see the
announcement on the Sass blog.

Command-Line Interface

• Add a --pkg-importer flag to enable built-in pkg: importers. Currently
  this only supports the Node.js package resolution algorithm, via
  --pkg-importer=node. For example, @use "pkg:bootstrap" will load
  node_modules/bootstrap/scss/bootstrap.scss.

JavaScript API

• Add a NodePackageImporter importer that can be passed to the importers
  option. This loads files using the pkg: URL scheme according to the Node.js
  package resolution algorithm. For example, @use "pkg:bootstrap" will load
  node_modules/bootstrap/scss/bootstrap.scss. The constructor takes a single
  optional argument, which indicates the base directory to use when locating
  node_modules directories. It defaults to
  path.dirname(require.main.filename).

Dart API

• Add a NodePackageImporter importer that can be passed to the importers
  option. This loads files using the pkg: URL scheme according to the Node.js
  package resolution algorithm. For example, @use "pkg:bootstrap" will load
  node_modules/bootstrap/scss/bootstrap.scss. The constructor takes a single
  argument, which indicates the base directory to use when locating
  node_modules directories.

v1.70.0

Compare Source

JavaScript API

• Add a sass.initCompiler() function that returns a sass.Compiler object
  which supports compile() and compileString() methods with the same API as
  the global Sass object. On the Node.js embedded host, each sass.Compiler
  object uses a single long-lived subprocess, making compiling multiple
  stylesheets much more efficient.

• Add a sass.initAsyncCompiler() function that returns a sass.AsyncCompiler
  object which supports compileAsync() and compileStringAsync() methods with
  the same API as the global Sass object. On the Node.js embedded host, each
  sass.AsynCompiler object uses a single long-lived subprocess, making
  compiling multiple stylesheets much more efficient.

Embedded Sass

• Support the CompileRequest.silent field. This allows compilations with no
  logging to avoid unnecessary request/response cycles.

• The Dart Sass embedded compiler now reports its name as "dart-sass" rather
  than "Dart Sass", to match the JS API's info field.

v1.69.7

Compare Source

Embedded Sass

• In the JS Embedded Host, properly install the x64 Dart Sass executable on
  ARM64 Windows.

v1.69.6

Compare Source

• Produce better output for numbers with complex units in meta.inspect() and
  debugging messages.

• Escape U+007F DELETE when serializing strings.

• When generating CSS error messages to display in-browser, escape all code
  points that aren't in the US-ASCII region. Previously only code points U+0100
  LATIN CAPITAL LETTER A WITH MACRON were escaped.

• Provide official releases for musl LibC and for Android.

• Don't crash when running meta.apply() in asynchronous mode.

JS API

• Fix a bug where certain exceptions could produce SourceSpans that didn't
  follow the documented SourceSpan API.

v1.69.5

Compare Source

JS API

• Compatibility with Node.js 21.0.0.

v1.69.4

Compare Source

• No user-visible changes.

v1.69.3

Compare Source

Embedded Sass

• Fix TypeScript type locations in package.json.

v1.69.2

Compare Source

JS API

• Fix a bug where Sass crashed when running in the browser if there was a global
  variable named process.

v1.69.1

Compare Source

• No user-visible changes.

v1.69.0

Compare Source

• Add a meta.get-mixin() function that returns a mixin as a first-class Sass
  value.

• Add a meta.apply() mixin that includes a mixin value.

• Add a meta.module-mixins() function which returns a map from mixin names in
  a module to the first-class mixins that belong to those names.

• Add a meta.accepts-content() function which returns whether or not a mixin
  value can take a content block.

• Add support for the relative color syntax from CSS Color 5. This syntax
  cannot be used to create Sass color values. It is always emitted as-is in the
  CSS output.

Dart API

• Deprecate Deprecation.calcInterp since it was never actually emitted as a
  deprecation.

Embedded Sass

• Fix a rare race condition where the embedded compiler could freeze when a
  protocol error was immediately followed by another request.

v1.68.0

Compare Source

• Fix the source spans associated with the abs-percent deprecation.

JS API

• Non-filesystem importers can now set the nonCanonicalScheme field, which
  declares that one or more URL schemes (without :) will never be used for
  URLs returned by the canonicalize() method.

• Add a containingUrl field to the canonicalize() and findFileUrl()
  methods of importers, which is set to the canonical URL of the stylesheet that
  contains the current load. For filesystem importers, this is always set; for
  other importers, it's set only if the current load has no URL scheme, or if
  its URL scheme is declared as non-canonical by the importer.

Dart API

• Add AsyncImporter.isNonCanonicalScheme, which importers (async or sync) can
  use to indicate that a certain URL scheme will never be used for URLs returned
  by the canonicalize() method.

• Add AsyncImporter.containingUrl, which is set during calls to the
  canonicalize() method to the canonical URL of the stylesheet that contains
  the current load. This is set only if the current load has no URL scheme, or
  if its URL scheme is declared as non-canonical by the importer.

Embedded Sass

• The CalculationValue.interpolation field is deprecated and will be removed
  in a future version. It will no longer be set by the compiler, and if the host
  sets it it will be treated as equivalent to CalculationValue.string except
  that "(" and ")" will be added to the beginning and end of the string
  values.

• Properly include TypeScript types in the sass-embedded package.

v1.67.0

Compare Source

• All functions defined in CSS Values and Units 4 are now once again parsed as
  calculation objects: round(), mod(), rem(), sin(), cos(), tan(),
  asin(), acos(), atan(), atan2(), pow(), sqrt(), hypot(),
  log(), exp(), abs(), and sign().

  Unlike in 1.65.0, function calls are not locked into being parsed as
  calculations or plain Sass functions at parse-time. This means that
  user-defined functions will take precedence over CSS calculations of the same
  name. Although the function names calc() and clamp() are still forbidden,
  users may continue to freely define functions whose names overlap with other
  CSS calculations (including abs(), min(), max(), and round() whose
  names overlap with global Sass functions).

• Breaking change: As a consequence of the change in calculation parsing
  described above, calculation functions containing interpolation are now parsed
  more strictly than before. However, almost all interpolations that would
  have produced valid CSS will continue to work. The only exception is
  #{$variable}% which is not valid in Sass and is no longer valid in
  calculations. Instead of this, either use $variable directly and ensure it
  already has the % unit, or write ($variable * 1%).

• Potentially breaking bug fix: The importer used to load a given file is no
  longer used to load absolute URLs that appear in that file. This was
  unintented behavior that contradicted the Sass specification. Absolute URLs
  will now correctly be loaded only from the global importer list. This applies
  to the modern JS API, the Dart API, and the embedded protocol.

Embedded Sass

• Substantially improve the embedded compiler's performance when compiling many
  files or files that require many importer or function call round-trips with
  the embedded host.

v1.66.1

Compare Source

JS API

• Fix a bug where Sass compilation could crash in strict mode if passed a
  callback that threw a string, boolean, number, symbol, or bignum.

v1.66.0

Compare Source

• Breaking change: Drop support for the additional CSS calculations defined
  in CSS Values and Units 4. Custom Sass functions whose names overlapped with
  these new CSS functions were being parsed as CSS calculations instead, causing
  an unintentional breaking change outside our normal [compatibility policy] for
  CSS compatibility changes.

  Support will be added again in a future version, but only after Sass has
  emitted a deprecation warning for all functions that will break for at least
  three months prior to the breakage.

gvergnaud/ts-pattern (ts-pattern)

v5.1.2

Compare Source

v5.1.1

Compare Source

What's Changed

• Fix(P.nonNullable): narrowing of unions of objects by @​gvergnaud in https://github.com/gvergnaud/ts-pattern/pull/237

Full Changelog: gvergnaud/ts-pattern@v5.1.0...v5.1.1

v5.1.0

Compare Source

New features

P.nonNullable wildcard

Add a new P.nonNullable pattern that will match any value except null or undefined.

import { match, P } from 'ts-pattern';

const input = null;

const output = match<number | null | undefined>(input)
  .with(P.nonNullable, () => 'it is a number!')
  .otherwise(() => 'it is either null or undefined!');

console.log(output);
// => 'it is either null or undefined!'

Closes #​60 #​154 #​190 and will be a work-around for #​143.

What's Changed

• feat: Add P.nonNullable patterns by @​gvergnaud in https://github.com/gvergnaud/ts-pattern/pull/229

Full Changelog: gvergnaud/ts-pattern@v5.0.8...v5.1.0

v5.0.8

[Compare Source](https://togithub.com/gvergnaud/ts-pattern/compare/d0d07c9617f8bb9699c97c05c8

---

Configuration

📅 Schedule: Branch creation - "before 4am on the first day of the month" in timezone Europe/Berlin, 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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

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