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

fix(deps): update all non-major dependencies #101

Merged
merged 2 commits into from
Mar 1, 2025
Merged

fix(deps): update all non-major dependencies #101

merged 2 commits into from
Mar 1, 2025

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 1, 2025 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@antfu/eslint-config ^4.1.1 -> ^4.3.0 age adoption passing confidence
@eslint/js (source) ^9.17.0 -> ^9.21.0 age adoption passing confidence
@swc/core (source) ^1.10.14 -> ^1.11.5 age adoption passing confidence
@types/node (source) ^22.13.1 -> ^22.13.7 age adoption passing confidence
bumpp ^10.0.1 -> ^10.0.3 age adoption passing confidence
esbuild ^0.24.2 -> ^0.25.0 age adoption passing confidence
eslint (source) ^9.5.0 -> ^9.21.0 age adoption passing confidence
eslint (source) ^9.19.0 -> ^9.21.0 age adoption passing confidence
importx ^0.5.1 -> ^0.5.2 age adoption passing confidence
octokit ^4.1.0 -> ^4.1.2 age adoption passing confidence
pnpm (source) 10.2.0 -> 10.5.2 age adoption passing confidence
tinyglobby ^0.2.10 -> ^0.2.12 age adoption passing confidence
tsx (source) ^4.19.2 -> ^4.19.3 age adoption passing confidence
typescript (source) ^5.7.3 -> ^5.8.2 age adoption passing confidence
typescript-eslint (source) ^8.18.2 -> ^8.25.0 age adoption passing confidence
unbuild ^3.3.1 -> ^3.5.0 age adoption passing confidence
vitest (source) ^3.0.5 -> ^3.0.7 age adoption passing confidence

Release Notes

antfu/eslint-config (@​antfu/eslint-config)

v4.3.0

Compare Source

   🚀 Features
   🏎 Performance
    View changes on GitHub

v4.2.1

Compare Source

   🚀 Features
    View changes on GitHub

v4.2.0

Compare Source

   🚀 Features
    View changes on GitHub
eslint/eslint (@​eslint/js)

v9.21.0

Compare Source

