build(deps-dev): bump the npm-development group across 1 directory with 6 updates

[dependabot]

Bumps the npm-development group with 6 updates in the / directory:

Package	From	To
@types/node	20.11.30	20.14.8
editorconfig-checker	5.1.5	5.1.8
esbuild	0.20.2	0.21.5
lint-staged	15.2.2	15.2.7
prettier	3.2.5	3.3.2
vitest	1.4.0	1.6.0

Updates @types/node from 20.11.30 to 20.14.8

Commits

• See full diff in compare view

Updates editorconfig-checker from 5.1.5 to 5.1.8

Release notes

Sourced from editorconfig-checker's releases.

v5.1.8

5.1.8 (2024-06-06)

Reverts

• Revert "chore(deps-dev): bump undici from 6.6.2 to 6.11.1 (#411)" (51a754a), closes #411

v5.1.6 release didn't work because of an issue with the @vercel/ncc compiler: vercel/ncc#1193, for now we revert the changes, so basically v5.1.8 is the same as v5.1.5. Sorry for the troubles, we also improved our CI, so we should be able to detect this kind of issues in the future.

v5.1.7

5.1.7 (2024-06-06)

Reverts

• Revert "fix: update dependencies to latest (#412)" (f04e860), closes #412 #413
• Revert "fix: semantic-release v23" (d1b7b93)

v5.1.6

5.1.6 (2024-06-06)

Bug Fixes

