chore(deps-dev): bump the dev-dependencies group across 1 directory with 6 updates

[dependabot]

Bumps the dev-dependencies group with 6 updates in the / directory:

Package	From	To
esbuild	0.23.0	0.23.1
publint	0.2.9	0.2.10
@jupyter-widgets/base-manager	1.0.9	1.0.11
@types/node	22.2.0	22.5.0
@types/react	18.3.3	18.3.4
vite	5.4.0	5.4.2

Updates esbuild from 0.23.0 to 0.23.1

Release notes

Sourced from esbuild's releases.

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";
  fs.open;
  // New output (with --bundle --format=esm --platform=node --target=node18,es2022)
  import fs from "node:fs";
  fs.open;

• Fix a panic when using the CLI with invalid build flags if --analyze is present (#3834)

  Previously esbuild's CLI could crash if it was invoked with flags that aren't valid for a "build" API call and the --analyze flag is present. This was caused by esbuild's internals attempting to add a Go plugin (which is how --analyze is implemented) to a null build object. The panic has been fixed in this release.

• Fix incorrect location of certain error messages (#3845)

  This release fixes a regression that caused certain errors relating to variable declarations to be reported at an incorrect location. The regression was introduced in version 0.18.7 of esbuild.

• Print comments before case clauses in switch statements (#3838)

  With this release, esbuild will attempt to print comments that come before case clauses in switch statements. This is similar to what esbuild already does for comments inside of certain types of expressions. Note that these types of comments are not printed if minification is enabled (specifically whitespace minification).

• Fix a memory leak with pluginData (#3825)

  With this release, the build context's internal pluginData cache will now be cleared when starting a new build. This should fix a leak of memory from plugins that return pluginData objects from onResolve and/or onLoad callbacks.

Changelog

Sourced from esbuild's changelog.

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
  // Old output (with --bundle --format=esm --platform=node --target=node18,es2022)
  import fs from "fs";
  fs.open;
  // New output (with --bundle --format=esm --platform=node --target=node18,es2022)
  import fs from "node:fs";
  fs.open;

• Fix a panic when using the CLI with invalid build flags if --analyze is present (#3834)

  Previously esbuild's CLI could crash if it was invoked with flags that aren't valid for a "build" API call and the --analyze flag is present. This was caused by esbuild's internals attempting to add a Go plugin (which is how --analyze is implemented) to a null build object. The panic has been fixed in this release.

• Fix incorrect location of certain error messages (#3845)

  This release fixes a regression that caused certain errors relating to variable declarations to be reported at an incorrect location. The regression was introduced in version 0.18.7 of esbuild.

• Print comments before case clauses in switch statements (#3838)

  With this release, esbuild will attempt to print comments that come before case clauses in switch statements. This is similar to what esbuild already does for comments inside of certain types of expressions. Note that these types of comments are not printed if minification is enabled (specifically whitespace minification).

• Fix a memory leak with pluginData (#3825)

  With this release, the build context's internal pluginData cache will now be cleared when starting a new build. This should fix a leak of memory from plugins that return pluginData objects from onResolve and/or onLoad callbacks.

Commits

• 3327274 publish 0.23.1 to npm
• 38e22ed add a warning/debug log message for #3867
• a15bb51 fix #3825: memory leak of pluginData values
• f6e6481 fix #3838: print comments before case clauses
• 9c13ae1 fix #3853: update go 1.22.4 => 1.22.5
• 78f89e4 fix #3845: some incorrect error message locations
• 892d2a7 fix #3834: cli sometimes panics with --analyze
• 360d472 fix a typo in the release notes
• e3f4e2d fix #3821: allow node: prefix with es* targets
• See full diff in compare view

Updates publint from 0.2.9 to 0.2.10

Release notes

Sourced from publint's releases.

v0.2.10

Features

• Adds a new rule that validates the "repository" field (bluwy/publint#106)
  • If "repository" is a string, it must be one of the supported shorthand strings from the docs.
  • If "repository" is an object with "type": "git", the "url" must be a valid git URL and can be parsed by npm.
  • The git:// protocol for GitHub repos should not be used due security concerns.
  • GitHub or GitLab links should be prefixed with git+ and postfixed with .git. (This is also warned by npm when publishing a package).

New Contributors

• @​Namchee made their first contribution in bluwy/publint#106

Full Changelog: publint/publint@v0.2.9...v0.2.10

Commits

• 6d00f6b Release v0.2.10
• a94f663 feat: add INVALID_REPOSITORY_VALUE rule (#106)
• See full diff in compare view

Updates @jupyter-widgets/base-manager from 1.0.9 to 1.0.11

Commits

• d386553 Publish npm packages
• 28bc0cf Merge pull request #1887 from jasongrout/docsupdate10
• bb8b308 Move ipywidgets to the conda-forge version and recommonmark back to pip.
• af44626 Merge pull request #1886 from jasongrout/docsupdate8
• b395272 More updates to docs build environment.
• ef5e1b2 Merge pull request #1885 from jasongrout/docsupdate7
• 7531ead Remove docs environment pin of sphinx to 1.4.8
• 4461f24 Merge pull request #1884 from jasongrout/docsupdate3
• 9ec4569 Update some doc environment requirements.
• a296e1c Merge pull request #1883 from jasongrout/rangeupdate
• Additional commits viewable in compare view

Updates @types/node from 22.2.0 to 22.5.0

Commits

• See full diff in compare view

Updates @types/react from 18.3.3 to 18.3.4

Commits

• See full diff in compare view

Updates vite from 5.4.0 to 5.4.2

Changelog

Sourced from vite's changelog.

5.4.2 (2024-08-20)

• chore: remove stale TODOs (#17866) (e012f29), closes #17866
• refactor: remove redundant prepend/strip base (#17887) (3b8f03d), closes #17887
• fix: resolve relative URL generated by renderBuiltUrl passed to module preload (#16084) (fac3a8e), closes #16084
• feat: support originalFilename (#17867) (7d8c0e2), closes #17867

5.4.1 (2024-08-15)

• fix: build.modulePreload.resolveDependencies is optimizable (#16083) (e961b31), closes #16083
• fix: align CorsOptions.origin type with @​types/cors (#17836) (1bda847), closes #17836
• fix: typings for vite:preloadError (#17868) (6700594), closes #17868
• fix(build): avoid re-define __vite_import_meta_env__ (#17876) (e686d74), closes #17876
• fix(deps): update all non-major dependencies (#17869) (d11711c), closes #17869
• fix(lightningcss): search for assets with correct base path (#17856) (4e5ce3c), closes #17856
• fix(worker): handle self reference url worker in dependency for build (#17846) (391bb49), closes #17846
• chore: fix picocolors import for local dev (#17884) (9018255), closes #17884
• refactor: remove handleHotUpdate from watch-package-data plugin (#17865) (e16bf1f), closes #17865

Commits

• b1ecdaf release: v5.4.2
• e012f29 chore: remove stale TODOs (#17866)
• 3b8f03d refactor: remove redundant prepend/strip base (#17887)
• fac3a8e fix: resolve relative URL generated by renderBuiltUrl passed to module prel...
• 7d8c0e2 feat: support originalFilename (#17867)
• b44c20c release: v5.4.1
• 391bb49 fix(worker): handle self reference url worker in dependency for build (#17846)
• e686d74 fix(build): avoid re-define __vite_import_meta_env__ (#17876)
• 9018255 chore: fix picocolors import for local dev (#17884)
• 1bda847 fix: align CorsOptions.origin type with @​types/cors (#17836)
• 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

[changeset-bot]

⚠️ No Changeset found

Latest commit: 6b3c4a8

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR