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

chore(deps): update all non-major dependencies #823

Merged
merged 1 commit into from
Dec 26, 2023
Merged

chore(deps): update all non-major dependencies #823

merged 1 commit into from
Dec 26, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 18, 2023 •
edited
Loading

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@sveltejs/kit (source) ^1.28.0 -> ^1.30.3 age adoption passing confidence
@sveltejs/package (source) ^2.2.3 -> ^2.2.4 age adoption passing confidence
@typescript-eslint/eslint-plugin (source) ^6.14.0 -> ^6.16.0 age adoption passing confidence
@typescript-eslint/parser (source) ^6.14.0 -> ^6.16.0 age adoption passing confidence
carbon-components-svelte ^0.82.4 -> ^0.82.7 age adoption passing confidence
carbon-icons-svelte ^12.4.0 -> ^12.4.2 age adoption passing confidence
dts-buddy ^0.4.2 -> ^0.4.3 age adoption passing confidence
esbuild ^0.19.9 -> ^0.19.10 age adoption passing confidence
eslint (source) ^8.55.0 -> ^8.56.0 age adoption passing confidence
eslint-plugin-n ^16.4.0 -> ^16.5.0 age adoption passing confidence
eslint-plugin-prettier ^5.0.1 -> ^5.1.2 age adoption passing confidence
pnpm (source) 8.12.0 -> 8.12.1 age adoption passing confidence
publint (source) ^0.2.6 -> ^0.2.7 age adoption passing confidence
sirv ^2.0.3 -> ^2.0.4 age adoption passing confidence
svelte-preprocess ^5.1.1 -> ^5.1.3 age adoption passing confidence
vite (source) ^5.0.7 -> ^5.0.10 age adoption passing confidence
vitest (source) ^1.0.4 -> ^1.1.0 age adoption passing confidence

Release Notes

sveltejs/kit (@​sveltejs/kit)

v1.30.3

Compare Source