• semantic-release v23 (52f4b29)
• update dependencies to latest (#412) (5b68e04)

Commits

• 09e6530 chore: improve ci so it verify if the built program with @​vercel/ncc executes...
• 51a754a Revert "chore(deps-dev): bump undici from 6.6.2 to 6.11.1 (#411)"
• f04e860 Revert "fix: update dependencies to latest (#412)"
• d1b7b93 Revert "fix: semantic-release v23"
• 52f4b29 fix: semantic-release v23
• 5b68e04 fix: update dependencies to latest (#412)
• d1f6ab1 chore(deps-dev): bump undici from 6.6.2 to 6.11.1 (#411)
• See full diff in compare view

Updates esbuild from 0.20.2 to 0.21.5

Release notes

Sourced from esbuild's releases.

v0.21.5

• Fix Symbol.metadata on classes without a class decorator (#3781)

  This release fixes a bug with esbuild's support for the decorator metadata proposal. Previously esbuild only added the Symbol.metadata property to decorated classes if there was a decorator on the class element itself. However, the proposal says that the Symbol.metadata property should be present on all classes that have any decorators at all, not just those with a decorator on the class element itself.

• Allow unknown import attributes to be used with the copy loader (#3792)

  Import attributes (the with keyword on import statements) are allowed to alter how that path is loaded. For example, esbuild cannot assume that it knows how to load ./bagel.js as type bagel:

  // This is an error with "--bundle" without also using "--external:./bagel.js"
  import tasty from "./bagel.js" with { type: "bagel" }

  Because of that, bundling this code with esbuild is an error unless the file ./bagel.js is external to the bundle (such as with --bundle --external:./bagel.js).

  However, there is an additional case where it's ok for esbuild to allow this: if the file is loaded using the copy loader. That's because the copy loader behaves similarly to --external in that the file is left external to the bundle. The difference is that the copy loader copies the file into the output folder and rewrites the import path while --external doesn't. That means the following will now work with the copy loader (such as with --bundle --loader:.bagel=copy):

  // This is no longer an error with "--bundle" and "--loader:.bagel=copy"
  import tasty from "./tasty.bagel" with { type: "bagel" }

• Support import attributes with glob-style imports (#3797)

  This release adds support for import attributes (the with option) to glob-style imports (dynamic imports with certain string literal patterns as paths). These imports previously didn't support import attributes due to an oversight. So code like this will now work correctly:

  async function loadLocale(locale: string): Locale {
    const data = await import(`./locales/${locale}.data`, { with: { type: 'json' } })
    return unpackLocale(locale, data)
  }

  Previously this didn't work even though esbuild normally supports forcing the JSON loader using an import attribute. Attempting to do this used to result in the following error:

  ✘ [ERROR] No loader is configured for ".data" files: locales/en-US.data
  example.ts:2:28:
    2 │   const data = await import(`./locales/${locale}.data`, { with: { type: 'json' } })
      ╵                             ~~~~~~~~~~~~~~~~~~~~~~~~~~
  
  

  In addition, this change means plugins can now access the contents of with for glob-style imports.

• Support ${configDir} in tsconfig.json files (#3782)

  This adds support for a new feature from the upcoming TypeScript 5.5 release. The character sequence ${configDir} is now respected at the start of baseUrl and paths values, which are used by esbuild during bundling to correctly map import paths to file system paths. This feature lets base tsconfig.json files specified via extends refer to the directory of the top-level tsconfig.json file. Here is an example:

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.21.5

• Fix Symbol.metadata on classes without a class decorator (#3781)

  This release fixes a bug with esbuild's support for the decorator metadata proposal. Previously esbuild only added the Symbol.metadata property to decorated classes if there was a decorator on the class element itself. However, the proposal says that the Symbol.metadata property should be present on all classes that have any decorators at all, not just those with a decorator on the class element itself.

• Allow unknown import attributes to be used with the copy loader (#3792)

  Import attributes (the with keyword on import statements) are allowed to alter how that path is loaded. For example, esbuild cannot assume that it knows how to load ./bagel.js as type bagel:

  // This is an error with "--bundle" without also using "--external:./bagel.js"
  import tasty from "./bagel.js" with { type: "bagel" }

  Because of that, bundling this code with esbuild is an error unless the file ./bagel.js is external to the bundle (such as with --bundle --external:./bagel.js).

  However, there is an additional case where it's ok for esbuild to allow this: if the file is loaded using the copy loader. That's because the copy loader behaves similarly to --external in that the file is left external to the bundle. The difference is that the copy loader copies the file into the output folder and rewrites the import path while --external doesn't. That means the following will now work with the copy loader (such as with --bundle --loader:.bagel=copy):

  // This is no longer an error with "--bundle" and "--loader:.bagel=copy"
  import tasty from "./tasty.bagel" with { type: "bagel" }

• Support import attributes with glob-style imports (#3797)

  This release adds support for import attributes (the with option) to glob-style imports (dynamic imports with certain string literal patterns as paths). These imports previously didn't support import attributes due to an oversight. So code like this will now work correctly:

  async function loadLocale(locale: string): Locale {
    const data = await import(`./locales/${locale}.data`, { with: { type: 'json' } })
    return unpackLocale(locale, data)
  }

  Previously this didn't work even though esbuild normally supports forcing the JSON loader using an import attribute. Attempting to do this used to result in the following error:

  ✘ [ERROR] No loader is configured for ".data" files: locales/en-US.data
  example.ts:2:28:
    2 │   const data = await import(`./locales/${locale}.data`, { with: { type: 'json' } })
      ╵                             ~~~~~~~~~~~~~~~~~~~~~~~~~~
  
  

  In addition, this change means plugins can now access the contents of with for glob-style imports.

• Support ${configDir} in tsconfig.json files (#3782)

  This adds support for a new feature from the upcoming TypeScript 5.5 release. The character sequence ${configDir} is now respected at the start of baseUrl and paths values, which are used by esbuild during bundling to correctly map import paths to file system paths. This feature lets base tsconfig.json files specified via extends refer to the directory of the top-level tsconfig.json file. Here is an example:

... (truncated)

Commits

• fc37c2f publish 0.21.5 to npm
• cb11924 fix Symbol.metadata errors in decorator tests
• b93a2a9 fix #3781: add metadata to all decorated classes
• 953dae9 fix #3797: import attributes and glob-style import
• 98cb2ed fix #3782: support ${configDir} in tsconfig.json
• 8e6603b run make update-compat-table
• db1b8ca fix #3792: import attributes and the copy loader
• de572d0 fix non-deterministic import attribute plugin test
• ae8d1b4 fix #3794: --supported:object-accessors=false
• 67cbf87 publish 0.21.4 to npm
• Additional commits viewable in compare view

Updates lint-staged from 15.2.2 to 15.2.7

Release notes

Sourced from lint-staged's releases.

v15.2.7

Patch Changes

• #1440 a51be80 Thanks @​iiroj! - In the previous version the native git rev-parse --show-toplevel command was taken into use for resolving the current git repo root. This version drops the --path-format=absolute option to support earlier git versions since it's also the default behavior. If you are still having trouble, please try upgrading git to the latest version.

v15.2.6

Patch Changes

• #1433 119adb2 Thanks @​iiroj! - Use native "git rev-parse" commands to determine git repo root directory and the .git config directory, instead of using custom logic. This hopefully makes path resolution more robust on non-POSIX systems.

v15.2.5

Patch Changes

• #1424 31a1f95 Thanks @​iiroj! - Allow approximately equivalent versions of direct dependencies by using the "~" character in the version ranges. This means a more recent patch version of a dependency is allowed if available.

• #1423 91abea0 Thanks @​iiroj! - Improve error logging when failing to read or parse a configuration file

• #1424 ee43f15 Thanks @​iiroj! - Upgrade micromatch@4.0.7

v15.2.4

Patch Changes

• 4f4537a Thanks @​iiroj! - Fix release issue with previous version; update dependencies

v15.2.3

Patch Changes

• #1407 d698162 Thanks @​iiroj! - Update dependencies

Changelog

Sourced from lint-staged's changelog.

15.2.7

Patch Changes

• #1440 a51be80 Thanks @​iiroj! - In the previous version the native git rev-parse --show-toplevel command was taken into use for resolving the current git repo root. This version drops the --path-format=absolute option to support earlier git versions since it's also the default behavior. If you are still having trouble, please try upgrading git to the latest version.

15.2.6

Patch Changes

• #1433 119adb2 Thanks @​iiroj! - Use native "git rev-parse" commands to determine git repo root directory and the .git config directory, instead of using custom logic. This hopefully makes path resolution more robust on non-POSIX systems.

15.2.5

Patch Changes

• #1424 31a1f95 Thanks @​iiroj! - Allow approximately equivalent versions of direct dependencies by using the "~" character in the version ranges. This means a more recent patch version of a dependency is allowed if available.

• #1423 91abea0 Thanks @​iiroj! - Improve error logging when failing to read or parse a configuration file

• #1424 ee43f15 Thanks @​iiroj! - Upgrade micromatch@4.0.7

15.2.4

Patch Changes

• 4f4537a Thanks @​iiroj! - Fix release issue with previous version; update dependencies

15.2.3

Patch Changes

• #1407 d698162 Thanks @​iiroj! - Update dependencies

Commits

• 87e4b30 chore(changeset): release (#1441)
• a39e829 docs: adjust changeset
• a51be80 fix: drop option to support earlier Git versions
• a91d942 chore(changeset): release
• 119adb2 fix: use native git command to get .git directory
• e0386dc fix: use native git command to get top-level directory for repo
• 6593870 ci: test Node.js versions against current instead of latest dependency
• 6c226c5 ci: add workflow for testing required Node.js semver range
• f7e4106 chore(changeset): release
• fc75303 build(release): lower next version bump from minor to patch
• Additional commits viewable in compare view

Updates prettier from 3.2.5 to 3.3.2

Release notes

Sourced from prettier's releases.

3.3.2

🔗 Changelog

3.3.1

🔗 Changelog

3.3.0

diff

🔗 Release note

Changelog

Sourced from prettier's changelog.

3.3.2

diff

Fix handlebars path expressions starts with @ (#16358 by @​Princeyadav05)

{{! Input }}
<div>{{@x.y.z}}</div>
{{! Prettier 3.3.1 }}
<div>{{@​x}}</div>
{{! Prettier 3.3.2 }}
<div>{{@​x.y.z}}</div>

3.3.1

diff

Preserve empty lines in front matter (#16347 by @​fisker)

<!-- Input -->
---
foo:
  - bar1


bar2


bar3



Markdown
<!-- Prettier 3.3.0 -->

foo:

bar1
bar2
bar3


Markdown
<!-- Prettier 3.3.1 -->
</tr></table>

... (truncated)

Commits

• 1596a60 Release 3.3.2
• aebcee5 chore(deps): update dependency esbuild to v0.21.5 (#16379)
• 57aa928 chore(deps): update dependency c8 to v10 (#16380)
• c3d0b7f chore(deps): update typescript-eslint to v7.13.0 (#16376)
• 27c35db chore(deps): update dependency codemirror-graphql to v2.0.12 (#16369)
• 6de3258 chore(deps): update dependency jest to v30.0.0-alpha.5 (#16371)
• b5f983d Upgrade yarn to v4.3.0 (#16377)
• d6f37c4 chore(deps): update dependency browserslist to v4.23.1 (#16368)
• 5055b7d chore(deps): update dependency execa to v9.2.0 (#16372)
• f4608cc chore(deps): update dependency cspell to v8.8.4 (#16370)
• Additional commits viewable in compare view

Updates vitest from 1.4.0 to 1.6.0

Release notes

Sourced from vitest's releases.

v1.6.0

   🚀 Features

• Support standalone mode  -  by @​sheremet-va in vitest-dev/vitest#5565 (bdce0)
• Custom "snapshotEnvironment" option  -  by @​sheremet-va in vitest-dev/vitest#5449 (30f72)
• benchmark: Support comparing benchmark result  -  by @​hi-ogawa and @​sheremet-va in vitest-dev/vitest#5398 (f8d3d)
• browser: Allow injecting scripts  -  by @​sheremet-va in vitest-dev/vitest#5656 (21e58)
• reporter: Support includeConsoleOutput and addFileAttribute in junit  -  by @​hi-ogawa in vitest-dev/vitest#5659 (2f913)
• ui: Sort items by file name  -  by @​btea in vitest-dev/vitest#5652 (1f726)

   🐞 Bug Fixes

• Keep order of arguments for .each in custom task collectors  -  by @​sheremet-va in vitest-dev/vitest#5640 (7d57c)
• Call resolveId('vitest') after buildStart  -  by @​hi-ogawa in vitest-dev/vitest#5646 (f5faf)
• Hash the name of the file when caching  -  by @​sheremet-va in vitest-dev/vitest#5654 (c9e68)
• Don't panic on empty files in node_modules  -  by @​sheremet-va (40c29)
• Use toJSON for error serialization  -  by @​hi-ogawa in vitest-dev/vitest#5526 (19a21)
• coverage:
  • Exclude *.test-d.* by default  -  by @​MindfulPol in vitest-dev/vitest#5634 (bfe8a)
  • Apply vite-node's wrapper only to executed files  -  by @​AriPerkkio in vitest-dev/vitest#5642 (c9883)
• vm:
  • Support network imports  -  by @​sheremet-va in vitest-dev/vitest#5610 (103a6)

   🏎 Performance

• Improve performance of forks pool  -  by @​sheremet-va in vitest-dev/vitest#5592 (d8304)
• Unnecessary rpc call when coverage is disabled  -  by @​AriPerkkio in vitest-dev/vitest#5658 (c5712)

    View changes on GitHub

v1.5.3

   🐞 Bug Fixes

• Use package.json name for a workspace project if not provided  -  by @​sheremet-va in vitest-dev/vitest#5608 (48fba)
• Backport jest iterable equality within object  -  by @​sukovanej in vitest-dev/vitest#5621 (30e5d)
• browser: Support benchmark  -  by @​hi-ogawa in vitest-dev/vitest#5622 (becab)
• reporter: Use default error formatter for JUnit  -  by @​hi-ogawa in vitest-dev/vitest#5629 (20060)

    View changes on GitHub

v1.5.2

   🐞 Bug Fixes

• Check for null before storing in weakmap  -  by @​sheremet-va (ce368)

    View changes on GitHub

v1.5.1

   🚀 Features

... (truncated)

Commits

• 6b29f3d chore: release v1.6.0
• f8d3d22 feat(benchmark): support comparing benchmark result (#5398)
• 21e58bd feat(browser): allow injecting scripts (#5656)
• 30f728b feat: custom "snapshotEnvironment" option (#5449)
• 2f91322 feat(reporter): support includeConsoleOutput and addFileAttribute in juni...
• c571276 perf: unnecessary rpc call when coverage is disabled (#5658)
• bdce0a2 feat: support standalone mode (#5565)
• 40c299f fix: don't panic on empty files in node_modules
• c9e68ce fix: hash the name of the file when caching (#5654)
• f5faf42 fix: call resolveId('vitest') after buildStart (#5646)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

• main
  • build(deps-dev): bump the npm-development group across 1 directory with 6 updates #30 👈