d1-northwind icon indicating copy to clipboard operation
d1-northwind copied to clipboard

Published 20 hours ago • verified publisher icon cloudflare

Bump esbuild, @cloudflare/vite-plugin and wrangler

Open dependabot[bot] opened this issue 6 months ago • 0 comments

Bumps esbuild to 0.25.2 and updates ancestor dependencies esbuild, @cloudflare/vite-plugin and wrangler. These dependencies need to be updated together.

Updates esbuild from 0.24.2 to 0.25.2

Release notes

Sourced from esbuild's releases.

v0.25.2

  • Support flags in regular expressions for the API (#4121)

    The JavaScript plugin API for esbuild takes JavaScript regular expression objects for the filter option. Internally these are translated into Go regular expressions. However, this translation previously ignored the flags property of the regular expression. With this release, esbuild will now translate JavaScript regular expression flags into Go regular expression flags. Specifically the JavaScript regular expression /\.[jt]sx?$/i is turned into the Go regular expression `(?i)\.[jt]sx?$` internally inside of esbuild's API. This should make it possible to use JavaScript regular expressions with the i flag. Note that JavaScript and Go don't support all of the same regular expression features, so this mapping is only approximate.

  • Fix node-specific annotations for string literal export names (#4100)

    When node instantiates a CommonJS module, it scans the AST to look for names to expose via ESM named exports. This is a heuristic that looks for certain patterns such as exports.NAME = ... or module.exports = { ... }. This behavior is used by esbuild to "annotate" CommonJS code that was converted from ESM with the original ESM export names. For example, when converting the file export let foo, bar from ESM to CommonJS, esbuild appends this to the end of the file:

    // Annotate the CommonJS export names for ESM import in node:
0 && (module.exports = {
  bar,
  foo
});

    However, this feature previously didn't work correctly for export names that are not valid identifiers, which can be constructed using string literal export names. The generated code contained a syntax error. That problem is fixed in this release:

    // Original code
let foo
export { foo as "foo!" }

    // Old output (with --format=cjs --platform=node)
...
0 && (module.exports = {
"foo!"
});
    

    // New output (with --format=cjs --platform=node)
...
0 && (module.exports = {
"foo!": null
});

  • Basic support for index source maps (#3439, #4109)

    The source map specification has an optional mode called index source maps that makes it easier for tools to create an aggregate JavaScript file by concatenating many smaller JavaScript files with source maps, and then generate an aggregate source map by simply providing the original source maps along with some offset information. My understanding is that this is rarely used in practice. I'm only aware of two uses of it in the wild: ClojureScript and Turbopack.

    This release provides basic support for indexed source maps. However, the implementation has not been tested on a real app (just on very simple test input). If you are using index source maps in a real app, please try this out and report back if anything isn't working for you.

    Note that this is also not a complete implementation. For example, index source maps technically allows nesting source maps to an arbitrary depth, while esbuild's implementation in this release only supports a single level of nesting. It's unclear whether supporting more than one level of nesting is important or not given the lack of available test cases.

    This feature was contributed by @​clyfish.

v0.25.1

... (truncated)

Changelog

Sourced from esbuild's changelog.

Changelog: 2024

This changelog documents all esbuild versions published in the year 2024 (versions 0.19.12 through 0.24.2).

Commits

Updates @cloudflare/vite-plugin from 1.0.3 to 1.0.6

Release notes

Sourced from @​cloudflare/vite-plugin's releases.

@​cloudflare/vite-plugin@​1.0.6

Patch Changes

@​cloudflare/vite-plugin@​1.0.5

Patch Changes

@​cloudflare/vite-plugin@​1.0.4

Patch Changes

  • #8862 f843447 Thanks @​jamesopstad! - Fix a bug where Node.js externals (i.e. Node.js imports that are included in the runtime) were being registered as missing imports with the depsOptimizer. This was previously causing the dev server to crash if these imports were encountered when using React Router.
Changelog

Sourced from @​cloudflare/vite-plugin's changelog.

1.0.6

Patch Changes

1.0.5

Patch Changes

1.0.4

Patch Changes

  • #8862 f843447 Thanks @​jamesopstad! - Fix a bug where Node.js externals (i.e. Node.js imports that are included in the runtime) were being registered as missing imports with the depsOptimizer. This was previously causing the dev server to crash if these imports were encountered when using React Router.
Commits

Updates wrangler from 4.9.1 to 4.11.0

Release notes

Sourced from wrangler's releases.

[email protected]

Minor Changes

Patch Changes

  • #8885 f2802f9 Thanks @​CarmenPopoviciu! - Disambiguate the "No files to upload. Proceeding with deployment..." message

  • #8924 d2b44a2 Thanks @​dario-piotrowicz! - fix redirected config env validation breaking wrangler pages commands

    a validation check has recently been introduced to make wrangler error on deploy commands when an environment is specified and a redirected configuration is in use (the reason being that redirected configurations should not include any environment), this check is problematic with pages commands where the "production" environment is anyways set by default, to address this the validation check is being relaxed here on pages commands

  • Updated dependencies [f5413c5]:

[email protected]

Minor Changes

Patch Changes

Changelog

Sourced from wrangler's changelog.

4.11.0

Minor Changes

Patch Changes

  • #8885 f2802f9 Thanks @​CarmenPopoviciu! - Disambiguate the "No files to upload. Proceeding with deployment..." message

  • #8924 d2b44a2 Thanks @​dario-piotrowicz! - fix redirected config env validation breaking wrangler pages commands

    a validation check has recently been introduced to make wrangler error on deploy commands when an environment is specified and a redirected configuration is in use (the reason being that redirected configurations should not include any environment), this check is problematic with pages commands where the "production" environment is anyways set by default, to address this the validation check is being relaxed here on pages commands

  • Updated dependencies [f5413c5]:

4.10.0

Minor Changes

Patch Changes

Commits
  • 25b1307 Version Packages (#8900)
  • d2b44a2 fix redirected config env validation breaking wrangler pages commands (#8924)
  • 4cc036d feat[wrangler]: Add deployment id to wrangler pages deployment list output ...
  • 84ecfe9 feat(wrangler): Add debug logs to capture assets upload status (#8244)
  • 2048ad5 docs: fix worker compat URL in docstring (#8799)
  • f5413c5 Bump the workerd-and-workers-types group with 2 updates (#8873)
  • c912b99 Update wrangler esbuild version (#8890)
  • f2802f9 fix(wrangler): Disambiguate the "No files to upload. Proceeding with deployme...
  • 421ea99 Version Packages (#8864)
  • 5388447 Fix multiple request logging (#8883)
  • 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 this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the Security Alerts page.

dependabot[bot] avatar Apr 15 '25 09:04 dependabot[bot]