Patch Changes
  • fix: correct documentation for beforeNavigate (#​11300)

v1.30.2

Compare Source

Patch Changes
  • fix: revert recent 'correctly return 415' and 'correctly return 404' changes (#​11295)

v1.30.1

Compare Source

Patch Changes

  • fix: prerendered root page with paths.base config uses correct trailing slash option (#​10763)

  • fix: correctly return 404 when a form action is not found (#​11278)

v1.30.0

Compare Source

Minor Changes
  • feat: inline response.arrayBuffer() during ssr (#​10535)
Patch Changes

  • fix: allow "false" value for preload link options (#​10555)

  • fix: call worker unref instead of terminate (#​10120)

  • fix: correctly analyse exported server API methods during build (#​11019)

  • fix: avoid error when back navigating before page is initialized (#​10636)

  • fix: allow service-worker.js to import assets (#​9285)

  • fix: distinguish better between not-found and internal-error (#​11131)

v1.29.1

Compare Source

Patch Changes

  • fix: correctly return 415 when unexpected content types are submitted to actions (#​11255)

  • chore: deprecate preloadCode calls with multiple arguments (#​11266)

v1.29.0

Compare Source

Minor Changes
  • feat: add resolveRoute to $app/paths, deprecate resolvePath (#​11261)
sveltejs/kit (@​sveltejs/package)

v2.2.4

Compare Source

Patch Changes
typescript-eslint/typescript-eslint (@​typescript-eslint/eslint-plugin)

v6.16.0

Compare Source

Bug Fixes
  • eslint-plugin: [unbound-method] exempt all non-Promise built-in statics (#​8096) (3182959)
Features
  • eslint-plugin: deprecate formatting (meta.type: layout) rules (#​8073) (04dea84)
  • eslint-plugin: deprecate no-extra-semi in favor of ESLint Stylistic equivalent (#​8123) (9368bf3)

You can read about our versioning strategy and releases on our website.

v6.15.0

Compare Source

Features

You can read about our versioning strategy and releases on our website.

typescript-eslint/typescript-eslint (@​typescript-eslint/parser)

v6.16.0

Compare Source

Note: Version bump only for package @​typescript-eslint/parser

You can read about our versioning strategy and releases on our website.

v6.15.0

Compare Source

Note: Version bump only for package @​typescript-eslint/parser

You can read about our versioning strategy and releases on our website.

carbon-design-system/carbon-components-svelte (carbon-components-svelte)

v0.82.7

Compare Source

v0.82.6

Compare Source

v0.82.5

Compare Source

carbon-design-system/carbon-icons-svelte (carbon-icons-svelte)

v12.4.2

Compare Source

Fixes

  • add types to exports map in package.json

v12.4.1

Compare Source

Fixes

  • add exports to package.json
Rich-Harris/dts-buddy (dts-buddy)

v0.4.3

Compare Source

  • Fix path resolution on Windows (#​71)
evanw/esbuild (esbuild)

v0.19.10

Compare Source

  • Fix glob imports in TypeScript files (#​3319)

    This release fixes a problem where bundling a TypeScript file containing a glob import could emit a call to a helper function that doesn't exist. The problem happened because esbuild's TypeScript transformation removes unused imports (which is required for correctness, as they may be type-only imports) and esbuild's glob import transformation wasn't correctly marking the imported helper function as used. This wasn't caught earlier because most of esbuild's glob import tests were written in JavaScript, not in TypeScript.

  • Fix require() glob imports with bundling disabled (#​3546)

    Previously require() calls containing glob imports were incorrectly transformed when bundling was disabled. All glob imports should only be transformed when bundling is enabled. This bug has been fixed.

  • Fix a panic when transforming optional chaining with define (#​3551, #​3554)

    This release fixes a case where esbuild could crash with a panic, which was triggered by using define to replace an expression containing an optional chain. Here is an example:

    // Original code
console.log(process?.env.SHELL)

// Old output (with --define:process.env={})
/* panic: Internal error (while parsing "<stdin>") */

// New output (with --define:process.env={})
var define_process_env_default = {};
console.log(define_process_env_default.SHELL);

    This fix was contributed by @​hi-ogawa.

  • Work around a bug in node's CommonJS export name detector (#​3544)

    The export names of a CommonJS module are dynamically-determined at run time because CommonJS exports are properties on a mutable object. But the export names of an ES module are statically-determined at module instantiation time by using import and export syntax and cannot be changed at run time.

    When you import a CommonJS module into an ES module in node, node scans over the source code to attempt to detect the set of export names that the CommonJS module will end up using. That statically-determined set of names is used as the set of names that the ES module is allowed to import at module instantiation time. However, this scan appears to have bugs (or at least, can cause false positives) because it doesn't appear to do any scope analysis. Node will incorrectly consider the module to export something even if the assignment is done to a local variable instead of to the module-level exports object. For example:

    // confuseNode.js
exports.confuseNode = function(exports) {
  // If this local is called "exports", node incorrectly
  // thinks this file has an export called "notAnExport".
  exports.notAnExport = function() {
  };
};

    You can see that node incorrectly thinks the file confuseNode.js has an export called notAnExport when that file is loaded in an ES module context:

    $ node -e 'import("./confuseNode.js").then(console.log)'
[Module: null prototype] {
  confuseNode: [Function (anonymous)],
  default: { confuseNode: [Function (anonymous)] },
  notAnExport: undefined
}

    To avoid this, esbuild will now rename local variables that use the names exports and module when generating CommonJS output for the node platform.

  • Fix the return value of esbuild's super() shim (#​3538)

    Some people write constructor methods that use the return value of super() instead of using this. This isn't too common because TypeScript doesn't let you do that but it can come up when writing JavaScript. Previously esbuild's class lowering transform incorrectly transformed the return value of super() into undefined. With this release, the return value of super() will now be this instead:

    // Original code
class Foo extends Object {
  field
  constructor() {
    console.log(typeof super())
  }
}
new Foo

// Old output (with --target=es6)
class Foo extends Object {
  constructor() {
    var __super = (...args) => {
      super(...args);
      __publicField(this, "field");
    };
    console.log(typeof __super());
  }
}
new Foo();

// New output (with --target=es6)
class Foo extends Object {
  constructor() {
    var __super = (...args) => {
      super(...args);
      __publicField(this, "field");
      return this;
    };
    console.log(typeof __super());
  }
}
new Foo();

  • Terminate the Go GC when esbuild's stop() API is called (#​3552)

    If you use esbuild with WebAssembly and pass the worker: false flag to esbuild.initialize(), then esbuild will run the WebAssembly module on the main thread. If you do this within a Deno test and that test calls esbuild.stop() to clean up esbuild's resources, Deno may complain that a setTimeout() call lasted past the end of the test. This happens when the Go is in the middle of a garbage collection pass and has scheduled additional ongoing garbage collection work. Normally calling esbuild.stop() will terminate the web worker that the WebAssembly module runs in, which will terminate the Go GC, but that doesn't happen if you disable the web worker with worker: false.

    With this release, esbuild will now attempt to terminate the Go GC in this edge case by calling clearTimeout() on these pending timeouts.

  • Apply /* @&#8203;__NO_SIDE_EFFECTS__ */ on tagged template literals (#​3511)

    Tagged template literals that reference functions annotated with a @__NO_SIDE_EFFECTS__ comment are now able to be removed via tree-shaking if the result is unused. This is a convention from Rollup. Here is an example:

    // Original code
const html = /* @&#8203;__NO_SIDE_EFFECTS__ */ (a, ...b) => ({ a, b })
html`<a>remove</a>`
x = html`<b>keep</b>`

// Old output (with --tree-shaking=true)
const html = /* @&#8203;__NO_SIDE_EFFECTS__ */ (a, ...b) => ({ a, b });
html`<a>remove</a>`;
x = html`<b>keep</b>`;

// New output (with --tree-shaking=true)
const html = /* @&#8203;__NO_SIDE_EFFECTS__ */ (a, ...b) => ({ a, b });
x = html`<b>keep</b>`;

    Note that this feature currently only works within a single file, so it's not especially useful. This feature does not yet work across separate files. I still recommend using @__PURE__ annotations instead of this feature, as they have wider tooling support. The drawback of course is that @__PURE__ annotations need to be added at each call site, not at the declaration, and for non-call expressions such as template literals you need to wrap the expression in an IIFE (immediately-invoked function expression) to create a call expression to apply the @__PURE__ annotation to.

  • Publish builds for IBM AIX PowerPC 64-bit (#​3549)

    This release publishes a binary executable to npm for IBM AIX PowerPC 64-bit, which means that in theory esbuild can now be installed in that environment with npm install esbuild. This hasn't actually been tested yet. If you have access to such a system, it would be helpful to confirm whether or not doing this actually works.

eslint/eslint (eslint)

v8.56.0

Compare Source

Features
  • 0dd9704 feat: Support custom severity when reporting unused disable directives (#​17212) (Bryan Mishkin)
  • 31a7e3f feat: fix no-restricted-properties false negatives with unknown objects (#​17818) (Arka Pratim Chaudhuri)
Bug Fixes
  • 7d5e5f6 fix: TypeError: fs.exists is not a function on read-only file system (#​17846) (Francesco Trotta)
  • 74739c8 fix: suggestion with invalid syntax in no-promise-executor-return rule (#​17812) (Bryan Mishkin)
Documentation
  • 9007719 docs: update link in ways-to-extend.md (#​17839) (Amel SELMANE)
  • 3a22236 docs: Update README (GitHub Actions Bot)
  • 54c3ca6 docs: fix migration-guide example (#​17829) (Tanuj Kanti)
  • 4391b71 docs: check config comments in rule examples (#​17815) (Francesco Trotta)
  • fd28363 docs: remove mention about ESLint stylistic rules in readme (#​17810) (Zwyx)
  • 48ed5a6 docs: Update README (GitHub Actions Bot)
Chores
eslint-community/eslint-plugin-n (eslint-plugin-n)

v16.5.0

Compare Source

Features
  • feat: Add builtins check for ES2021 to no-unsupported-features/es-builtins rule (#​153) (15a5850)
  • feat: Add syntax check for ES2021 to no-unsupported-features/es-syntax rule (#​152) (6835a10)
Docs & Chores
  • docs: Auto-generate configs list with eslint-doc-generator (#​146) (6409e34)
  • chore: Configure Renovate (0d6a0fe)
prettier/eslint-plugin-prettier (eslint-plugin-prettier)

v5.1.2

Compare Source

Patch Changes

  • #​623 8210e44 Thanks @​BPScott! - Add exports mapping to package.json, to allow import eslintPluginRecommended from 'eslint-plugin-prettier/recommended' to work as expected.

    Strictly speaking this is a breaking change as it removes the ability for people to import from "eslint-plugin-prettier/eslint-plugin-prettier.js" and "eslint-plugin-prettier/recommended.js" but the former was never recommended in the first place and the latter has only been available for a few days.

  • #​621 2b09e7f Thanks @​JounQin! - feat: support parsing markdown via eslint-mdx natively

v5.1.1

Compare Source

Patch Changes

v5.1.0

Compare Source

Minor Changes

  • #​616 3856413 Thanks @​BPScott! - Add recommended config for the flat config format.

    If you are using flat config, import the recommended config from eslint-plugin-prettier/recommended. Like the legacy format recommended config, this automatically includes the contents of eslint-config-prettier.

    // eslint.config.js
const eslintPluginPrettierRecommended = require('eslint-plugin-prettier/recommended');

module.exports = [
  // Any other config imports go at the top
  eslintPluginPrettierRecommended,
];
Patch Changes

  • #​614 5270877 Thanks @​BPScott! - Add meta block to plugin. This improves debugging and cachebusting when using the new flat config

  • #​603 a63a570 Thanks @​filiptammergard! - fix: specify eslint-config-prettier as peer dependency

    It's already added to peerDependenciesMeta as optional, which means it should also be specified in peerDependencies.

pnpm/pnpm (pnpm)

v8.12.1

Compare Source

Patch Changes

  • Don't report dependencies with optional dependencies as being added on repeat install. This was a bug in reporting #​7384.
  • Fix a bug where --fix-lockfile crashes on tarballs #​7368.
  • Do not create empty patch directory.
  • Installation should not fail if an empty node_modules directory cannot be removed #​7405.

Our Gold Sponsors

Our Silver Sponsors
bluwy/publint (publint)

v0.2.7

Compare Source

Features
  • If the library exports from both "main"/"module" and "exports" fields, but the "exports" field doesn't export the root entrypoint, warn about the inconsistency. When "exports" is defined, it takes the highest priority, so all the library's entrypoint (root and deep) needs to be specified here. (https://github.com/bluwy/publint/issues/88)
  • Suggest using the "type" field. In Node.js v20.10.0, it introduces a new --experimental-default-type flag to flip the default module system from "CJS-as-default" to "ESM-as-default". It's recommended for libraries to specify the "type" field explicitly to prevent CJS files from being incorrectly interpreted as ESM. This suggestion helps push towards a better ESM experience in the future. (https://github.com/bluwy/publint/issues/83)

Full Changelog: publint/publint@v0.2.6...v0.2.7

lukeed/sirv (sirv)

v2.0.4

Compare Source

Patches

Full Changelog: lukeed/sirv@v2.0.3...v2.0.4

sveltejs/svelte-preprocess (svelte-preprocess)

v5.1.3

Compare Source

Bug Fixes
  • sass dependency list referencing source file in win32 (#​621) (209312f)

v5.1.2

Compare Source

  • chore: mark postcss-load-config 5 as supported (3b5b1f0)
vitejs/vite (vite)

v5.0.10

Compare Source

v5.0.9

Compare Source

v5.0.8

Compare Source

vitest-dev/vitest (vitest)

v1.1.0

Compare Source

   🚀 Features
   🐞 Bug Fixes

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 force-pushed the renovate/all-minor-patch branch 10 times, most recently from 7a47ff3 to 5c57aac Compare December 24, 2023 06:35
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 5c57aac to bae6e1d Compare December 25, 2023 18:45
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from bae6e1d to e60eadd Compare December 26, 2023 02:48
@bluwy bluwy merged commit 4a8d590 into main Dec 26, 2023
5 checks passed
@bluwy bluwy deleted the renovate/all-minor-patch branch December 26, 2023 02:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@bluwy bluwy bluwy approved these changes

Assignees
No one assigned
Labels
dependencies
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@bluwy