Oryx icon indicating copy to clipboard operation
Oryx copied to clipboard
verified publisher icon microsoft

Bump esbuild and @angular-devkit/build-angular in /tests/SampleApps/nodejs/soundcloud-ng18

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

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

Updates esbuild from 0.23.0 to 0.25.9

Release notes

Sourced from esbuild's releases.

v0.25.9

  • Better support building projects that use Yarn on Windows (#3131, #3663)

    With this release, you can now use esbuild to bundle projects that use Yarn Plug'n'Play on Windows on drives other than the C: drive. The problem was as follows:

    1. Yarn in Plug'n'Play mode on Windows stores its global module cache on the C: drive
    2. Some developers put their projects on the D: drive
    3. Yarn generates relative paths that use ../.. to get from the project directory to the cache directory
    4. Windows-style paths don't support directory traversal between drives via .. (so D:\.. is just D:)
    5. I didn't have access to a Windows machine for testing this edge case

    Yarn works around this edge case by pretending Windows-style paths beginning with C:\ are actually Unix-style paths beginning with /C:/, so the ../.. path segments are able to navigate across drives inside Yarn's implementation. This was broken for a long time in esbuild but I finally got access to a Windows machine and was able to debug and fix this edge case. So you should now be able to bundle these projects with esbuild.

  • Preserve parentheses around function expressions (#4252)

    The V8 JavaScript VM uses parentheses around function expressions as an optimization hint to immediately compile the function. Otherwise the function would be lazily-compiled, which has additional overhead if that function is always called immediately as lazy compilation involves parsing the function twice. You can read V8's blog post about this for more details.

    Previously esbuild did not represent parentheses around functions in the AST so they were lost during compilation. With this change, esbuild will now preserve parentheses around function expressions when they are present in the original source code. This means these optimization hints will not be lost when bundling with esbuild. In addition, esbuild will now automatically add this optimization hint to immediately-invoked function expressions. Here's an example:

    // Original code
const fn0 = () => 0
const fn1 = (() => 1)
console.log(fn0, function() { return fn1() }())

    // Old output
    
const fn0 = () => 0;
    
const fn1 = () => 1;
    
console.log(fn0, function() {
    
return fn1();
    
}());
    

    // New output
    
const fn0 = () => 0;
    
const fn1 = (() => 1);
    
console.log(fn0, (function() {
    
return fn1();
    
})());

    Note that you do not want to wrap all function expressions in parentheses. This optimization hint should only be used for functions that are called on initial load. Using this hint for functions that are not called on initial load will unnecessarily delay the initial load. Again, see V8's blog post linked above for details.

  • Update Go from 1.23.10 to 1.23.12 (#4257, #4258)

    This should have no effect on existing code as this version change does not change Go's operating system support. It may remove certain false positive reports (specifically CVE-2025-4674 and CVE-2025-47907) from vulnerability scanners that only detect which version of the Go compiler esbuild uses.

v0.25.8

  • Fix another TypeScript parsing edge case (#4248)

    This fixes a regression with a change in the previous release that tries to more accurately parse TypeScript arrow functions inside the ?: operator. The regression specifically involves parsing an arrow function containing a #private identifier inside the middle of a ?: ternary operator inside a class body. This was fixed by propagating private identifier state into the parser clone used to speculatively parse the arrow function body. Here is an example of some affected code:

... (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).

0.24.2

  • Fix regression with --define and import.meta (#4010, #4012, #4013)

    The previous change in version 0.24.1 to use a more expression-like parser for define values to allow quoted property names introduced a regression that removed the ability to use --define:import.meta=.... Even though import is normally a keyword that can't be used as an identifier, ES modules special-case the import.meta expression to behave like an identifier anyway. This change fixes the regression.

    This fix was contributed by @​sapphi-red.

0.24.1

  • Allow es2024 as a target in tsconfig.json (#4004)

    TypeScript recently added es2024 as a compilation target, so esbuild now supports this in the target field of tsconfig.json files, such as in the following configuration file:

    {
  "compilerOptions": {
    "target": "ES2024"
  }
}

    As a reminder, the only thing that esbuild uses this field for is determining whether or not to use legacy TypeScript behavior for class fields. You can read more in the documentation.

    This fix was contributed by @​billyjanitsch.

  • Allow automatic semicolon insertion after get/set

    This change fixes a grammar bug in the parser that incorrectly treated the following code as a syntax error:

    class Foo {
  get
  *x() {}
  set
  *y() {}
}

    The above code will be considered valid starting with this release. This change to esbuild follows a similar change to TypeScript which will allow this syntax starting with TypeScript 5.7.

  • Allow quoted property names in --define and --pure (#4008)

    The define and pure API options now accept identifier expressions containing quoted property names. Previously all identifiers in the identifier expression had to be bare identifiers. This change now makes --define and --pure consistent with --global-name, which already supported quoted property names. For example, the following is now possible:

... (truncated)

Commits

Updates @angular-devkit/build-angular from 18.2.20 to 20.2.2

Release notes

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

20.2.2

@​angular/cli

Commit Description
fix - a793bbc47 don't set a default for array options when length is 0
fix - 2736599e2 set process title when running architect commands

@​angular/build

Commit Description
fix - 5c2abffea avoid extra tick in SSR dev-server builds
fix - f3c826853 maintain media output hashing with vitest unit-testing

20.2.1

@​angular-devkit/schematics-cli

Commit Description
fix - e93919dea correctly set default array values

@​schematics/angular

Commit Description
fix - 6937123a3 directly resolve karma config template in migration
fix - 5d6dd4425 prevent AI config schematic from failing when 'none' and other AI tools are selected

@​angular/cli

Commit Description
fix - 3b693e09e correctly set default array values

@​angular/build

Commit Description
fix - 06a6ddc10 correct JS/TS file paths when running under Bazel
fix - b6816b0cb ensure karma polyfills reporter factory returns a value

20.2.0

@​schematics/angular

Commit Description
feat - 2e3cfd598 add migration to remove default Karma configurations
feat - d80dae276 add schematics to generate ai context files.
fix - ffe6fb916 allow AI config prompt to be skipped without selecting a value
fix - ae2802b7d improve AI config prompt wording
fix - b017f84fd improve coverage directory handling for Karma configuration comparisons
fix - 6a79f9a75 zoneless is now stable

@​angular/cli

Commit Description
feat - b4de9a1bf add --experimental-tool option to mcp command
feat - 755ba70fd add --local-only option to mcp command
feat - 59d7ef343 add --read-only option to mcp command
feat - 4e92eb6f1 add modernize tool to the MCP server
fix - a3b25f675 add choices to command line parser when type is array and has an enum

... (truncated)

Changelog

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

20.2.2 (2025-09-03)

@​angular/cli

Commit Type Description
a793bbc47 fix don't set a default for array options when length is 0
2736599e2 fix set process title when running architect commands

@​angular/build

Commit Type Description
5c2abffea fix avoid extra tick in SSR dev-server builds
f3c826853 fix maintain media output hashing with vitest unit-testing

21.0.0-next.1 (2025-08-27)

Breaking Changes

@​angular/cli

  • The ng commands will no longer automatically detect and use cnpm as the package manager. As an alternative use the .npmrc file to ensure npm uses the cnpm registry.

@​angular-devkit/schematics-cli

Commit Type Description
aed26c388 fix correctly set default array values

@​schematics/angular

Commit Type Description
4912f3990 feat add Tailwind CSS option to application schematic and ng new
6c7b79833 fix directly resolve karma config template in migration
0f86cf878 fix prevent AI config schematic from failing when 'none' and other AI tools are selected

@​angular/cli

Commit Type Description
0d53e82d5 feat provide detailed peer dependency conflict errors in ng add
f513089e2 feat remove direct support for cnpm
47d77a3ed fix correctly set default array values
e5aed6d65 fix show planned actions in ng add dry run

... (truncated)

Commits
  • 8ffc449 release: cut the v20.2.2 release
  • 425bfe4 refactor(@​angular/cli): update MCP example tool format for if example
  • 2736599 fix(@​angular/cli): set process title when running architect commands
  • f3c8268 fix(@​angular/build): maintain media output hashing with vitest unit-testing
  • 99526bd refactor(@​angular/cli): Improve zoneless migration prompts based on observed ...
  • b2d5e6e refactor(@​angular/cli): add logging and HTML removal to doc search tool
  • 5c2abff fix(@​angular/build): avoid extra tick in SSR dev-server builds
  • 0eaec23 build: update github/codeql-action action to v3.30.0
  • 269fd99 build: lock file maintenance
  • 2d8b6f6 build: update pnpm to v10.15.1
  • 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 Sep 09 '25 07:09 dependabot[bot]