fix(deps): update npm

[renovate]

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Confidence
@esbuild/linux-arm64	^0.27.0 → ^0.28.0
@sveltejs/vite-plugin-svelte (source)	7.0.0 → 7.3.0
@tailwindcss/typography	0.5.19 → 0.5.20
lightningcss-darwin-arm64	1.32.0 → 1.33.0
lightningcss-darwin-x64	1.32.0 → 1.33.0
lightningcss-linux-arm64-gnu	1.32.0 → 1.33.0
lightningcss-linux-arm64-musl	1.32.0 → 1.33.0
lightningcss-linux-x64-gnu	1.32.0 → 1.33.0
lightningcss-win32-x64-msvc	1.32.0 → 1.33.0
positron-components	1.14.1 → 1.15.2
prettier (source)	3.8.1 → 3.9.6
prettier-plugin-svelte	3.5.1 → 3.5.2
prettier-plugin-tailwindcss	^0.7.2 → ^0.8.0
svelte-check	4.4.5 → 4.7.5
tailwind-variants	3.2.2 → 3.3.1
typescript (source)	6.0.2 → 6.0.3
zod (source)	4.3.6 → 4.4.3

---

Release Notes

evanw/esbuild (@​esbuild/linux-arm64)

v0.28.2

Compare Source

• Fix tree shaking bug due to TypeScript import alias (#​4507)

  This release fixes a bug that could cause esbuild to incorrectly tree-shake imports that are used in a TypeScript type alias under certain circumstances. Affected code uses a TypeScript-specific import assignment and looks something like this:

  import Base from './dep.js';
  import Alias = Base.SomeType;

• Fix CSS minification bug involving & (#​4497)

  This release fixes a bug where esbuild's CSS minifier incorrectly removed a & when it was unsafe to do so. Here is an example:

  /* Original code */
  .a .b {
    & .b:not(& .c) {
      color: red;
    }
  }
  
  /* Old output (with --minify) */
  .a .b{.b:not(& .c){color:red}}
  
  /* New output (with --minify) */
  .a .b{& .b:not(& .c){color:red}}

  This should match <span class="a"><span class="b"><span class="b">yes</span></span></span> but not <span class="a"><span class="b">no</span></span>. The old output incorrectly matched both.

• Avoid overwriting input files without --allow-overwrite (#​4484)

  For example: esbuild input.js --outfile=input.js tells esbuild to overwrite input.js with the output of running esbuild on it. This was supposed to already be prevented by default, but it accidentally regressed in version 0.17.0 and apparently didn't have any test coverage. The error message was being printed but the input file was still being overwritten. Oops.

  This release puts the original behavior back. With this release, esbuild should now actually avoid overwriting input files unless --allow-overwrite is explicitly present. This is done by not writing out any files when a build error is encountered.

• Fix incorrect code generated when using top-level await (#​4498)

  Previously esbuild could generate code containing a syntax error in complex scenarios involving top-level await used in a dependency cycle. The problem was a missing async on one or more module wrapper closures. With this release, esbuild now uses a fixed-point iteration algorithm to correctly annotate all dependencies in the cycle as needing an async module wrapper.

• Fix a minification bug with lowered logical assignment operators (#​4508)

  This release fixes a bug that could cause esbuild to generate incorrect code for logical assignment operators when lowering them to an older target environment. Specifically the lowering process requires duplicating the left-hand side, but esbuild incorrectly failed to count the duplicate as a new usage when the left-hand side is an identifier. That then caused the minifier to believe that the left-hand side was only used once and could attempt to incorrectly inline an initializer into the first usage. This bug has now been fixed:

  // Original code
  function foo() {
    let x
    bar(x ||= {})
  }
  
  // Old output (with --minify-syntax --target=es6)
  function foo() {
    bar(void 0 || (x = {}));
  }
  
  // New output (with --minify-syntax --target=es6)
  function foo() {
    let x;
    bar(x || (x = {}));
  }

• Fix a potential deadlock when the JavaScript API is used incorrectly (#​4503, #​4506)

  The JavaScript API runs the native esbuild executable as a long-lived child process and communicates with it over stdin/stdout/stderr. Each API request is asynchronous and the executable stays open as long as it has work to do, which is as long as either stdin is still open (meaning there may be more API requests) or there are currently requests being processed.

  Previously esbuild's tracking of outstanding API requests missed decrementing a reference count in an edge case where esbuild's JavaScript API was used incorrectly and the API request returned an error. This could in some cases cause esbuild's native executable to exit with an error message about a deadlock. This release fixes the reference counting bug.

  This fix was submitted by @​ZuBB.

• Handle target collisions (#​4509)

  It's possible to specify the same target engine multiple times, such as with --target=chrome1,chrome99. This edge case wasn't anticipated and previously took the last version for the duplicated target engine instead of the minimum version (so chrome99 in this case instead of chrome1). With this release, esbuild will now pick the minimum version between all duplicated target engines.

• Force .mp3 files to use the audio/mpeg MIME type (#​4485)

  MIME type detection for esbuild's data URLs uses Go's built-in MIME type detection, which is based on the MIME sniffing standard. This works correctly for MP3 files that start with the byte sequence ID3, which is commonly the case. However, it's possible to construct valid MP3 files that do not start with ID3, and that perhaps Go's built-in MIME type detection doesn't implement the "Signature for MP3 without ID3" part of the algorithm. This results in some .mp3 files incorrectly using the application/octet-stream MIME type instead of audio/mpeg. With this release, esbuild will now always use the audio/mpeg MIME type for files ending in .mp3.

• Add a new TypeScript syntax warning

  TypeScript 7 turned some previously-valid TypeScript syntax into a syntax error because it was confusing. TypeScript 6 accepts 1 + 2 as number * 3 as valid syntax but confusingly converts it to (1 + 2) * 3 instead of the more intuitive conversion to 1 + (2 * 3). This syntax is now an error in TypeScript 7+. With this release, esbuild will now warn about the use of this syntax:

  ▲ [WARNING] Operator "*" should not directly follow a TypeScript type cast after the "+" operator [confusing-typescript-cast]
  
      example.ts:1:28:
        1 │ console.log(1 + 2 as number * 3)
          ╵                             ^
  
    This is a syntax error in newer versions of TypeScript because the type cast has unintuitive
    precedence in this case. Surround the inner expression in parentheses to silence this warning:
  
      example.ts:1:12:
        1 │ console.log(1 + 2 as number * 3)
          │             ~~~~~~~~~~~~~~~
          ╵             (             )

  See microsoft/TypeScript#63527 for more information.

• Add support for formatting errors for Visual Studio (#​4460)

  Visual Studio has a specific style that it expects log messages to be in for them to show up in the UI when esbuild is run as a custom build step. The current log style that esbuild uses doesn't conform to this specific style.

  With this release, esbuild has a new log style for Visual Studio (and other tools in the MSBuild ecosystem) that can be enabled with --log-style=visualstudio. Here is an example log message in this style:

  $ esbuild example.ts --log-style=visualstudio
  /Users/evan/dev/esbuild/example.ts(1,29): warning ES0010: Operator "*" should not directly follow a TypeScript type cast after the "+" operator
  

  This log style is also available via the JS and Go APIs, and can now be used with the existing formatMessages API.

• Fix a bug with CSS gamut mapping (#​4488)

  Due to a typo, the fallback colors generated for CSS colors outside of the sRGB gamut weren't correct. This release fixes the generated colors to use the intended algorithm.

  This fix was submitted by @​chatman-media.

v0.28.1

Compare Source

• Disallow \ in local development server HTTP requests (GHSA-g7r4-m6w7-qqqr)

  This release fixes a security issue where HTTP requests to esbuild's local development server could traverse outside of the serve directory on Windows using a \ backslash character. It happened due to the use of Go's path.Clean() function, which only handles Unix-style / characters. HTTP requests with paths containing \ are no longer allowed.

  Thanks to @​dellalibera for reporting this issue.

• Add integrity checks to the Deno API (GHSA-gv7w-rqvm-qjhr)

  The previous release of esbuild added integrity checks to esbuild's npm install script. This release also adds integrity checks to esbuild's Deno install script. Now esbuild's Deno API will also fail with an error if the downloaded esbuild binary contains something other than the expected content.

  Note that esbuild's Deno API installs from registry.npmjs.org by default, but allows the NPM_CONFIG_REGISTRY environment variable to override this with a custom package registry. This change means that the esbuild executable served by NPM_CONFIG_REGISTRY must now match the expected content.

  Thanks to @​sondt99 for reporting this issue.

• Avoid inlining using and await using declarations (#​4482)

  Previously esbuild's minifier sometimes incorrectly inlined using and await using declarations into subsequent uses of that declaration, which then fails to dispose of the resource correctly. This bug happened because inlining was done for let and const declarations by avoiding doing it for var declarations, which no longer worked when more declaration types were added. Here's an example:

  // Original code
  {
    using x = new Resource()
    x.activate()
  }
  
  // Old output (with --minify)
  new Resource().activate();
  
  // New output (with --minify)
  {using e=new Resource;e.activate()}

• Fix module evaluation when an error is thrown (#​4461, #​4467)

  If an error is thrown during module evaluation, esbuild previously didn't preserve the state of the module for subsequent module references. This was observable if import() or require() is used to import a module multiple times. The thrown error is supposed to be thrown by every call to import() or require(), not just the first. With this release, esbuild will now throw the same error every time you call import() or require() on a module that throws during its evaluation.

• Fix some edge cases around the new operator (#​4477)

  Previously esbuild incorrectly printed certain edge cases involving complex expressions inside the target of a new expression (specifically an optional chain and/or a tagged template literal). The generated code for the new target was not correctly wrapped with parentheses, and either contained a syntax error or had different semantics. These edge cases have been fixed so that they now correctly wrap the new target in parentheses. Here is an example of some affected code:

  // Original code
  new (foo()`bar`)()
  new (foo()?.bar)()
  
  // Old output
  new foo()`bar`();
  new (foo())?.bar();
  
  // New output
  new (foo())`bar`();
  new (foo()?.bar)();

• Fix renaming of nested var declarations (#​4471)

  This release fixes a bug where var declarations in nested scopes that are hoisted up to module scope were not correctly being renamed during bundling. That could previously lead to name collisions when minification was disabled, which could potentially cause a behavior change. The bug has been fixed so that these hoisted declarations are now considered to be module-level symbols during the name collision avoidance pass.

• Emit var instead of const for certain TypeScript-only constructs for ES5 (#​4448)

  While esbuild doesn't generally support converting const to var for ES5 due to nested scoping rules (which is currently a build-time error), esbuild previously incorrectly converted TypeScript-only import assignment constructs into a const declaration even when targeting ES5. With this release, esbuild will now use var for this case instead:

  // Original code
  import x = require('y')
  
  // Old output (with --target=es5)
  const x = require("y");
  
  // New output (with --target=es5)
  var x = require("y");

v0.28.0

Compare Source

• Add support for with { type: 'text' } imports (#​4435)

  The import text proposal has reached stage 3 in the TC39 process, which means that it's recommended for implementation. It has also already been implemented by Deno and Bun. So with this release, esbuild also adds support for it. This behaves exactly the same as esbuild's existing text loader. Here's an example:

  import string from './example.txt' with { type: 'text' }
  console.log(string)

• Add integrity checks to fallback download path (#​4343)

  Installing esbuild via npm is somewhat complicated with several different edge cases (see esbuild's documentation for details). If the regular installation of esbuild's platform-specific package fails, esbuild's install script attempts to download the platform-specific package itself (first with the npm command, and then with a HTTP request to registry.npmjs.org as a last resort).

  This last resort path previously didn't have any integrity checks. With this release, esbuild will now verify that the hash of the downloaded binary matches the expected hash for the current release. This means the hashes for all of esbuild's platform-specific binary packages will now be embedded in the top-level esbuild package. Hopefully this should work without any problems. But just in case, this change is being done as a breaking change release.

• Update the Go compiler from 1.25.7 to 1.26.1

  This upgrade should not affect anything. However, there have been some significant internal changes to the Go compiler, so esbuild could potentially behave differently in certain edge cases:

  • It now uses the new garbage collector that comes with Go 1.26.
  • The Go compiler is now more aggressive with allocating memory on the stack.
  • The executable format that the Go linker uses has undergone several changes.
  • The WebAssembly build now unconditionally makes use of the sign extension and non-trapping floating-point to integer conversion instructions.

  You can read the Go 1.26 release notes for more information.

sveltejs/vite-plugin-svelte (@​sveltejs/vite-plugin-svelte)

v7.3.0

Compare Source

Minor Changes

• feat: pass environment to dynamicCompileOptions (#​1386)

Patch Changes

• fix: don't log inline config when encountering unexpected options (#​1376)

v7.2.0

Compare Source

Minor Changes

• feat(inspector): add a context menu with current component stack (#​1370)

v7.1.4

Compare Source

Patch Changes

• fix: enforce ltr styles for inspector (#​1324)

v7.1.3

Compare Source

Patch Changes

• fix: ensure the inspector is injected into the client correctly for Vite+ projects (#​1355)

v7.1.2

Compare Source

Patch Changes

• fix: correctly resolve compiled CSS on the server for dependencies with Svelte files (#​1342)

v7.1.1

Compare Source

Patch Changes

• fix: pass typescript.onlyRemoveTypeImports to transformWithOxc in vitePreprocess so that value imports are not dropped when they are only referenced in Svelte template markup (#​1326)

• fix: correctly resolve compiled CSS for optimised Svelte dependencies on the server (#​1336)

v7.1.0

Compare Source

Minor Changes

• feat: enable optimizer for server environments during dev (#​1328)

tailwindlabs/tailwindcss-typography (@​tailwindcss/typography)

v0.5.20

Compare Source

Fixed

• Support installing with stable versions of Tailwind CSS v4 (#​424)

parcel-bundler/lightningcss (lightningcss-darwin-arm64)

v1.33.0

Compare Source

Added

• Add support for ::highlight by @​lucasweng in #​970
• Add support for @​position-try at-rule by @​mattcosta7 in #​1238
  #​851
• Add support for ::search-text and :current::search-text (#​1212) by @​lucinadin in #​1213
• Collapse light-dark(x, x) to x by @​cscnk52 in #​1183
• Supports :target-before/after/current pseudo-class by @​yisibl in #​1185
• Support for the alpha() relative color function by @​yisibl in #​1266

Fixed

• Print unknown at-rules in the same location by @​RobinMalfait in #​1233
• Fix #rrggbbaa support on older versions of android by @​fkeiler in #​1198
• Replace atty with std::io::IsTerminal by @​fkeiler in #​1197
• Bump dependencies (cssparser, const-str) by @​noahbald in #​1200
• Fix minification of negative scientific notation dimensions by @​ssssota in #​1192
• Change serde attribute to be conditional for ResolveResult enum File variant by @​FlorianDevP in #​1251
• Add external to return type of resolve by @​sapphi-red in #​1261

Profiidev/positron_components (positron-components)

v1.15.2

Compare Source

Bug Fixes

• updated typescript (432e174)
• wider deps pinning (8e647c9)

v1.15.1

Compare Source

Bug Fixes

• websocket reexport (9be594c)

v1.15.0

Compare Source

Features

• added clean table (70e16ea)
• added form components (5c13f3f)
• added sidebar components (b349323)
• added websocket connection (415fd6e)

Bug Fixes

• added option for href for table actions (2b4adcf)

v1.14.4

Compare Source

Bug Fixes

• base form recreation (654e71c)

v1.14.3

Compare Source

Bug Fixes

• deps (ff6fdac)

v1.14.2

Compare Source

Bug Fixes

• removed unused deps (1ce3ec5)

prettier/prettier (prettier)

v3.9.6

Compare Source

v3.9.5

Compare Source

diff

Markdown: Cap ordered list mark at 999,999,999 (#​19351 by @​tats-u)

CommonMark parsers only support ordered list item numbers up to 999,999,999.

With this change, Prettier now caps the ordered list item number at 999,999,999 to ensure that the output is correctly parsed as an ordered list by CommonMark parsers. Numbers larger than 999,999,999 are not parsed as list item numbers and are left unchanged in the output:

<!-- Input -->
999999998. text
999999998. text
999999998. text
999999998. text

1234567890123456789012) text

<!-- Prettier 3.9.4 -->
999999998. text
999999999. text
1000000000. text
1000000001. text

1234567890123456789012) text

<!-- Prettier 3.9.5 -->
999999998. text
999999999. text
999999999. text
999999999. text

1234567890123456789012) text

Markdown: Avoid corrupting empty link with title (#​19487 by @​andersk)

Do not remove <> from an inline link or image with an empty URL and a title, as this removal would change its interpretation.

<!-- Input -->
[link](<> "title")

<!-- Prettier 3.9.4 -->
[link]( "title")

<!-- Prettier 3.9.5 -->
[link](<> "title")

Less: Remove extra spaces after [ in map lookups (#​19503 by @​kovsu)

// Input
.foo {
  color: #theme[ primary];
  color: #theme[@name];
  color: #theme[@@name];
}

// Prettier 3.9.4
.foo {
  color: #theme[ primary];
  color: #theme[ @name];
  color: #theme[ @@name];
}

// Prettier 3.9.5
.foo {
  color: #theme[primary];
  color: #theme[@name];
  color: #theme[@@name];
}

CSS: Prevent addition space in type() with + (#​19516 by @​bigandy)

This fixes the addition space before + in CSS type() declaration. For example type(<number>+) was being converted into type(<number> +) which is invalid CSS and does not work.

/* Input */
div {
  border-radius: attr(br type(<length>+));
}

/* Prettier 3.9.4 */
div {
  border-radius: attr(br type(<length> +));
}

/* Prettier 3.9.5 */
div {
  border-radius: attr(br type(<length>+));
}

Less: Remove spaces between merge markers and colons (#​19517 by @​kovsu)

// Input
a {
  box-shadow  +  : 0 0 1px #​000;
}

// Prettier 3.9.4
a {
  box-shadow+  : 0 0 1px #​000;
}

// Prettier 3.9.5
a {
  box-shadow+: 0 0 1px #​000;
}

Markdown: Preserve wiki links with aliases (#​19527 by @​kovsu)

<!-- Input -->
[[Foo:Bar]]

<!-- Prettier 3.9.4 -->
[[Foo]]

<!-- Prettier 3.9.5 -->
[[Foo:Bar]]

TypeScript: Fix comments being dropped on shorthand type import/export specifiers (#​19565 by @​kirkwaiblinger)

// Input
export { type /* comment */ T } from "foo";
import { type /* comment */ T } from "foo";

// Prettier 3.9.4
Error: Comment "comment" was not printed. Please report this error!

// Prettier 3.9.5
export { type /* comment */ T } from "foo";
import { type /* comment */ T } from "foo";

Miscellaneous: Preserving comments' placement property (#​19567 by @​Janther)

Prettier@​3.9.0 deleted an undocumented property on comments, which was already used by plugins, comment.placement is now available again after comment attach.

Flow: Stop enforcing empty module declaration to break (#​19568 by @​fisker)

// Input
declare module "foo" {}

// Prettier 3.9.4
declare module "foo" {
}

// Prettier 3.9.5
declare module "foo" {}

Angular: Support expression for exhaustive typechecking (#​19571 by @​fisker)

<!-- Input -->
@switch (state.mode) {
  @default never(state);
}

<!-- Prettier 3.9.4 -->
@switch (state.mode) {
  @default never;
}

<!-- Prettier 3.9.5 -->
@switch (state.mode) {
  @default never(state);
}

TypeScript: Ignore comments inside mapped type when checking type parameter comments (#​19572 by @​fisker)

// Input
foo<{
  // comment
  [key in keyof Foo]: number
}>();

// Prettier 3.9.4
foo<
  {
    // comment
    [key in keyof Foo]: number;
  }
>();

// Prettier 3.9.5
foo<{
  // comment
  [key in keyof Foo]: number;
}>();

Less: Fix adjacent block comments being corrupted (#​19574 by @​kovsu)

// Input
/* a *//* b */
/* a */* {
  color: red;
}

// Prettier 3.9.4
/* a */
/* b */
/* a * {
  color: red;
}

// Prettier 3.9.5
/* a */ /* b */
/* a */
* {
  color: red;
}

JavaScript: Handle dangling comments in SwitchStatement (#​19581 by @​fisker)

// Input
switch (foo) {
 // comment
}

// Prettier 3.9.4
switch (
  foo
  // comment
) {
}

// Prettier 3.9.5
switch (foo) {
  // comment
}

TypeScript: Remove space in comment-only object type (#​19583 by @​fisker)

// Input
var foo = {
  /* comment */
};
type Foo = {
  /* comment */
};

// Prettier 3.9.4
var foo = {/* comment */};
type Foo = { /* comment */ };

// Prettier 3.9.5
var foo = {/* comment */};
type Foo = {/* comment */};

v3.9.4

Compare Source

v3.9.3

Compare Source

v3.9.2

Compare Source

v3.9.1

Compare Source

v3.9.0

Compare Source

diff

🔗 Release Notes

v3.8.5

Compare Source

v3.8.4

Compare Source

diff

Markdown: Fix blank lines between list items and nested sub-lists being removed in Markdown/MDX (#​17746 by @​byplayer)

Prettier was removing blank lines between list items and their nested sub-lists, converting loose lists into tight lists and changing their semantic meaning.

<!-- Input -->
- a

  - b

- c

  - d

<!-- Prettier 3.8.3 -->
- a
  - b
- c
  - d

<!-- Prettier 3.8.4 -->
- a

  - b

- c

  - d

v3.8.3

Compare Source

diff

SCSS: Prevent trailing comma in if() function (#​18471 by @​kovsu)

// Input
$value: if(sass(false): 1; else: -1);

// Prettier 3.8.2
$value: if(
  sass(false): 1; else: -1,
);

// Prettier 3.8.3
$value: if(sass(false): 1; else: -1);

v3.8.2

Compare Source

diff

Angular: Support Angular v21.2 (#​18722, #​19034 by @​fisker)

Exhaustive typechecking with @default never;

<!-- Input -->
@switch (foo) {
  @case (1) {}
  @default never;
}

<!-- Prettier 3.8.1 -->
SyntaxError: Incomplete block "default never". If you meant to write the @ character, you should use the "&#&#8203;64;" HTML entity instead. (3:3)

<!-- Prettier 3.8.2 -->
@switch (foo) {
  @case (1) {}
  @default never;
}

arrow function and instanceof expressions.

<!-- Input -->
@let fn = (a) =>        a?    1:2;

{{ fn ( a         instanceof b)}}

<!-- Prettier 3.8.1 -->
@let fn = (a) =>        a?    1:2;

{{ fn ( a         instanceof b)}}

<!-- Prettier 3.8.2 -->
@let fn = (a) => (a ? 1 : 2);

{{ fn(a instanceof b) }}

sveltejs/prettier-plugin-svelte (prettier-plugin-svelte)

v3.5.2

Compare Source

• (fix) Preserve non-breaking spaces
• (fix) handle comments in bind: get/set tuple
• (fix) handle computed properties in e.g. {#each} blocks

tailwindlabs/prettier-plugin-tailwindcss (prettier-plugin-tailwindcss)

v0.8.1

Compare Source

Fixed

• Don't remove escape sequences when sorting classes in JavaScript string literals, which could produce invalid code in Vue attribute expressions (#​461)
• Restore class sorting in Svelte markup and dynamic class={...} expressions when using prettier-plugin-svelte v4 (#​462)

v0.8.0

Compare Source

Changed

• Require at least Prettier 3.7.x (#​420)

Added

• Export public sorting APIs to /sorter (#​438)

Fixed

• Remove top-level await (#​420)
• Improve load-time performance (#​420)
• Improve config resolution caching with directory-based cache (#​432)
• Load compatible plugins on demand and tighten plugin detection (#​437)
• Load v3/v4 modules only when needed (#​439)
• Remove recast/ast-types deps and optimize dynamic JS attribute handling (#​440)
• Remove unused deps (#​441)
• Use the plugin that has already been imported rather than dynamically importing it again (#​442)
• Skip visiting non-node children (#​443)
• Optimize whitespace-only class detection (#​429)
• Fix v3 config loading with Jiti re-exports (#​448)
• Collapse whitespace in template literals with adjacent quasis (#​427)
• Improve canCollapseWhitespaceIn handling for "tailwindPreserveWhitespace": true (#​428)

v0.7.4

Compare Source

Same as v0.7.2, since v0.7.3 contained breaking changes.

v0.7.3

Compare Source

Changed

• Remove top-level await (#​420)
• Improve load-time performance (#​420)

Fixed

• Collapse whitespace in template literals with adjacent quasis (#​427)

sveltejs/language-tools (svelte-check)

v4.7.5

Compare Source

Patch Changes

• fix: prevent silent error during start-up caused by unhandled promise (#​3096)

• Updated dependencies [1df53d8]:

  • @​sveltejs/load-config@​0.2.2

v4.7.4

Compare Source

Patch Changes

• fix: support TypeScript 7 Stable under npm alias (#​3073)

v4.7.3

Compare Source

Patch Changes

• feat: zero-config +error.svelte props (#​3076)

v4.7.2

Compare Source

Patch Changes

• fix: resolve tsgo bin path with package.json (#​3074)

• fix: report tsconfig errors in --tsgo-experimental-api (#​3070)

v4.7.1

Compare Source

Patch Changes

• fix: correctly parse --tsgo-experimental-api flag (#​3067)

v4.7.0

Compare Source

Minor Changes

• feat: add --config option (#​3066)

• feat: svelte-check tsgo support with experimental api (#​3036)

Patch Changes

• fix: load esm version of Vite (#​3065)

• fix: stop excluding workspaces under dot-prefixed ancestors (#​3037)

• Updated dependencies [7a3464b, a2561fc]:

  • @​sveltejs/load-config@​0.2.0

v4.6.0

Compare Source

Minor Changes

• feat: support reading Svelte config from vite.config.js/ts (#​3031)

Patch Changes

• Updated dependencies [151cf45]:
  • @​sveltejs/load-config@​0.1.1

v4.5.0

Compare Source

Minor Changes

• feat: support Svelte 5 declaration tags (#​3033)

Patch Changes

• fix: properly handle props with the name slot inside Svelte 5 snippets (#​3030)

• feat: add support for svelte config ts/mts files (#​3009)

v4.4.8

Compare Source

Patch Changes

• feat: typescript 6.0 support (#​2985)

v4.4.7

Compare Source

Patch Changes

• fix: flush stdout/stderr before exit (#​3014)

• fix: report diagnostics in tsconfig.json (#​3005)

v4.4.6

Compare Source

Patch Changes

• fix: prevent config loading message in svelte-check --incremental (#​2974)

• fix: resolve svelte files with NodeNext in --incremental/tsgo (#​2990)

• perf: various optimization with ast walk (#​2969)

• fix: prevent error with escape sequence in attribute (#​2968)

• fix: typescript 6.0 compatibility (#​2988)

heroui-inc/tailwind-variants (tailwind-variants)

v3.3.1

Compare Source

Bug Fixes

• slots shared-state contamination (#​305) ([8b7f0b6](https://redirect.github.com/heroui-inc/tailwind-variants/commit/8b7f0b66

✂ Note

PR body was truncated to here.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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 was generated by Mend Renovate. View the repository job log.

[github-actions]

Test Results

75 tests   75 ✅  5s ⏱️
 2 suites   0 💤
 1 files     0 ❌

Results for commit 7411d85.

♻️ This comment has been updated with latest results.