Skip to content

Conversation

angular-robot
Copy link
Collaborator

@angular-robot angular-robot commented Sep 21, 2024

This PR contains the following updates:

Package Type Update Change
chokidar devDependencies patch 4.0.0 -> 4.0.1
esbuild optionalDependencies minor 0.23.1 -> 0.24.0
esbuild dependencies minor 0.23.1 -> 0.24.0
esbuild devDependencies minor 0.23.1 -> 0.24.0
esbuild-wasm dependencies minor 0.23.1 -> 0.24.0
esbuild-wasm devDependencies minor 0.23.1 -> 0.24.0
rollup (source) dependencies patch 4.22.2 -> 4.22.4
rollup (source) devDependencies patch 4.22.2 -> 4.22.4

Release Notes

paulmillr/chokidar (chokidar)

v4.0.1

Compare Source

  • Various fixes and improvements of typescript types
New Contributors

Full Changelog: paulmillr/chokidar@4.0.0...4.0.1

evanw/esbuild (esbuild)

v0.24.0

Compare Source

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.23.0 or ~0.23.0. See npm's documentation about semver for more information.

  • Drop support for older platforms (#​3902)

    This release drops support for the following operating system:

    • macOS 10.15 Catalina

    This is because the Go programming language dropped support for this operating system version in Go 1.23, and this release updates esbuild from Go 1.22 to Go 1.23. Go 1.23 now requires macOS 11 Big Sur or later.

    Note that this only affects the binary esbuild executables that are published to the esbuild npm package. It's still possible to compile esbuild's source code for these older operating systems. If you need to, you can compile esbuild for yourself using an older version of the Go compiler (before Go version 1.23). That might look something like this:

    git clone https://github.com/evanw/esbuild.git
    cd esbuild
    go build ./cmd/esbuild
    ./esbuild --version
    
  • Fix class field decorators in TypeScript if useDefineForClassFields is false (#​3913)

    Setting the useDefineForClassFields flag to false in tsconfig.json means class fields use the legacy TypeScript behavior instead of the standard JavaScript behavior. Specifically they use assign semantics instead of define semantics (e.g. setters are triggered) and fields without an initializer are not initialized at all. However, when this legacy behavior is combined with standard JavaScript decorators, TypeScript switches to always initializing all fields, even those without initializers. Previously esbuild incorrectly continued to omit field initializers for this edge case. These field initializers in this case should now be emitted starting with this release.

  • Avoid incorrect cycle warning with tsconfig.json multiple inheritance (#​3898)

    TypeScript 5.0 introduced multiple inheritance for tsconfig.json files where extends can be an array of file paths. Previously esbuild would incorrectly treat files encountered more than once when processing separate subtrees of the multiple inheritance hierarchy as an inheritance cycle. With this release, tsconfig.json files containing this edge case should work correctly without generating a warning.

  • Handle Yarn Plug'n'Play stack overflow with tsconfig.json (#​3915)

    Previously a tsconfig.json file that extends another file in a package with an exports map could cause a stack overflow when Yarn's Plug'n'Play resolution was active. This edge case should work now starting with this release.

  • Work around more issues with Deno 1.31+ (#​3917)

    This version of Deno broke the stdin and stdout properties on command objects for inherited streams, which matters when you run esbuild's Deno module as the entry point (i.e. when import.meta.main is true). Previously esbuild would crash in Deno 1.31+ if you ran esbuild like that. This should be fixed starting with this release.

    This fix was contributed by @​Joshix-1.

rollup/rollup (rollup)

v4.22.4

Compare Source

2024-09-21

Bug Fixes
  • Fix a vulnerability in generated code that affects IIFE, UMD and CJS bundles when run in a browser context (#​5671)
Pull Requests

v4.22.3

Compare Source

2024-09-21

Bug Fixes
  • Ensure that mutations in modules without side effects are observed while properly handling transitive dependencies (#​5669)
Pull Requests

Configuration

📅 Schedule: Branch creation - "after 10:00pm every weekday,before 4:00am every weekday,every weekend" in timezone America/Tijuana, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@angular-robot angular-robot added action: merge The PR is ready for merge by the caretaker target: minor This PR is targeted for the next minor release labels Sep 21, 2024
@angular-robot angular-robot bot added the area: build & ci Related the build and CI infrastructure of the project label Sep 21, 2024
@angular-robot angular-robot force-pushed the ng-renovate/all-minor-patch branch from 0cfced8 to 5e2ca78 Compare September 21, 2024 07:09
@angular-robot angular-robot changed the title build: update dependency rollup to v4.22.3 build: update dependency rollup to v4.22.4 Sep 21, 2024
@angular-robot angular-robot force-pushed the ng-renovate/all-minor-patch branch from 5e2ca78 to c8fa1c7 Compare September 22, 2024 02:33
@angular-robot angular-robot changed the title build: update dependency rollup to v4.22.4 build: update all non-major dependencies Sep 22, 2024
@angular-robot angular-robot force-pushed the ng-renovate/all-minor-patch branch from c8fa1c7 to 13754c5 Compare September 22, 2024 14:08
@clydin clydin merged commit 1434d62 into angular:main Sep 23, 2024
30 checks passed
@angular-robot angular-robot deleted the ng-renovate/all-minor-patch branch September 23, 2024 13:16
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Oct 24, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

action: merge The PR is ready for merge by the caretaker area: build & ci Related the build and CI infrastructure of the project target: minor This PR is targeted for the next minor release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants