remoll/eth-physics
1
0
Fork 0
Code Issues 1 Pull Requests 2 Packages Projects Releases Wiki Activity

chore(deps): update dependency esbuild to ^0.20.0 - autoclosed #5

Closed
renovate wants to merge 1 commits from renovate/esbuild-0.x into v4
pull from: renovate/esbuild-0.x
merge into: remoll:v4
Conversation 1 Commits 1 Files Changed 1 +1 -1
renovate commented 2024-02-03 22:01:24 +00:00
Collaborator
Copy Link

This PR contains the following updates:

Package Type Update Change
esbuild devDependencies minor ^0.19.9 -> ^0.20.0

Release Notes

evanw/esbuild (esbuild)

v0.20.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.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.

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

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

This PR has been generated by Renovate Bot.

This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [esbuild](https://github.com/evanw/esbuild) | devDependencies | minor | [`^0.19.9` -> `^0.20.0`](https://renovatebot.com/diffs/npm/esbuild/0.19.12/0.20.0) | --- ### Release Notes <details> <summary>evanw/esbuild (esbuild)</summary> ### [`v0.20.0`](https://github.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0200) [Compare Source](https://github.com/evanw/esbuild/compare/v0.19.12...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](https://docs.npmjs.com/cli/v6/using-npm/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 ([#&#8203;3609](https://github.com/evanw/esbuild/issues/3609), [#&#8203;3611](https://github.com/evanw/esbuild/pull/3611)) [Deno 1.40.0](https://deno.com/blog/v1.40) 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` ([#&#8203;3341](https://github.com/evanw/esbuild/issues/3341), [#&#8203;3608](https://github.com/evanw/esbuild/issues/3608)) In [version 0.18.0](https://github.com/evanw/esbuild/releases/v0.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. </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), 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. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy4xMDcuMCIsInVwZGF0ZWRJblZlciI6IjM3LjEwNy4wIiwidGFyZ2V0QnJhbmNoIjoidjQifQ==-->
renovate added 1 commit 2024-02-03 22:01:24 +00:00
chore(deps): update dependency esbuild to ^0.20.0
Some checks failed
renovate/artifacts Artifact file update failure
28cf7d96d8
renovate commented 2024-02-03 22:01:24 +00:00
Author
Collaborator
Copy Link

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: esbuild-sass-plugin@2.16.0
npm ERR! Found: esbuild@0.20.0
npm ERR! node_modules/esbuild
npm ERR!   dev esbuild@"^0.20.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer esbuild@"^0.19.4" from esbuild-sass-plugin@2.16.0
npm ERR! node_modules/esbuild-sass-plugin
npm ERR!   esbuild-sass-plugin@"^2.16.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: esbuild@0.19.12
npm ERR! node_modules/esbuild
npm ERR!   peer esbuild@"^0.19.4" from esbuild-sass-plugin@2.16.0
npm ERR!   node_modules/esbuild-sass-plugin
npm ERR!     esbuild-sass-plugin@"^2.16.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2024-02-03T22_01_05_299Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-02-03T22_01_05_299Z-debug-0.log
### ⚠ Artifact update problem Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is. ♻ Renovate will retry this branch, including artifacts, only when one of the following happens: - any of the package files in this branch needs updating, or - the branch becomes conflicted, or - you click the rebase/retry checkbox if found above, or - you rename this PR's title to start with "rebase!" to trigger it manually The artifact failure details are included below: ##### File name: package-lock.json ``` npm ERR! code ERESOLVE npm ERR! ERESOLVE could not resolve npm ERR! npm ERR! While resolving: esbuild-sass-plugin@2.16.0 npm ERR! Found: esbuild@0.20.0 npm ERR! node_modules/esbuild npm ERR! dev esbuild@"^0.20.0" from the root project npm ERR! npm ERR! Could not resolve dependency: npm ERR! peer esbuild@"^0.19.4" from esbuild-sass-plugin@2.16.0 npm ERR! node_modules/esbuild-sass-plugin npm ERR! esbuild-sass-plugin@"^2.16.0" from the root project npm ERR! npm ERR! Conflicting peer dependency: esbuild@0.19.12 npm ERR! node_modules/esbuild npm ERR! peer esbuild@"^0.19.4" from esbuild-sass-plugin@2.16.0 npm ERR! node_modules/esbuild-sass-plugin npm ERR! esbuild-sass-plugin@"^2.16.0" from the root project npm ERR! npm ERR! Fix the upstream dependency conflict, or retry npm ERR! this command with --force or --legacy-peer-deps npm ERR! to accept an incorrect (and potentially broken) dependency resolution. npm ERR! npm ERR! npm ERR! For a full report see: npm ERR! /tmp/renovate/cache/others/npm/_logs/2024-02-03T22_01_05_299Z-eresolve-report.txt npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-02-03T22_01_05_299Z-debug-0.log ```
renovate changed title from chore(deps): update dependency esbuild to ^0.20.0 to chore(deps): update dependency esbuild to ^0.20.0 - autoclosed 2024-02-11 10:00:28 +00:00
renovate closed this pull request 2024-02-11 10:00:28 +00:00
Some checks failed
renovate/artifacts Artifact file update failure

Pull request closed

This pull request cannot be reopened because the branch was deleted.
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
renovate remoll
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: remoll/eth-physics#5
No description provided.
Delete Branch "renovate/esbuild-0.x"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?