Features
Bug Fixes
  • db5340d fix: update missing plugin message template (#​19445) (Milos Djermanovic)
  • d8ffdd4 fix: do not exit process on rule crash (#​19436) (Francesco Trotta)
Documentation
  • c5561ea docs: Update README (GitHub Actions Bot)
  • 80b0485 docs: replace var with let and const in rule example (#​19434) (Tanuj Kanti)
  • f67d5e8 docs: Update README (GitHub Actions Bot)
  • 75afc61 docs: Update README (GitHub Actions Bot)
  • 0636cab docs: Update Eleventy from v2 to v3 (#​19415) (Amaresh S M)
  • dd7d930 docs: Update README (GitHub Actions Bot)
Chores
  • a8c9a9f chore: update @eslint/eslintrc and @eslint/js (#​19453) (Francesco Trotta)
  • 265e0cf chore: package.json update for @​eslint/js release (Jenkins)
  • 3401b85 test: add test for Rule.ReportDescriptor type (#​19449) (Francesco Trotta)
  • e497aa7 chore: update rewrite dependencies (#​19448) (Francesco Trotta)
  • dab5478 chore: better error message for missing plugin in config (#​19402) (Tanuj Kanti)
  • ebfe2eb chore: set js language for bug report issue config block (#​19439) (Josh Goldberg ✨)
  • 5fd211d test: processors can return subpaths (#​19425) (Milos Djermanovic)

v9.20.0

Compare Source

Features

  • e89a54a feat: change behavior of inactive flags (#​19386) (Milos Djermanovic)

Bug Fixes

  • 91d4d9f fix: Bring types in sync with @​eslint/core (#​19157) (Nicholas C. Zakas)
  • fa25c7a fix: Emit warning when empty config file is used (#​19399) (Nicholas C. Zakas)
  • 31a9fd0 fix: Clearer error message for wrong plugin format (#​19380) (Nicholas C. Zakas)
  • 61d99e3 fix: Better error message for unserializable parser (#​19384) (Nicholas C. Zakas)
  • db1b9a6 fix: Ensure module scope is checked for references in consistent-this (#​19383) (Nicholas C. Zakas)
  • 8bcd820 fix: arrow-body-style crash with single-token body (#​19379) (Milos Djermanovic)

Documentation

  • b7012c8 docs: rewrite examples with var using let and const (#​19407) (Mueez Javaid Hashmi)
  • 6406376 docs: Update README (GitHub Actions Bot)
  • 350f2b9 docs: rewrite some examples with var using let and const (#​19404) (Mueez Javaid Hashmi)
  • 93c325a docs: rewrite examples with var using let and const (#​19398) (Mueez Javaid Hashmi)
  • 56ff404 docs: replace var with let or const in rules docs (#​19396) (Daniel Harbrueger)
  • 4053226 docs: change sourceType in no-eval examples (#​19393) (Milos Djermanovic)
  • 1324af0 docs: replace var with let and const in rules docs (#​19392) (Daniel Harbrueger)
  • 8b87e00 docs: replace var with const and let in rules (#​19389) (Tanuj Kanti)
  • 758c66b docs: Explain what frozen rules mean (#​19382) (Nicholas C. Zakas)
  • 0ef8bb8 docs: additional checks for rule examples (#​19358) (Milos Djermanovic)
  • 58ab2f6 docs: fix order of installation steps in getting started (#​19326) (Tanuj Kanti)

Chores

swc-project/swc (@​swc/core)

v1.11.5

Compare Source

Bug Fixes

  • (es/lints) Capture errors and emit from the original thread (#​10119) (2304cd8)

  • (es/minifier) Skip inlining if the referential identity of a function matters (#​10123) (c08fe8d)

  • (ts/fast-strip) Throw object consistently (#​10122) (010ff2a)

Miscellaneous Tasks
Performance

v1.11.4

Compare Source

Bug Fixes
Miscellaneous Tasks
Performance
Refactor

v1.11.1

Compare Source

Bug Fixes
Documentation
Features
Miscellaneous Tasks
Performance
Refactor

v1.10.18

Compare Source

Bug Fixes
Miscellaneous Tasks
  • (es/minifier) Make minify-all example ignore parsing errors (#​10045) (6c7ec46)
Build

v1.10.17

Compare Source

Bug Fixes
Performance
Testing

v1.10.16

Compare Source

Bug Fixes

  • (es/minifier) Check assign target before merge assign cond (#​10020) (6dab49a)

  • (es/parser) Preserve comment positions with leading semicolon (#​10019) (c9937b6)

  • (swc_common) Fix panic with non-narrow chars with width != 2 (#​10011) (f9f4cac)

  • (ts/fast-strip) Handle unsupported module keyword (#​10022) (308f5d0)

Performance

v1.10.15

Compare Source

Bug Fixes
Features
Performance
antfu-collective/bumpp (bumpp)

v10.0.3

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v10.0.2

Compare Source

No significant changes

    View changes on GitHub
evanw/esbuild (esbuild)

v0.25.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.24.0 or ~0.24.0. See npm's documentation about semver for more information.

  • Restrict access to esbuild's development server (GHSA-67mh-4wv8-2f99)

    This change addresses esbuild's first security vulnerability report. Previously esbuild set the Access-Control-Allow-Origin header to * to allow esbuild's development server to be flexible in how it's used for development. However, this allows the websites you visit to make HTTP requests to esbuild's local development server, which gives read-only access to your source code if the website were to fetch your source code's specific URL. You can read more information in the report.

    Starting with this release, CORS will now be disabled, and requests will now be denied if the host does not match the one provided to --serve=. The default host is 0.0.0.0, which refers to all of the IP addresses that represent the local machine (e.g. both 127.0.0.1 and 192.168.0.1). If you want to customize anything about esbuild's development server, you can put a proxy in front of esbuild and modify the incoming and/or outgoing requests.

    In addition, the serve() API call has been changed to return an array of hosts instead of a single host string. This makes it possible to determine all of the hosts that esbuild's development server will accept.

    Thanks to @​sapphi-red for reporting this issue.

  • Delete output files when a build fails in watch mode (#​3643)

    It has been requested for esbuild to delete files when a build fails in watch mode. Previously esbuild left the old files in place, which could cause people to not immediately realize that the most recent build failed. With this release, esbuild will now delete all output files if a rebuild fails. Fixing the build error and triggering another rebuild will restore all output files again.

  • Fix correctness issues with the CSS nesting transform (#​3620, #​3877, #​3933, #​3997, #​4005, #​4037, #​4038)

    This release fixes the following problems:

    • Naive expansion of CSS nesting can result in an exponential blow-up of generated CSS if each nesting level has multiple selectors. Previously esbuild sometimes collapsed individual nesting levels using :is() to limit expansion. However, this collapsing wasn't correct in some cases, so it has been removed to fix correctness issues.

      /* Original code */
.parent {
  > .a,
  > .b1 > .b2 {
    color: red;
  }
}

/* Old output (with --supported:nesting=false) */
.parent > :is(.a, .b1 > .b2) {
  color: red;
}

/* New output (with --supported:nesting=false) */
.parent > .a,
.parent > .b1 > .b2 {
  color: red;
}

      Thanks to @​tim-we for working on a fix.

    • The & CSS nesting selector can be repeated multiple times to increase CSS specificity. Previously esbuild ignored this possibility and incorrectly considered && to have the same specificity as &. With this release, this should now work correctly:

      /* Original code (color should be red) */
div {
  && { color: red }
  & { color: blue }
}

/* Old output (with --supported:nesting=false) */
div {
  color: red;
}
div {
  color: blue;
}

/* New output (with --supported:nesting=false) */
div:is(div) {
  color: red;
}
div {
  color: blue;
}

      Thanks to @​CPunisher for working on a fix.

    • Previously transforming nested CSS incorrectly removed leading combinators from within pseudoclass selectors such as :where(). This edge case has been fixed and how has test coverage.

      /* Original code */
a b:has(> span) {
  a & {
    color: green;
  }
}

/* Old output (with --supported:nesting=false) */
a :is(a b:has(span)) {
  color: green;
}

/* New output (with --supported:nesting=false) */
a :is(a b:has(> span)) {
  color: green;
}

      This fix was contributed by @​NoremacNergfol.

    • The CSS minifier contains logic to remove the & selector when it can be implied, which happens when there is only one and it's the leading token. However, this logic was incorrectly also applied to selector lists inside of pseudo-class selectors such as :where(). With this release, the minifier will now avoid applying this logic in this edge case:

      /* Original code */
.a {
  & .b { color: red }
  :where(& .b) { color: blue }
}

/* Old output (with --minify) */
.a{.b{color:red}:where(.b){color:#​00f}}

/* New output (with --minify) */
.a{.b{color:red}:where(& .b){color:#​00f}}

  • Fix some correctness issues with source maps (#​1745, #​3183, #​3613, #​3982)

    Previously esbuild incorrectly treated source map path references as file paths instead of as URLs. With this release, esbuild will now treat source map path references as URLs. This fixes the following problems with source maps:

    • File names in sourceMappingURL that contained a space previously did not encode the space as %20, which resulted in JavaScript tools (including esbuild) failing to read that path back in when consuming the generated output file. This should now be fixed.

    • Absolute URLs in sourceMappingURL that use the file:// scheme previously attempted to read from a folder called file:. These URLs should now be recognized and parsed correctly.

    • Entries in the sources array in the source map are now treated as URLs instead of file paths. The correct behavior for this is much more clear now that source maps has a formal specification. Many thanks to those who worked on the specification.

  • Fix incorrect package for @esbuild/netbsd-arm64 (#​4018)

    Due to a copy+paste typo, the binary published to @esbuild/netbsd-arm64 was not actually for arm64, and didn't run in that environment. This release should fix running esbuild in that environment (NetBSD on 64-bit ARM). Sorry about the mistake.

  • Fix a minification bug with bitwise operators and bigints (#​4065)

    This change removes an incorrect assumption in esbuild that all bitwise operators result in a numeric integer. That assumption was correct up until the introduction of bigints in ES2020, but is no longer correct because almost all bitwise operators now operate on both numbers and bigints. Here's an example of the incorrect minification:

    // Original code
if ((a & b) !== 0) found = true

// Old output (with --minify)
a&b&&(found=!0);

// New output (with --minify)
(a&b)!==0&&(found=!0);

  • Fix esbuild incorrectly rejecting valid TypeScript edge case (#​4027)

    The following TypeScript code is valid:

    export function open(async?: boolean): void {
  console.log(async as boolean)
}

    Before this version, esbuild would fail to parse this with a syntax error as it expected the token sequence async as ... to be the start of an async arrow function expression async as => .... This edge case should be parsed correctly by esbuild starting with this release.

  • Transform BigInt values into constructor calls when unsupported (#​4049)

    Previously esbuild would refuse to compile the BigInt literals (such as 123n) if they are unsupported in the configured target environment (such as with --target=es6). The rationale was that they cannot be polyfilled effectively because they change the behavior of JavaScript's arithmetic operators and JavaScript doesn't have operator overloading.

    However, this prevents using esbuild with certain libraries that would otherwise work if BigInt literals were ignored, such as with old versions of the buffer library before the library fixed support for running in environments without BigInt support. So with this release, esbuild will now turn BigInt literals into BigInt constructor calls (so 123n becomes BigInt(123)) and generate a warning in this case. You can turn off the warning with --log-override:bigint=silent or restore the warning to an error with --log-override:bigint=error if needed.

  • Change how console API dropping works (#​4020)

    Previously the --drop:console feature replaced all method calls off of the console global with undefined regardless of how long the property access chain was (so it applied to console.log() and console.log.call(console) and console.log.not.a.method()). However, it was pointed out that this breaks uses of console.log.bind(console). That's also incompatible with Terser's implementation of the feature, which is where this feature originally came from (it does support bind). So with this release, using this feature with esbuild will now only replace one level of method call (unless extended by call or apply) and will replace the method being called with an empty function in complex cases:

    // Original code
const x = console.log('x')
const y = console.log.call(console, 'y')
const z = console.log.bind(console)('z')

// Old output (with --drop-console)
const x = void 0;
const y = void 0;
const z = (void 0)("z");

// New output (with --drop-console)
const x = void 0;
const y = void 0;
const z = (() => {
}).bind(console)("z");

    This should more closely match Terser's existing behavior.

  • Allow BigInt literals as define values

    With this release, you can now use BigInt literals as define values, such as with --define:FOO=123n. Previously trying to do this resulted in a syntax error.

  • Fix a bug with resolve extensions in node_modules (#​4053)

    The --resolve-extensions= option lets you specify the order in which to try resolving implicit file extensions. For complicated reasons, esbuild reorders TypeScript file extensions after JavaScript ones inside of node_modules so that JavaScript source code is always preferred to TypeScript source code inside of dependencies. However, this reordering had a bug that could accidentally change the relative order of TypeScript file extensions if one of them was a prefix of the other. That bug has been fixed in this release. You can see the issue for details.

  • Better minification of statically-determined switch cases (#​4028)

    With this release, esbuild will now try to trim unused code within switch statements when the test expression and case expressions are primitive literals. This can arise when the test expression is an identifier that is substituted for a primitive literal at compile time. For example:

    // Original code
switch (MODE) {
  case 'dev':
    installDevToolsConsole()
    break
  case 'prod':
    return
  default:
    throw new Error
}

// Old output (with --minify '--define:MODE="prod"')
switch("prod"){case"dev":installDevToolsConsole();break;case"prod":return;default:throw new Error}

// New output (with --minify '--define:MODE="prod"')
return;

  • Emit /* @​__KEY__ */ for string literals derived from property names (#​4034)

    Property name mangling is an advanced feature that shortens certain property names for better minification (I say "advanced feature" because it's very easy to break your code with it). Sometimes you need to store a property name in a string, such as obj.get('foo') instead of obj.foo. JavaScript minifiers such as esbuild and Terser have a convention where a /* @​__KEY__ */ comment before the string makes it behave like a property name. So obj.get(/* @​__KEY__ */ 'foo') allows the contents of the string 'foo' to be shortened.

    However, esbuild sometimes itself generates string literals containing property names when transforming code, such as when lowering class fields to ES6 or when transforming TypeScript decorators. Previously esbuild didn't generate its own /* @​__KEY__ */ comments in this case, which means that minifying your code by running esbuild again on its own output wouldn't work correctly (this does not affect people that both minify and transform their code in a single step

Configuration

📅 Schedule: Branch creation - "* 0-3 1 * *" (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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the dependencies label Mar 1, 2025
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 152f623 to 814a649 Compare March 1, 2025 02:24
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 814a649 to 7cf459c Compare March 1, 2025 02:27
@pkg-pr-new pkg.pr.new
Copy link

pkg-pr-new bot commented Mar 1, 2025 

npm i https://pkg.pr.new/@zotero-plugin/eslint-config@101

npm i https://pkg.pr.new/zotero-plugin-scaffold@101

commit: a8554ef

@northword northword merged commit 304dafb into main Mar 1, 2025
6 checks passed
@northword northword deleted the renovate/all-minor-patch branch March 1, 2025 03:57
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.
1 participant
@northword