inhji/chiya
inhji
/
chiya
1
1
Fork 0
Code Issues 8 Pull Requests 9 Activity

Update dependency esbuild to v0.19.5 #323

Open
renovate wants to merge 1 commits from renovate/esbuild-0.x-lockfile into devel
pull from: renovate/esbuild-0.x-lockfile
merge into: inhji:devel
Conversation 0 Commits 1 Files Changed 1 +91 -91
renovate commented 2023-09-14 08:00:31 +02:00
Collaborator
Copy Link

This PR contains the following updates:

Package Type Update Change
esbuild devDependencies patch 0.19.2 -> 0.19.5

Release Notes

evanw/esbuild (esbuild)

v0.19.5

Compare Source

  • Fix a regression in 0.19.0 regarding paths in tsconfig.json (#​3354)

    The fix in esbuild version 0.19.0 to process tsconfig.json aliases before the --packages=external setting unintentionally broke an edge case in esbuild's handling of certain tsconfig.json aliases where there are multiple files with the same name in different directories. This release adjusts esbuild's behavior for this edge case so that it passes while still processing aliases before --packages=external. Please read the linked issue for more details.

  • Fix a CSS font property minification bug (#​3452)

    This release fixes a bug where esbuild's CSS minifier didn't insert a space between the font size and the font family in the font CSS shorthand property in the edge case where the original source code didn't already have a space and the leading string token was shortened to an identifier:

    /* Original code */
.foo { font: 16px"Menlo"; }

/* Old output (with --minify) */
.foo{font:16pxMenlo}

/* New output (with --minify) */
.foo{font:16px Menlo}

  • Fix bundling CSS with asset names containing spaces (#​3410)

    Assets referenced via CSS url() tokens may cause esbuild to generate invalid output when bundling if the file name contains spaces (e.g. url(image 2.png)). With this release, esbuild will now quote all bundled asset references in url() tokens to avoid this problem. This only affects assets loaded using the file and copy loaders.

  • Fix invalid CSS url() tokens in @import rules (#​3426)

    In the future, CSS url() tokens may contain additional stuff after the URL. This is irrelevant today as no CSS specification does this. But esbuild previously had a bug where using these tokens in an @import rule resulted in malformed output. This bug has been fixed.

  • Fix browser + false + type: module in package.json (#​3367)

    The browser field in package.json allows you to map a file to false to have it be treated as an empty file when bundling for the browser. However, if package.json contains "type": "module" then all .js files will be considered ESM, not CommonJS. Importing a named import from an empty CommonJS file gives you undefined, but importing a named export from an empty ESM file is a build error. This release changes esbuild's interpretation of these files mapped to false in this situation from ESM to CommonJS to avoid generating build errors for named imports.

  • Fix a bug in top-level await error reporting (#​3400)

    Using require() on a file that contains top-level await is not allowed because require() must return synchronously and top-level await makes that impossible. You will get a build error if you try to bundle code that does this with esbuild. This release fixes a bug in esbuild's error reporting code for complex cases of this situation involving multiple levels of imports to get to the module containing the top-level await.

  • Update to Unicode 15.1.0

    The character tables that determine which characters form valid JavaScript identifiers have been updated from Unicode version 15.0.0 to the newly-released Unicode version 15.1.0. I'm not putting an example in the release notes because all of the new characters will likely just show up as little squares since fonts haven't been updated yet. But you can read https://www.unicode.org/versions/Unicode15.1.0/#Summary for more information about the changes.

    This upgrade was contributed by @​JLHwung.

v0.19.4

Compare Source

  • Fix printing of JavaScript decorators in tricky cases (#​3396)

    This release fixes some bugs where esbuild's pretty-printing of JavaScript decorators could incorrectly produced code with a syntax error. The problem happened because esbuild sometimes substitutes identifiers for other expressions in the pretty-printer itself, but the decision about whether to wrap the expression or not didn't account for this. Here are some examples:

    // Original code
import { constant } from './constants.js'
import { imported } from 'external'
import { undef } from './empty.js'
class Foo {
  @​constant()
  @​imported()
  @​undef()
  foo
}

// Old output (with --bundle --format=cjs --packages=external --minify-syntax)
var import_external = require("external");
var Foo = class {
  @​123()
  @​(0, import_external.imported)()
  @​(void 0)()
  foo;
};

// New output (with --bundle --format=cjs --packages=external --minify-syntax)
var import_external = require("external");
var Foo = class {
  @​(123())
  @​((0, import_external.imported)())
  @​((void 0)())
  foo;
};

  • Allow pre-release versions to be passed to target (#​3388)

    People want to be able to pass version numbers for unreleased versions of node (which have extra stuff after the version numbers) to esbuild's target setting and have esbuild do something reasonable with them. These version strings are of course not present in esbuild's internal feature compatibility table because an unreleased version has not been released yet (by definition). With this release, esbuild will now attempt to accept these version strings passed to target and do something reasonable with them.

v0.19.3

Compare Source

  • Fix list-style-type with the local-css loader (#​3325)

    The local-css loader incorrectly treated all identifiers provided to list-style-type as a custom local identifier. That included identifiers such as none which have special meaning in CSS, and which should not be treated as custom local identifiers. This release fixes this bug:

    /* Original code */
ul { list-style-type: none }

/* Old output (with --loader=local-css) */
ul {
  list-style-type: stdin_none;
}

/* New output (with --loader=local-css) */
ul {
  list-style-type: none;
}

    Note that this bug only affected code using the local-css loader. It did not affect code using the css loader.

  • Avoid inserting temporary variables before use strict (#​3322)

    This release fixes a bug where esbuild could incorrectly insert automatically-generated temporary variables before use strict directives:

    // Original code
function foo() {
  'use strict'
  a.b?.c()
}

// Old output (with --target=es6)
function foo() {
  var _a;
  "use strict";
  (_a = a.b) == null ? void 0 : _a.c();
}

// New output (with --target=es6)
function foo() {
  "use strict";
  var _a;
  (_a = a.b) == null ? void 0 : _a.c();
}

  • Adjust TypeScript enum output to better approximate tsc (#​3329)

    TypeScript enum values can be either number literals or string literals. Numbers create a bidirectional mapping between the name and the value but strings only create a unidirectional mapping from the name to the value. When the enum value is neither a number literal nor a string literal, TypeScript and esbuild both default to treating it as a number:

    // Original TypeScript code
declare const foo: any
enum Foo {
  NUMBER = 1,
  STRING = 'a',
  OTHER = foo,
}

// Compiled JavaScript code (from "tsc")
var Foo;
(function (Foo) {
  Foo[Foo["NUMBER"] = 1] = "NUMBER";
  Foo["STRING"] = "a";
  Foo[Foo["OTHER"] = foo] = "OTHER";
})(Foo || (Foo = {}));

    However, TypeScript does constant folding slightly differently than esbuild. For example, it may consider template literals to be string literals in some cases:

    // Original TypeScript code
declare const foo = 'foo'
enum Foo {
  PRESENT = `${foo}`,
  MISSING = `${bar}`,
}

// Compiled JavaScript code (from "tsc")
var Foo;
(function (Foo) {
  Foo["PRESENT"] = "foo";
  Foo[Foo["MISSING"] = `${bar}`] = "MISSING";
})(Foo || (Foo = {}));

    The template literal initializer for PRESENT is treated as a string while the template literal initializer for MISSING is treated as a number. Previously esbuild treated both of these cases as a number but starting with this release, esbuild will now treat both of these cases as a string. This doesn't exactly match the behavior of tsc but in the case where the behavior diverges tsc reports a compile error, so this seems like acceptible behavior for esbuild. Note that handling these cases completely correctly would require esbuild to parse type declarations (see the declare keyword), which esbuild deliberately doesn't do.

  • Ignore case in CSS in more places (#​3316)

    This release makes esbuild's CSS support more case-agnostic, which better matches how browsers work. For example:

    /* Original code */
@​KeyFrames Foo { From { OpaCity: 0 } To { OpaCity: 1 } }
body { CoLoR: YeLLoW }

/* Old output (with --minify) */
@​KeyFrames Foo{From {OpaCity: 0} To {OpaCity: 1}}body{CoLoR:YeLLoW}

/* New output (with --minify) */
@​KeyFrames Foo{0%{OpaCity:0}To{OpaCity:1}}body{CoLoR:#ff0}

    Please never actually write code like this.

  • Improve the error message for null entries in exports (#​3377)

    Package authors can disable package export paths with the exports map in package.json. With this release, esbuild now has a clearer error message that points to the null token in package.json itself instead of to the surrounding context. Here is an example of the new error message:

    ✘ [ERROR] Could not resolve "msw/browser"

    lib/msw-config.ts:2:28:
      2 │ import { setupWorker } from 'msw/browser';
        ╵                             ~~~~~~~~~~~~~

  The path "./browser" cannot be imported from package "msw" because it was explicitly disabled by
  the package author here:

    node_modules/msw/package.json:17:14:
      17 │       "node": null,
         ╵               ~~~~

  You can mark the path "msw/browser" as external to exclude it from the bundle, which will remove
  this error and leave the unresolved path in the bundle.

  • Parse and print the with keyword in import statements

    JavaScript was going to have a feature called "import assertions" that adds an assert keyword to import statements. It looked like this:

    import stuff from './stuff.json' assert { type: 'json' }

    The feature provided a way to assert that the imported file is of a certain type (but was not allowed to affect how the import is interpreted, even though that's how everyone expected it to behave). The feature was fully specified and then actually implemented and shipped in Chrome before the people behind the feature realized that they should allow it to affect how the import is interpreted after all. So import assertions are no longer going to be added to the language.

    Instead, the current proposal is to add a feature called "import attributes" instead that adds a with keyword to import statements. It looks like this:

    import stuff from './stuff.json' with { type: 'json' }

    This feature provides a way to affect how the import is interpreted. With this release, esbuild now has preliminary support for parsing and printing this new with keyword. The with keyword is not yet interpreted by esbuild, however, so bundling code with it will generate a build error. All this release does is allow you to use esbuild to process code containing it (such as removing types from TypeScript code). Note that this syntax is not yet a part of JavaScript and may be removed or altered in the future if the specification changes (which it already has once, as described above). If that happens, esbuild reserves the right to remove or alter its support for this syntax too.

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 | patch | [`0.19.2` -> `0.19.5`](https://renovatebot.com/diffs/npm/esbuild/0.19.2/0.19.5) | --- ### Release Notes <details> <summary>evanw/esbuild (esbuild)</summary> ### [`v0.19.5`](https://github.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0195) [Compare Source](https://github.com/evanw/esbuild/compare/v0.19.4...v0.19.5) - Fix a regression in 0.19.0 regarding `paths` in `tsconfig.json` ([#&#8203;3354](https://github.com/evanw/esbuild/issues/3354)) The fix in esbuild version 0.19.0 to process `tsconfig.json` aliases before the `--packages=external` setting unintentionally broke an edge case in esbuild's handling of certain `tsconfig.json` aliases where there are multiple files with the same name in different directories. This release adjusts esbuild's behavior for this edge case so that it passes while still processing aliases before `--packages=external`. Please read the linked issue for more details. - Fix a CSS `font` property minification bug ([#&#8203;3452](https://github.com/evanw/esbuild/issues/3452)) This release fixes a bug where esbuild's CSS minifier didn't insert a space between the font size and the font family in the `font` CSS shorthand property in the edge case where the original source code didn't already have a space and the leading string token was shortened to an identifier: ```css /* Original code */ .foo { font: 16px"Menlo"; } /* Old output (with --minify) */ .foo{font:16pxMenlo} /* New output (with --minify) */ .foo{font:16px Menlo} ``` - Fix bundling CSS with asset names containing spaces ([#&#8203;3410](https://github.com/evanw/esbuild/issues/3410)) Assets referenced via CSS `url()` tokens may cause esbuild to generate invalid output when bundling if the file name contains spaces (e.g. `url(image 2.png)`). With this release, esbuild will now quote all bundled asset references in `url()` tokens to avoid this problem. This only affects assets loaded using the `file` and `copy` loaders. - Fix invalid CSS `url()` tokens in `@import` rules ([#&#8203;3426](https://github.com/evanw/esbuild/issues/3426)) In the future, CSS `url()` tokens may contain additional stuff after the URL. This is irrelevant today as no CSS specification does this. But esbuild previously had a bug where using these tokens in an `@import` rule resulted in malformed output. This bug has been fixed. - Fix `browser` + `false` + `type: module` in `package.json` ([#&#8203;3367](https://github.com/evanw/esbuild/issues/3367)) The `browser` field in `package.json` allows you to map a file to `false` to have it be treated as an empty file when bundling for the browser. However, if `package.json` contains `"type": "module"` then all `.js` files will be considered ESM, not CommonJS. Importing a named import from an empty CommonJS file gives you undefined, but importing a named export from an empty ESM file is a build error. This release changes esbuild's interpretation of these files mapped to `false` in this situation from ESM to CommonJS to avoid generating build errors for named imports. - Fix a bug in top-level await error reporting ([#&#8203;3400](https://github.com/evanw/esbuild/issues/3400)) Using `require()` on a file that contains [top-level await](https://v8.dev/features/top-level-await) is not allowed because `require()` must return synchronously and top-level await makes that impossible. You will get a build error if you try to bundle code that does this with esbuild. This release fixes a bug in esbuild's error reporting code for complex cases of this situation involving multiple levels of imports to get to the module containing the top-level await. - Update to Unicode 15.1.0 The character tables that determine which characters form valid JavaScript identifiers have been updated from Unicode version 15.0.0 to the newly-released Unicode version 15.1.0. I'm not putting an example in the release notes because all of the new characters will likely just show up as little squares since fonts haven't been updated yet. But you can read https://www.unicode.org/versions/Unicode15.1.0/#Summary for more information about the changes. This upgrade was contributed by [@&#8203;JLHwung](https://github.com/JLHwung). ### [`v0.19.4`](https://github.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0194) [Compare Source](https://github.com/evanw/esbuild/compare/v0.19.3...v0.19.4) - Fix printing of JavaScript decorators in tricky cases ([#&#8203;3396](https://github.com/evanw/esbuild/issues/3396)) This release fixes some bugs where esbuild's pretty-printing of JavaScript decorators could incorrectly produced code with a syntax error. The problem happened because esbuild sometimes substitutes identifiers for other expressions in the pretty-printer itself, but the decision about whether to wrap the expression or not didn't account for this. Here are some examples: ```js // Original code import { constant } from './constants.js' import { imported } from 'external' import { undef } from './empty.js' class Foo { @&#8203;constant() @&#8203;imported() @&#8203;undef() foo } // Old output (with --bundle --format=cjs --packages=external --minify-syntax) var import_external = require("external"); var Foo = class { @&#8203;123() @&#8203;(0, import_external.imported)() @&#8203;(void 0)() foo; }; // New output (with --bundle --format=cjs --packages=external --minify-syntax) var import_external = require("external"); var Foo = class { @&#8203;(123()) @&#8203;((0, import_external.imported)()) @&#8203;((void 0)()) foo; }; ``` - Allow pre-release versions to be passed to `target` ([#&#8203;3388](https://github.com/evanw/esbuild/issues/3388)) People want to be able to pass version numbers for unreleased versions of node (which have extra stuff after the version numbers) to esbuild's `target` setting and have esbuild do something reasonable with them. These version strings are of course not present in esbuild's internal feature compatibility table because an unreleased version has not been released yet (by definition). With this release, esbuild will now attempt to accept these version strings passed to `target` and do something reasonable with them. ### [`v0.19.3`](https://github.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0193) [Compare Source](https://github.com/evanw/esbuild/compare/v0.19.2...v0.19.3) - Fix `list-style-type` with the `local-css` loader ([#&#8203;3325](https://github.com/evanw/esbuild/issues/3325)) The `local-css` loader incorrectly treated all identifiers provided to `list-style-type` as a custom local identifier. That included identifiers such as `none` which have special meaning in CSS, and which should not be treated as custom local identifiers. This release fixes this bug: ```css /* Original code */ ul { list-style-type: none } /* Old output (with --loader=local-css) */ ul { list-style-type: stdin_none; } /* New output (with --loader=local-css) */ ul { list-style-type: none; } ``` Note that this bug only affected code using the `local-css` loader. It did not affect code using the `css` loader. - Avoid inserting temporary variables before `use strict` ([#&#8203;3322](https://github.com/evanw/esbuild/issues/3322)) This release fixes a bug where esbuild could incorrectly insert automatically-generated temporary variables before `use strict` directives: ```js // Original code function foo() { 'use strict' a.b?.c() } // Old output (with --target=es6) function foo() { var _a; "use strict"; (_a = a.b) == null ? void 0 : _a.c(); } // New output (with --target=es6) function foo() { "use strict"; var _a; (_a = a.b) == null ? void 0 : _a.c(); } ``` - Adjust TypeScript `enum` output to better approximate `tsc` ([#&#8203;3329](https://github.com/evanw/esbuild/issues/3329)) TypeScript enum values can be either number literals or string literals. Numbers create a bidirectional mapping between the name and the value but strings only create a unidirectional mapping from the name to the value. When the enum value is neither a number literal nor a string literal, TypeScript and esbuild both default to treating it as a number: ```ts // Original TypeScript code declare const foo: any enum Foo { NUMBER = 1, STRING = 'a', OTHER = foo, } // Compiled JavaScript code (from "tsc") var Foo; (function (Foo) { Foo[Foo["NUMBER"] = 1] = "NUMBER"; Foo["STRING"] = "a"; Foo[Foo["OTHER"] = foo] = "OTHER"; })(Foo || (Foo = {})); ``` However, TypeScript does constant folding slightly differently than esbuild. For example, it may consider template literals to be string literals in some cases: ```ts // Original TypeScript code declare const foo = 'foo' enum Foo { PRESENT = `${foo}`, MISSING = `${bar}`, } // Compiled JavaScript code (from "tsc") var Foo; (function (Foo) { Foo["PRESENT"] = "foo"; Foo[Foo["MISSING"] = `${bar}`] = "MISSING"; })(Foo || (Foo = {})); ``` The template literal initializer for `PRESENT` is treated as a string while the template literal initializer for `MISSING` is treated as a number. Previously esbuild treated both of these cases as a number but starting with this release, esbuild will now treat both of these cases as a string. This doesn't exactly match the behavior of `tsc` but in the case where the behavior diverges `tsc` reports a compile error, so this seems like acceptible behavior for esbuild. Note that handling these cases completely correctly would require esbuild to parse type declarations (see the `declare` keyword), which esbuild deliberately doesn't do. - Ignore case in CSS in more places ([#&#8203;3316](https://github.com/evanw/esbuild/issues/3316)) This release makes esbuild's CSS support more case-agnostic, which better matches how browsers work. For example: ```css /* Original code */ @&#8203;KeyFrames Foo { From { OpaCity: 0 } To { OpaCity: 1 } } body { CoLoR: YeLLoW } /* Old output (with --minify) */ @&#8203;KeyFrames Foo{From {OpaCity: 0} To {OpaCity: 1}}body{CoLoR:YeLLoW} /* New output (with --minify) */ @&#8203;KeyFrames Foo{0%{OpaCity:0}To{OpaCity:1}}body{CoLoR:#ff0} ``` Please never actually write code like this. - Improve the error message for `null` entries in `exports` ([#&#8203;3377](https://github.com/evanw/esbuild/issues/3377)) Package authors can disable package export paths with the `exports` map in `package.json`. With this release, esbuild now has a clearer error message that points to the `null` token in `package.json` itself instead of to the surrounding context. Here is an example of the new error message: ✘ [ERROR] Could not resolve "msw/browser" lib/msw-config.ts:2:28: 2 │ import { setupWorker } from 'msw/browser'; ╵ ~~~~~~~~~~~~~ The path "./browser" cannot be imported from package "msw" because it was explicitly disabled by the package author here: node_modules/msw/package.json:17:14: 17 │ "node": null, ╵ ~~~~ You can mark the path "msw/browser" as external to exclude it from the bundle, which will remove this error and leave the unresolved path in the bundle. - Parse and print the `with` keyword in `import` statements JavaScript was going to have a feature called "import assertions" that adds an `assert` keyword to `import` statements. It looked like this: ```js import stuff from './stuff.json' assert { type: 'json' } ``` The feature provided a way to assert that the imported file is of a certain type (but was not allowed to affect how the import is interpreted, even though that's how everyone expected it to behave). The feature was fully specified and then actually implemented and shipped in Chrome before the people behind the feature realized that they should allow it to affect how the import is interpreted after all. So import assertions are no longer going to be added to the language. Instead, the [current proposal](https://github.com/tc39/proposal-import-attributes) is to add a feature called "import attributes" instead that adds a `with` keyword to import statements. It looks like this: ```js import stuff from './stuff.json' with { type: 'json' } ``` This feature provides a way to affect how the import is interpreted. With this release, esbuild now has preliminary support for parsing and printing this new `with` keyword. The `with` keyword is not yet interpreted by esbuild, however, so bundling code with it will generate a build error. All this release does is allow you to use esbuild to process code containing it (such as removing types from TypeScript code). Note that this syntax is not yet a part of JavaScript and may be removed or altered in the future if the specification changes (which it already has once, as described above). If that happens, esbuild reserves the right to remove or alter its support for this syntax too. </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:eyJjcmVhdGVkSW5WZXIiOiIzNi4yNS41IiwidXBkYXRlZEluVmVyIjoiMzcuMC4xIiwidGFyZ2V0QnJhbmNoIjoiZGV2ZWwifQ==-->
renovate added 1 commit 2023-09-14 08:00:32 +02:00
renovate force-pushed renovate/esbuild-0.x-lockfile from 6dd649a180 to 5c27859fb8 2023-09-20 15:00:29 +02:00 Compare
renovate force-pushed renovate/esbuild-0.x-lockfile from 5c27859fb8 to 006488bb2b 2023-09-21 13:10:25 +02:00 Compare
renovate force-pushed renovate/esbuild-0.x-lockfile from 006488bb2b to 0ddc7e3409 2023-09-21 13:20:25 +02:00 Compare
renovate force-pushed renovate/esbuild-0.x-lockfile from 0ddc7e3409 to 73b269dfba 2023-09-21 13:30:26 +02:00 Compare
renovate force-pushed renovate/esbuild-0.x-lockfile from 73b269dfba to c0774102c2 2023-09-21 13:40:27 +02:00 Compare
renovate force-pushed renovate/esbuild-0.x-lockfile from c0774102c2 to 16d34e0aa3 2023-09-21 15:00:27 +02:00 Compare
renovate force-pushed renovate/esbuild-0.x-lockfile from 16d34e0aa3 to 5fd0053131 2023-09-21 15:20:25 +02:00 Compare
renovate force-pushed renovate/esbuild-0.x-lockfile from 5fd0053131 to 045bded157 2023-09-21 15:40:25 +02:00 Compare
renovate force-pushed renovate/esbuild-0.x-lockfile from 045bded157 to 432a658e4f 2023-09-22 11:20:28 +02:00 Compare
renovate force-pushed renovate/esbuild-0.x-lockfile from 432a658e4f to 1a5ec65aeb 2023-09-22 12:00:25 +02:00 Compare
renovate force-pushed renovate/esbuild-0.x-lockfile from 1a5ec65aeb to 3f71d12381 2023-09-22 14:20:25 +02:00 Compare
renovate force-pushed renovate/esbuild-0.x-lockfile from 3f71d12381 to f0fef23890 2023-09-22 14:30:26 +02:00 Compare
renovate force-pushed renovate/esbuild-0.x-lockfile from f0fef23890 to 54f4a20c78 2023-09-23 22:50:26 +02:00 Compare
renovate force-pushed renovate/esbuild-0.x-lockfile from 54f4a20c78 to 0e0699d2bb 2023-09-24 11:10:32 +02:00 Compare
renovate force-pushed renovate/esbuild-0.x-lockfile from 0e0699d2bb to 29bfdabeee 2023-09-26 10:50:26 +02:00 Compare
renovate force-pushed renovate/esbuild-0.x-lockfile from 29bfdabeee to 8287eeeaeb 2023-09-26 11:20:28 +02:00 Compare
renovate force-pushed renovate/esbuild-0.x-lockfile from 8287eeeaeb to fc082a49c4 2023-09-27 16:38:33 +02:00 Compare
renovate force-pushed renovate/esbuild-0.x-lockfile from fc082a49c4 to 4de36b3e45 2023-09-28 08:00:22 +02:00 Compare
renovate changed title from Update dependency esbuild to v0.19.3 to Update dependency esbuild to v0.19.4 2023-09-28 08:00:25 +02:00
renovate force-pushed renovate/esbuild-0.x-lockfile from 4de36b3e45 to 513b5ad6ec 2023-09-30 13:00:23 +02:00 Compare
renovate force-pushed renovate/esbuild-0.x-lockfile from 513b5ad6ec to 157d6c4310 2023-10-17 08:00:24 +02:00 Compare
renovate changed title from Update dependency esbuild to v0.19.4 to Update dependency esbuild to v0.19.5 2023-10-17 08:00:27 +02:00
renovate force-pushed renovate/esbuild-0.x-lockfile from 157d6c4310 to 8d2d58d3b7 2023-10-30 21:01:33 +01:00 Compare
renovate force-pushed renovate/esbuild-0.x-lockfile from 8d2d58d3b7 to 3dfc9f5195 2023-10-30 21:20:33 +01:00 Compare
This pull request can be merged automatically.
You are not authorized to merge this pull request.
You can also view command line instructions.

Step 1:

From your project repository, check out a new branch and test the changes.
git checkout -b renovate/esbuild-0.x-lockfile devel
git pull origin renovate/esbuild-0.x-lockfile

Step 2:

Merge the changes and update on Forgejo.
git checkout devel
git merge --no-ff renovate/esbuild-0.x-lockfile
git push origin devel
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
ActivityPub

   
Bug

   
Indie/Micropub

   
Indie/Microsub

   
Indie/Webmention

   
Special/MEGA

   
Special/Renovate
No Label
ActivityPub
Bug
Indie/Micropub
Indie/Microsub
Indie/Webmention
Special/MEGA
Special/Renovate
Milestone
Clear milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Reference: inhji/chiya#323
No description provided.
Delete Branch "renovate/esbuild-0.x-lockfile"

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?