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

chore(deps): update devdependencies #2641

Merged
merged 2 commits into from
Feb 5, 2024
Merged

chore(deps): update devdependencies #2641

merged 2 commits into from
Feb 5, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 5, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence Type Update
@eslint-types/typescript-eslint (source) ~6.18.1 -> ~6.19.1 age adoption passing confidence devDependencies minor
@types/node (source) ~20.11.6 -> ~20.11.16 age adoption passing confidence devDependencies patch
@types/sanitize-html (source) ~2.9.5 -> ~2.11.0 age adoption passing confidence devDependencies minor
cypress (source) ~13.6.3 -> ~13.6.4 age adoption passing confidence devDependencies patch
esbuild ~0.19.12 -> ~0.20.0 age adoption passing confidence devDependencies minor
eslint-plugin-vitest ~0.3.20 -> ~0.3.21 age adoption passing confidence devDependencies patch
npm-run-all ~4.1.5 -> ~5.0.0 age adoption passing confidence devDependencies replacement
semver ~7.5.4 -> ~7.6.0 age adoption passing confidence devDependencies minor
tsx ~3.13.0 -> ~3.14.0 age adoption passing confidence devDependencies minor

This is a special PR that replaces npm-run-all with the community suggested minimal stable replacement version.


Release Notes

cypress-io/cypress (cypress)

v13.6.4

Compare Source

Changelog: https://docs.cypress.io/guides/references/changelog#13-6-4

evanw/esbuild (esbuild)

v0.20.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.19.0 or ~0.19.0. See npm's documentation about semver for more information.

This time there is only one breaking change, and it only matters for people using Deno. Deno tests that use esbuild will now fail unless you make the change described below.

  • Work around API deprecations in Deno 1.40.x (#​3609, #​3611)

    Deno 1.40.0 was just released and introduced run-time warnings about certain APIs that esbuild uses. With this release, esbuild will work around these run-time warnings by using newer APIs if they are present and falling back to the original APIs otherwise. This should avoid the warnings without breaking compatibility with older versions of Deno.

    Unfortunately, doing this introduces a breaking change. The newer child process APIs lack a way to synchronously terminate esbuild's child process, so calling esbuild.stop() from within a Deno test is no longer sufficient to prevent Deno from failing a test that uses esbuild's API (Deno fails tests that create a child process without killing it before the test ends). To work around this, esbuild's stop() function has been changed to return a promise, and you now have to change esbuild.stop() to await esbuild.stop() in all of your Deno tests.

  • Reorder implicit file extensions within node_modules (#​3341, #​3608)

    In version 0.18.0, esbuild changed the behavior of implicit file extensions within node_modules directories (i.e. in published packages) to prefer .js over .ts even when the --resolve-extensions= order prefers .ts over .js (which it does by default). However, doing that also accidentally made esbuild prefer .css over .ts, which caused problems for people that published packages containing both TypeScript and CSS in files with the same name.

    With this release, esbuild will reorder TypeScript file extensions immediately after the last JavaScript file extensions in the implicit file extension order instead of putting them at the end of the order. Specifically the default implicit file extension order is .tsx,.ts,.jsx,.js,.css,.json which used to become .jsx,.js,.css,.json,.tsx,.ts in node_modules directories. With this release it will now become .jsx,.js,.tsx,.ts,.css,.json instead.

    Why even rewrite the implicit file extension order at all? One reason is because the .js file is more likely to behave correctly than the .ts file. The behavior of the .ts file may depend on tsconfig.json and the tsconfig.json file may not even be published, or may use extends to refer to a base tsconfig.json file that wasn't published. People can get into this situation when they forget to add all .ts files to their .npmignore file before publishing to npm. Picking .js over .ts helps make it more likely that resulting bundle will behave correctly.

veritem/eslint-plugin-vitest (eslint-plugin-vitest)

v0.3.21

Compare Source

What's Changed

New Contributors

Full Changelog: vitest-dev/eslint-plugin-vitest@v0.3.20...v0.3.21

npm/node-semver (semver)

v7.6.0

Compare Source

Features
Chores
privatenumber/tsx (tsx)

v3.14.0

Compare Source

Bug Fixes
Features
  • support Node v20.6.0 module.register() & --import flag (#​337) (23e4694)

This release is also available on:


Configuration

📅 Schedule: Branch creation - "before 4am 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.

@renovate renovate bot requested a review from a team as a code owner February 5, 2024 01:34
@renovate renovate bot added the c: dependencies Pull requests that adds/updates a dependency label Feb 5, 2024
Copy link

codecov bot commented Feb 5, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (c6b8383) 99.57% compared to head (07a9865) 99.57%.

❗ Current head 07a9865 differs from pull request most recent head 8211d70. Consider uploading reports for the commit 8211d70 to get more accurate results

Additional details and impacted files
@@           Coverage Diff           @@
##             next    #2641   +/-   ##
=======================================
  Coverage   99.57%   99.57%           
=======================================
  Files        2807     2807           
  Lines      250525   250525           
  Branches     1150     1155    +5     
=======================================
+ Hits       249453   249472   +19     
+ Misses       1072     1053   -19     

see 1 file with indirect coverage changes

@renovate renovate bot force-pushed the renovate/devdependencies branch 5 times, most recently from 9c1be48 to d9b3e23 Compare February 5, 2024 21:15
@renovate renovate bot force-pushed the renovate/devdependencies branch from d9b3e23 to 07a9865 Compare February 5, 2024 21:35
@ST-DDT ST-DDT self-assigned this Feb 5, 2024
Copy link
Contributor Author

renovate bot commented Feb 5, 2024

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

Warning: custom changes will be lost.

@ST-DDT ST-DDT requested review from a team February 5, 2024 22:06
@ST-DDT ST-DDT added this to the vAnytime milestone Feb 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c: dependencies Pull requests that adds/updates a dependency
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants