Skip to content

Conversation

@angular-robot
Copy link
Contributor

@angular-robot angular-robot commented Apr 14, 2023

This PR contains the following updates:

Package Type Update Change
@typescript-eslint/eslint-plugin devDependencies minor 5.58.0 -> 5.59.0
@typescript-eslint/parser devDependencies minor 5.58.0 -> 5.59.0
actions/checkout action patch v3.5.1 -> v3.5.2
esbuild optionalDependencies patch 0.17.16 -> 0.17.17
esbuild devDependencies patch 0.17.16 -> 0.17.17
esbuild-wasm dependencies patch 0.17.16 -> 0.17.17
esbuild-wasm devDependencies patch 0.17.16 -> 0.17.17
ini dependencies minor 4.0.0 -> 4.1.0
ini devDependencies minor 4.0.0 -> 4.1.0
postcss (source) dependencies patch 8.4.21 -> 8.4.22
postcss (source) devDependencies patch 8.4.21 -> 8.4.22
semver dependencies minor 7.4.0 -> 7.5.0
semver devDependencies minor 7.4.0 -> 7.5.0
webpack-dev-server dependencies patch 4.13.2 -> 4.13.3
webpack-dev-server devDependencies patch 4.13.2 -> 4.13.3

Release Notes

typescript-eslint/typescript-eslint (@​typescript-eslint/eslint-plugin)

v5.59.0

Compare Source

Bug Fixes
  • eslint-plugin: [no-unnecessary-condition] allow nullish coalescing for naked type parameter (#​6910) (3e5f858)
Features
  • eslint-plugin: [ban-types] add NonNullable suggestion and allow custom suggestions (#​6876) (ff65235)
typescript-eslint/typescript-eslint (@​typescript-eslint/parser)

v5.59.0

Compare Source

Note: Version bump only for package @​typescript-eslint/parser

actions/checkout

v3.5.2

Compare Source

evanw/esbuild

v0.17.17

Compare Source

  • Fix CSS nesting transform for top-level & (#​3052)

    Previously esbuild could crash with a stack overflow when lowering CSS nesting rules with a top-level &, such as in the code below. This happened because esbuild's CSS nesting transform didn't handle top-level &, causing esbuild to inline the top-level selector into itself. This release handles top-level & by replacing it with the :scope pseudo-class:

    /* Original code */
    &,
    a {
      .b {
        color: red;
      }
    }
    
    /* New output (with --target=chrome90) */
    :is(:scope, a) .b {
      color: red;
    }
  • Support exports in package.json for extends in tsconfig.json (#​3058)

    TypeScript 5.0 added the ability to use extends in tsconfig.json to reference a path in a package whose package.json file contains an exports map that points to the correct location. This doesn't automatically work in esbuild because tsconfig.json affects esbuild's path resolution, so esbuild's normal path resolution logic doesn't apply.

    This release adds support for doing this by adding some additional code that attempts to resolve the extends path using the exports field. The behavior should be similar enough to esbuild's main path resolution logic to work as expected.

    Note that esbuild always treats this extends import as a require() import since that's what TypeScript appears to do. Specifically the require condition will be active and the import condition will be inactive.

  • Fix watch mode with NODE_PATH (#​3062)

    Node has a rarely-used feature where you can extend the set of directories that node searches for packages using the NODE_PATH environment variable. While esbuild supports this too, previously a bug prevented esbuild's watch mode from picking up changes to imported files that were contained directly in a NODE_PATH directory. You're supposed to use NODE_PATH for packages, but some people abuse this feature by putting files in that directory instead (e.g. node_modules/some-file.js instead of node_modules/some-pkg/some-file.js). The watch mode bug happens when you do this because esbuild first tries to read some-file.js as a directory and then as a file. Watch mode was incorrectly waiting for some-file.js to become a valid directory. This release fixes this edge case bug by changing watch mode to watch some-file.js as a file when this happens.

npm/ini

v4.1.0

Compare Source

Features
Bug Fixes
postcss/postcss

v8.4.22

Compare Source

  • Fixed TypeScript support with node16 (by Remco Haszing).
npm/node-semver

v7.5.0

Compare Source

Features
Bug Fixes
webpack/webpack-dev-server

v4.13.3

Compare Source


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 Apr 14, 2023
@angular-robot angular-robot bot added the area: build & ci Related the build and CI infrastructure of the project label Apr 14, 2023
@alan-agius4 alan-agius4 added target: rc This PR is targeted for the next release-candidate and removed target: minor This PR is targeted for the next minor release labels Apr 14, 2023
@alan-agius4 alan-agius4 added target: minor This PR is targeted for the next minor release and removed target: rc This PR is targeted for the next release-candidate labels Apr 14, 2023
@angular-robot angular-robot force-pushed the ng-renovate/all-minor-patch branch 6 times, most recently from d3a54eb to 2663647 Compare April 17, 2023 16:20
@angular-robot angular-robot force-pushed the ng-renovate/all-minor-patch branch from 2663647 to e92c105 Compare April 17, 2023 18:17
@angular-robot angular-robot bot merged commit 8c4a84d into angular:main Apr 17, 2023
@angular-robot angular-robot deleted the ng-renovate/all-minor-patch branch April 17, 2023 20:17
@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 May 18, 2023
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