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.

Sign up for GitHub

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

Jump to bottom

chore(deps): update all non-major dependencies #46

Merged
merged 1 commit into from
Apr 24, 2023
Merged

chore(deps): update all non-major dependencies #46

merged 1 commit into from
Apr 24, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 24, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@types/node (source) ^18.15.11 -> ^18.16.0 age adoption passing confidence
@typescript-eslint/eslint-plugin ^5.58.0 -> ^5.59.0 age adoption passing confidence
@typescript-eslint/parser ^5.58.0 -> ^5.59.0 age adoption passing confidence
esbuild ^0.17.16 -> ^0.17.18 age adoption passing confidence
eslint (source) ^8.38.0 -> ^8.39.0 age adoption passing confidence
pnpm (source) 7.32.0 -> 7.32.2 age adoption passing confidence
prettier (source) ^2.8.7 -> ^2.8.8 age adoption passing confidence
rollup (source) ^3.20.2 -> ^3.21.0 age adoption passing confidence
vitest ^0.30.0 -> ^0.30.1 age adoption passing confidence

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

evanw/esbuild

v0.17.18

Compare Source

  • Fix non-default JSON import error with export {} from (#​3070)

    This release fixes a bug where esbuild incorrectly identified statements of the form export { default as x } from "y" assert { type: "json" } as a non-default import. The bug did not affect code of the form import { default as x } from ... (only code that used the export keyword).

  • Fix a crash with an invalid subpath import (#​3067)

    Previously esbuild could crash when attempting to generate a friendly error message for an invalid subpath import (i.e. an import starting with #). This happened because esbuild originally only supported the exports field and the code for that error message was not updated when esbuild later added support for the imports field. This crash has been fixed.

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.

eslint/eslint

v8.39.0

Compare Source

Features

  • 3f7af9f feat: Implement SourceCode#markVariableAsUsed() (#​17086) (Nicholas C. Zakas)

Documentation

  • 6987dc5 docs: Fix formatting in Custom Rules docs (#​17097) (Milos Djermanovic)
  • 4ee92e5 docs: Update README (GitHub Actions Bot)
  • d8e9887 docs: Custom Rules cleanup/expansion (#​16906) (Ben Perlmutter)
  • 1fea279 docs: Clarify how to add to tsc agenda (#​17084) (Nicholas C. Zakas)
  • 970ef1c docs: Update triage board location (Nicholas C. Zakas)
  • 6d8bffd docs: Update README (GitHub Actions Bot)

Chores

pnpm/pnpm

v7.32.2

Compare Source

Patch Changes
  • Patch node-fetch to fix an error that happens on Node.js 20 #​6424.
Our Gold Sponsors
Our Silver Sponsors

v7.32.1

Compare Source

Patch Changes
  • Warn user when publishConfig.directory of an injected workspace dependency does not exist #​6396.
  • Use hard links to link the node executable on Windows machines #​4315.
Our Gold Sponsors
Our Silver Sponsors
prettier/prettier

v2.8.8

Compare Source

This version is a republished version of v2.8.7.
A bad version was accidentally published and it can't be unpublished, apologies for the churn.

rollup/rollup

v3.21.0

Compare Source

2023-04-23

Features
  • Support tree-shaking of named exports in dynamic imports when using destructuring and similar patterns (#​4952)
Pull Requests

v3.20.7

Compare Source

2023-04-21

Bug Fixes
  • Properly track array element mutations when iterating with a for-of loop (#​4949)
  • Handle default exporting an anonymous class that extends another class (#​4950)
Pull Requests

v3.20.6

Compare Source

2023-04-18

Bug Fixes
  • Revert handling of non-JS import and export names due to regressions (#​4914)
Pull Requests

v3.20.5

Compare Source

2023-04-18

Bug Fixes
  • Handle import and export names that are not valid JavaScript identifiers (#​4939)
Pull Requests

v3.20.4

Compare Source

2023-04-17

Bug Fixes
  • Do not remove breaks statements after switch statements with conditional breaks (#​4937)
Pull Requests

v3.20.3

Compare Source

2023-04-16

Bug Fixes
  • Reduce memory consumption for function call parameter analysis (#​4938)
  • Fix types for shouldTransformCachedModule (#​4932)
Pull Requests
vitest-dev/vitest

v0.30.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

Configuration

📅 Schedule: Branch creation - "before 3am on Monday" (UTC), 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 Mend Renovate. View repository job log here.

@AriPerkkio AriPerkkio merged commit eaad676 into master Apr 24, 2023
@AriPerkkio AriPerkkio deleted the renovate/all-minor-patch branch April 24, 2023 05:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
dependencies
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
1 participant
@AriPerkkio