Sourced fromesbuild's releases.

v0.25.4

• Add simple support for CORS to esbuild's development server (#4125)

  Starting with version 0.25.0, esbuild's development server is no longer configured to serve cross-origin requests. This was a deliberate change to prevent any website you visit from accessing your running esbuild development server. However, this change prevented (by design) certain use cases such as "debugging in production" by having your production website load code fromlocalhost where the esbuild development server is running.

  To enable this use case, esbuild is adding a feature to allowCross-Origin Resource Sharing (a.k.a. CORS) forsimple requests. Specifically, passing your origin to the newcors option will now set theAccess-Control-Allow-Origin response header when the request has a matchingOrigin header. Note that this currently only works for requests that don't send a preflightOPTIONS request, as esbuild's development server doesn't currently supportOPTIONS requests.

  Some examples:

  • CLI:

    esbuild --servedir=. --cors-origin=https://example.com

  • JS:

    constctx=awaitesbuild.context({})awaitctx.serve({servedir:'.',cors:{origin:'https://example.com',},})

  • Go:

    ctx,_:=api.Context(api.BuildOptions{})ctx.Serve(api.ServeOptions{Servedir:".",CORS: api.CORSOptions{Origin: []string{"https://example.com"},  },})

  The special origin* can be used to allow any origin to access esbuild's development server. Note that this means any website you visit will be able to read everything served by esbuild.

• Pass through invalid URLs in source maps unmodified (#4169)

  This fixes a regression in version 0.25.0 wheresources in source maps that form invalid URLs were not being passed through to the output. Version 0.25.0 changed the interpretation ofsources from file paths to URLs, which means that URL parsing can now fail. Previously URLs that couldn't be parsed were replaced with the empty string. With this release, invalid URLs insources should now be passed through unmodified.

• Handle exports named__proto__ in ES modules (#4162,#4163)

  In JavaScript, the special property name__proto__ sets the prototype when used inside an object literal. Previously esbuild's ESM-to-CommonJS conversion didn't special-case the property name of exports named__proto__ so the exported getter accidentally became the prototype of the object literal. It's unclear what this affects, if anything, but it's better practice to avoid this by using a computed property name in this case.

  This fix was contributed by@​magic-akari.

Sourced fromesbuild's changelog.

0.25.4

• Add simple support for CORS to esbuild's development server (#4125)

  Starting with version 0.25.0, esbuild's development server is no longer configured to serve cross-origin requests. This was a deliberate change to prevent any website you visit from accessing your running esbuild development server. However, this change prevented (by design) certain use cases such as "debugging in production" by having your production website load code fromlocalhost where the esbuild development server is running.

  To enable this use case, esbuild is adding a feature to allowCross-Origin Resource Sharing (a.k.a. CORS) forsimple requests. Specifically, passing your origin to the newcors option will now set theAccess-Control-Allow-Origin response header when the request has a matchingOrigin header. Note that this currently only works for requests that don't send a preflightOPTIONS request, as esbuild's development server doesn't currently supportOPTIONS requests.

  Some examples:

  • CLI:

    esbuild --servedir=. --cors-origin=https://example.com

  • JS:

    constctx=awaitesbuild.context({})awaitctx.serve({servedir:'.',cors:{origin:'https://example.com',},})

  • Go:

    ctx,_:=api.Context(api.BuildOptions{})ctx.Serve(api.ServeOptions{Servedir:".",CORS: api.CORSOptions{Origin: []string{"https://example.com"},  },})

  The special origin* can be used to allow any origin to access esbuild's development server. Note that this means any website you visit will be able to read everything served by esbuild.

• Pass through invalid URLs in source maps unmodified (#4169)

  This fixes a regression in version 0.25.0 wheresources in source maps that form invalid URLs were not being passed through to the output. Version 0.25.0 changed the interpretation ofsources from file paths to URLs, which means that URL parsing can now fail. Previously URLs that couldn't be parsed were replaced with the empty string. With this release, invalid URLs insources should now be passed through unmodified.

• Handle exports named__proto__ in ES modules (#4162,#4163)

  In JavaScript, the special property name__proto__ sets the prototype when used inside an object literal. Previously esbuild's ESM-to-CommonJS conversion didn't special-case the property name of exports named__proto__ so the exported getter accidentally became the prototype of the object literal. It's unclear what this affects, if anything, but it's better practice to avoid this by using a computed property name in this case.

... (truncated)

• 218d29e publish 0.25.4 to npm
• e66cd0b dev server: simple support for CORS requests (#4171)
• 8bf3368 js api: validate some options as arrays of strings
• 1e7375a js api: simplify comma-separated array validation
• 5f5964d release notes for#4163
• adb5284 fix: handle__proto__ as a computed property in exports and add tests for s...
• 0aa9f7b fix#4169: keep invalid source map URLs unmodified
• 5959289 add additional guards for#4114 when using:is()
• See full diff incompare view

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)