Closed renovate[bot] closed 9 months ago
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:
The artifact failure details are included below:
/usr/local/bin/docker: line 4: .: filename argument required
.: usage: . filename [arguments]
[19:17:33.015] INFO (44): Downloading file ...
url: "https://github.com/containerbase/node-prebuild/releases/download/18.17.0/node-18.17.0-focal-x86_64.tar.xz.sha512"
output: "/tmp/worker/22caa4/e5fec1/cache/containerbase/4f1b66de1eebc4e832e9ad5a012165a5e79cd3b1c3892eb6646e768a14a95e7c/node-18.17.0-focal-x86_64.tar.xz.sha512"
[19:17:33.066] INFO (44): Download completed in 51ms.
[19:17:33.183] INFO (60): Downloading file ...
url: "https://github.com/containerbase/node-prebuild/releases/download/18.17.0/node-18.17.0-focal-x86_64.tar.xz"
output: "/tmp/worker/22caa4/e5fec1/cache/containerbase/d71155bd68a6dac4a334976c5d82cd47e91bf95aa8811a4ec27c615d8d82df76/node-18.17.0-focal-x86_64.tar.xz"
[19:17:33.424] INFO (60): Download completed in 241ms.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: @nx/esbuild@16.2.2
npm ERR! Found: esbuild@0.19.0
npm ERR! node_modules/esbuild
npm ERR! dev esbuild@"^0.19.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peerOptional esbuild@"~0.17.5" from @nx/esbuild@16.2.2
npm ERR! node_modules/@nx/esbuild
npm ERR! dev @nx/esbuild@"^16.2.2" from the root project
npm ERR! @nx/esbuild@"16.2.2" from @nrwl/esbuild@16.2.2
npm ERR! node_modules/@nrwl/esbuild
npm ERR! @nrwl/esbuild@"16.2.2" from @nx/esbuild@16.2.2
npm ERR!
npm ERR! Conflicting peer dependency: esbuild@0.17.19
npm ERR! node_modules/esbuild
npm ERR! peerOptional esbuild@"~0.17.5" from @nx/esbuild@16.2.2
npm ERR! node_modules/@nx/esbuild
npm ERR! dev @nx/esbuild@"^16.2.2" from the root project
npm ERR! @nx/esbuild@"16.2.2" from @nrwl/esbuild@16.2.2
npm ERR! node_modules/@nrwl/esbuild
npm ERR! @nrwl/esbuild@"16.2.2" from @nx/esbuild@16.2.2
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/worker/22caa4/e5fec1/cache/others/npm/_logs/2023-08-08T19_17_38_514Z-eresolve-report.txt
npm ERR! A complete log of this run can be found in: /tmp/worker/22caa4/e5fec1/cache/others/npm/_logs/2023-08-08T19_17_38_514Z-debug-0.log
This PR contains the following updates:
^0.17.17
->^0.19.0
Release Notes
evanw/esbuild (esbuild)
### [`v0.19.8`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0198) [Compare Source](https://togithub.com/evanw/esbuild/compare/v0.19.7...v0.19.8) - Add a treemap chart to esbuild's bundle analyzer ([#2848](https://togithub.com/evanw/esbuild/issues/2848)) The bundler analyzer on esbuild's website (https://esbuild.github.io/analyze/) now has a treemap chart type in addition to the two existing chart types (sunburst and flame). This should be more familiar for people coming from other similar tools, as well as make better use of large screens. - Allow decorators after the `export` keyword ([#104](https://togithub.com/evanw/esbuild/issues/104)) Previously esbuild's decorator parser followed the original behavior of TypeScript's experimental decorators feature, which only allowed decorators to come before the `export` keyword. However, the upcoming JavaScript decorators feature also allows decorators to come after the `export` keyword. And with TypeScript 5.0, TypeScript now also allows experimental decorators to come after the `export` keyword too. So esbuild now allows this as well: ```js // This old syntax has always been permitted: @decorator export class Foo {} @decorator export default class Foo {} // This new syntax is now permitted too: export @decorator class Foo {} export default @decorator class Foo {} ``` In addition, esbuild's decorator parser has been rewritten to fix several subtle and likely unimportant edge cases with esbuild's parsing of exports and decorators in TypeScript (e.g. TypeScript apparently does automatic semicolon insertion after `interface` and `export interface` but not after `export default interface`). - Pretty-print decorators using the same whitespace as the original When printing code containing decorators, esbuild will now try to respect whether the original code contained newlines after the decorator or not. This can make generated code containing many decorators much more compact to read: ```js // Original code class Foo { @a @b @c abc @x @y @z xyz } // Old output class Foo { @a @b @c abc; @x @y @z xyz; } // New output class Foo { @a @b @c abc; @x @y @z xyz; } ``` ### [`v0.19.7`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0197) [Compare Source](https://togithub.com/evanw/esbuild/compare/v0.19.6...v0.19.7) - Add support for bundling code that uses import attributes ([#3384](https://togithub.com/evanw/esbuild/issues/3384)) JavaScript is gaining new syntax for associating a map of string key-value pairs with individual ESM imports. The proposal is still a work in progress and is still undergoing significant changes before being finalized. However, the first iteration has already been shipping in Chromium-based browsers for a while, and the second iteration has landed in V8 and is now shipping in node, so it makes sense for esbuild to support it. Here are the two major iterations of this proposal (so far): 1. Import assertions (deprecated, will not be standardized) - Uses the `assert` keyword - Does *not* affect module resolution - Causes an error if the assertion fails - Shipping in Chrome 91+ (and in esbuild 0.11.22+) 2. Import attributes (currently set to become standardized) - Uses the `with` keyword - Affects module resolution - Unknown attributes cause an error - Shipping in node 21+ You can already use esbuild to bundle code that uses import assertions (the first iteration). However, this feature is mostly useless for bundlers because import assertions are not allowed to affect module resolution. It's basically only useful as an annotation on external imports, which esbuild will then preserve in the output for use in a browser (which would otherwise refuse to load certain imports). With this release, esbuild now supports bundling code that uses import attributes (the second iteration). This is much more useful for bundlers because they are allowed to affect module resolution, which means the key-value pairs can be provided to plugins. Here's an example, which uses esbuild's built-in support for the upcoming [JSON module standard](https://togithub.com/tc39/proposal-json-modules): ```js // On static imports import foo from './package.json' with { type: 'json' } console.log(foo) // On dynamic imports const bar = await import('./package.json', { with: { type: 'json' } }) console.log(bar) ``` One important consequence of the change in semantics between import assertions and import attributes is that two imports with identical paths but different import attributes are now considered to be different modules. This is because the import attributes are provided to the loader, which might then use those attributes during loading. For example, you could imagine an image loader that produces an image of a different size depending on the import attributes. Import attributes are now reported in the [metafile](https://esbuild.github.io/api/#metafile) and are now provided to [on-load plugins](https://esbuild.github.io/plugins/#on-load) as a map in the `with` property. For example, here's an esbuild plugin that turns all imports with a `type` import attribute equal to `'cheese'` into a module that exports the cheese emoji: ```js const cheesePlugin = { name: 'cheese', setup(build) { build.onLoad({ filter: /.*/ }, args => { if (args.with.type === 'cheese') return { contents: `export default "π§"`, } }) } } require('esbuild').build({ bundle: true, write: false, stdin: { contents: ` import foo from 'data:text/javascript,' with { type: 'cheese' } console.log(foo) `, }, plugins: [cheesePlugin], }).then(result => { const code = new Function(result.outputFiles[0].text) code() }) ``` Warning: It's possible that the second iteration of this feature may change significantly again even though it's already shipping in real JavaScript VMs (since it has already happened once before). In that case, esbuild may end up adjusting its implementation to match the eventual standard behavior. So keep in mind that by using this, you are using an unstable upcoming JavaScript feature that may undergo breaking changes in the future. - Adjust TypeScript experimental decorator behavior ([#3230](https://togithub.com/evanw/esbuild/issues/3230), [#3326](https://togithub.com/evanw/esbuild/issues/3326), [#3394](https://togithub.com/evanw/esbuild/issues/3394)) With this release, esbuild will now allow TypeScript experimental decorators to access both static class properties and `#private` class names. For example: ```js const check =Configuration
π Schedule: Branch creation - "after 10pm every weekday,every weekend,before 5am every weekday" (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.
π Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.