Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump esbuild and @angular-devkit/build-angular in /scripts/webframeworks-deploy-tests/angular #8321

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Mar 13, 2025

Bumps esbuild to 0.25.1 and updates ancestor dependency @angular-devkit/build-angular. These dependencies need to be updated together.

Updates esbuild from 0.19.5 to 0.25.1

Release notes

Sourced from esbuild's releases.

v0.25.1

  • Fix incorrect paths in inline source maps (#4070, #4075, #4105)

    This fixes a regression from version 0.25.0 where esbuild didn't correctly resolve relative paths contained within source maps in inline sourceMappingURL data URLs. The paths were incorrectly being passed through as-is instead of being resolved relative to the source file containing the sourceMappingURL comment, which was due to the data URL not being a file URL. This regression has been fixed, and this case now has test coverage.

  • Fix invalid generated source maps (#4080, #4082, #4104, #4107)

    This release fixes a regression from version 0.24.1 that could cause esbuild to generate invalid source maps. Specifically under certain conditions, esbuild could generate a mapping with an out-of-bounds source index. It was introduced by code that attempted to improve esbuild's handling of "null" entries in source maps (i.e. mappings with a generated position but no original position). This regression has been fixed.

    This fix was contributed by @​jridgewell.

  • Fix a regression with non-file source map paths (#4078)

    The format of paths in source maps that aren't in the file namespace was unintentionally changed in version 0.25.0. Path namespaces is an esbuild-specific concept that is optionally available for plugins to use to distinguish paths from file paths and from paths meant for other plugins. Previously the namespace was prepended to the path joined with a : character, but version 0.25.0 unintentionally failed to prepend the namespace. The previous behavior has been restored.

  • Fix a crash with switch optimization (#4088)

    The new code in the previous release to optimize dead code in switch statements accidentally introduced a crash in the edge case where one or more switch case values include a function expression. This is because esbuild now visits the case values first to determine whether any cases are dead code, and then visits the case bodies once the dead code status is known. That triggered some internal asserts that guard against traversing the AST in an unexpected order. This crash has been fixed by changing esbuild to expect the new traversal ordering. Here's an example of affected code:

    switch (x) {
      case '':
        return y.map(z => z.value)
      case y.map(z => z.key).join(','):
        return []
    }
  • Update Go from 1.23.5 to 1.23.7 (#4076, #4077)

    This should have no effect on existing code as this version change does not change Go's operating system support. It may remove certain reports from vulnerability scanners that detect which version of the Go compiler esbuild uses.

    This PR was contributed by @​MikeWillCook.

v0.25.0

This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.24.0 or ~0.24.0. See npm's documentation about semver for more information.

  • Restrict access to esbuild's development server (GHSA-67mh-4wv8-2f99)

    This change addresses esbuild's first security vulnerability report. Previously esbuild set the Access-Control-Allow-Origin header to * to allow esbuild's development server to be flexible in how it's used for development. However, this allows the websites you visit to make HTTP requests to esbuild's local development server, which gives read-only access to your source code if the website were to fetch your source code's specific URL. You can read more information in the report.

    Starting with this release, CORS will now be disabled, and requests will now be denied if the host does not match the one provided to --serve=. The default host is 0.0.0.0, which refers to all of the IP addresses that represent the local machine (e.g. both 127.0.0.1 and 192.168.0.1). If you want to customize anything about esbuild's development server, you can put a proxy in front of esbuild and modify the incoming and/or outgoing requests.

    In addition, the serve() API call has been changed to return an array of hosts instead of a single host string. This makes it possible to determine all of the hosts that esbuild's development server will accept.

    Thanks to @​sapphi-red for reporting this issue.

  • Delete output files when a build fails in watch mode (#3643)

    It has been requested for esbuild to delete files when a build fails in watch mode. Previously esbuild left the old files in place, which could cause people to not immediately realize that the most recent build failed. With this release, esbuild will now delete all output files if a rebuild fails. Fixing the build error and triggering another rebuild will restore all output files again.

... (truncated)

Changelog

Sourced from esbuild's changelog.

Changelog: 2023

This changelog documents all esbuild versions published in the year 2023 (versions 0.16.13 through 0.19.11).

0.19.11

  • Fix TypeScript-specific class transform edge case (#3559)

    The previous release introduced an optimization that avoided transforming super() in the class constructor for TypeScript code compiled with useDefineForClassFields set to false if all class instance fields have no initializers. The rationale was that in this case, all class instance fields are omitted in the output so no changes to the constructor are needed. However, if all of this is the case and there are #private instance fields with initializers, those private instance field initializers were still being moved into the constructor. This was problematic because they were being inserted before the call to super() (since super() is now no longer transformed in that case). This release introduces an additional optimization that avoids moving the private instance field initializers into the constructor in this edge case, which generates smaller code, matches the TypeScript compiler's output more closely, and avoids this bug:

    // Original code
    class Foo extends Bar {
      #private = 1;
      public: any;
      constructor() {
        super();
      }
    }
    // Old output (with esbuild v0.19.9)
    class Foo extends Bar {
    constructor() {
    super();
    this.#private = 1;
    }
    #private;
    }
    // Old output (with esbuild v0.19.10)
    class Foo extends Bar {
    constructor() {
    this.#private = 1;
    super();
    }
    #private;
    }
    // New output
    class Foo extends Bar {
    #private = 1;
    constructor() {
    super();
    }
    }

  • Minifier: allow reording a primitive past a side-effect (#3568)

    The minifier previously allowed reordering a side-effect past a primitive, but didn't handle the case of reordering a primitive past a side-effect. This additional case is now handled:

... (truncated)

Commits

Updates @angular-devkit/build-angular from 17.0.5 to 19.2.3

Release notes

Sourced from @​angular-devkit/build-angular's releases.

v19.2.3

19.2.3 (2025-03-13)

@​angular/build

Commit Description
fix - 5a739820b update babel packages

v19.2.2

19.2.2 (2025-03-12)

@​angular/cli

Commit Description
fix - 0ee24e29b record analytics for nested schematics

@​angular/build

Commit Description
fix - 4575265f0 exclude all entrypoints of a library from prebundling
fix - 83fcffbb7 handle postcss compilation errors gracefully
fix - 78297ee47 provide extract-i18n does not respect
fix - b18b9c8f2 remove duplicate prebundling warning

@​angular/ssr

Commit Description
fix - e6e8ce960 prevent stream draining if write does not return a boolean

v19.2.1

19.2.1 (2025-03-05)

@​schematics/angular

Commit Description
fix - 4c35b5721 prevent accidental deletion of main.ts during application builder migration
fix - d7f9cb578 prevent error when tsconfig file is missing in application builder migration

@​angular-devkit/architect

Commit Description
fix - 3ebd7ca7c improve error message when configuration is missing

@​angular/build

Commit Description
fix - c07330967 allow component HMR with a service worker
fix - c989c91c3 exclude component styles from 'any' and 'all' budget calculations
fix - 96e5dcb5f handle undefined less stylesheet sourcemap values

v19.2.0

19.2.0 (2025-02-26)

@​schematics/angular

... (truncated)

Changelog

Sourced from @​angular-devkit/build-angular's changelog.

19.2.3 (2025-03-13)

@​angular/build

Commit Type Description
5a739820b fix update babel packages

18.2.15 (2025-03-13)

@​angular-devkit/build-angular

Commit Type Description
255c8a50d fix update babel packages

20.0.0-next.1 (2025-03-13)

Breaking Changes

@​angular/build

  • TypeScript versions less than 5.8 are no longer supported.

@​schematics/angular

Commit Type Description
03180fe03 feat use TypeScript module preserve option for new projects
dc2f65999 fix generate component templates with a .ng.html file extension

@​angular/cli

Commit Type Description
2d03d8f11 fix record analytics for nested schematics

@​angular/build

Commit Type Description
31c81e9c6 feat drop support for TypeScript older than 5.8

... (truncated)

Commits
  • e4d1c2a release: cut the v19.2.3 release
  • 5a73982 fix(@​angular/build): update babel packages
  • 0ee1fc5 build: avoid WSL interop flake when preparing Windows CI environment
  • 935cc1d release: cut the v19.2.2 release
  • dc24656 docs: improve developer guide for pnpm and windows
  • 177f356 build: ensure that tools/legacy-rnjs/node_modules is ignored
  • 377e0a4 Further clean-up rules_nodejs npm workspace and remove yarn.lock (#29779)
  • e6e8ce9 fix(@​angular/ssr): prevent stream draining if write does not return a boolean
  • 0ee24e2 fix(@​angular/cli): record analytics for nested schematics
  • 83fcffb fix(@​angular/build): handle postcss compilation errors gracefully
  • 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.

Bumps [esbuild](https://github.com/evanw/esbuild) to 0.25.1 and updates ancestor dependency [@angular-devkit/build-angular](https://github.com/angular/angular-cli). These dependencies need to be updated together.


Updates `esbuild` from 0.19.5 to 0.25.1
- [Release notes](https://github.com/evanw/esbuild/releases)
- [Changelog](https://github.com/evanw/esbuild/blob/main/CHANGELOG-2023.md)
- [Commits](evanw/esbuild@v0.19.5...v0.25.1)

Updates `@angular-devkit/build-angular` from 17.0.5 to 19.2.3
- [Release notes](https://github.com/angular/angular-cli/releases)
- [Changelog](https://github.com/angular/angular-cli/blob/main/CHANGELOG.md)
- [Commits](angular/angular-cli@17.0.5...19.2.3)

---
updated-dependencies:
- dependency-name: esbuild
  dependency-type: indirect
- dependency-name: "@angular-devkit/build-angular"
  dependency-type: direct:development
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Mar 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants