marimo-team / vscode-marimo

marimo vscode extenion
https://marketplace.visualstudio.com/items?itemName=marimo-team.vscode-marimo
MIT License
17 stars 3 forks source link

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

Closed renovate[bot] closed 6 months ago

renovate[bot] commented 8 months ago

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@types/node (source) 20.8.9 -> 20.10.4 age adoption passing confidence
@vscode/test-electron ^2.3.6 -> ^2.3.8 age adoption passing confidence
pnpm (source) 8.10.0 -> 8.12.1 age adoption passing confidence
prettier (source) ^3.0.3 -> ^3.1.1 age adoption passing confidence

Release Notes

Microsoft/vscode-test (@​vscode/test-electron) ### [`v2.3.7`](https://togithub.com/Microsoft/vscode-test/blob/HEAD/CHANGELOG.md#237--2022-11-23) [Compare Source](https://togithub.com/Microsoft/vscode-test/compare/v2.3.6...v2.3.7) - Remove detection for unsupported win32 builds - Add length and hash validation for downloaded builds
pnpm/pnpm (pnpm) ### [`v8.12.1`](https://togithub.com/pnpm/pnpm/releases/tag/v8.12.1) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v8.12.0...v8.12.1) #### Patch Changes - Don't report dependencies with optional dependencies as being added on repeat install. This was a bug in reporting [#​7384](https://togithub.com/pnpm/pnpm/issues/7384). - Fix a bug where `--fix-lockfile` crashes on tarballs [#​7368](https://togithub.com/pnpm/pnpm/issues/7368). - Do not create empty patch directory. - Installation should not fail if an empty `node_modules` directory cannot be removed [#​7405](https://togithub.com/pnpm/pnpm/issues/7405). #### Our Gold Sponsors
#### Our Silver Sponsors
### [`v8.12.0`](https://togithub.com/pnpm/pnpm/releases/tag/v8.12.0) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v8.11.0...v8.12.0) #### Minor Changes - Add support for basic authorization header [#​7371](https://togithub.com/pnpm/pnpm/issues/7371). #### Patch Changes - Fix a bug where pnpm incorrectly passes a flag to a run handler as a fallback command [#​7244](https://togithub.com/pnpm/pnpm/issues/7244). - When `dedupe-direct-deps` is set to `true`, commands of dependencies should be deduplicated [#​7359](https://togithub.com/pnpm/pnpm/pull/7359). #### Our Gold Sponsors
#### Our Silver Sponsors
### [`v8.11.0`](https://togithub.com/pnpm/pnpm/releases/tag/v8.11.0) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v8.10.5...v8.11.0) #### Minor Changes - (IMPORTANT) When the package tarballs aren't hosted on the same domain on which the registry (the server with the package metadata) is, the dependency keys in the lockfile should only contain `/@​/@​`. This change is a fix to avoid the same package from being added to `node_modules/.pnpm` multiple times. The change to the lockfile is backward compatible, so previous versions of pnpm will work with the fixed lockfile. We recommend that all team members update pnpm in order to avoid repeated changes in the lockfile. Related PR: [#​7318](https://togithub.com/pnpm/pnpm/pull/7318). #### Patch Changes - `pnpm add a-module-already-in-dev-deps` will show a message to notice the user that the package was not moved to "dependencies" [#​926](https://togithub.com/pnpm/pnpm/issues/926). - The modules directory should not be removed if the registry configuration has changed. - Fix missing auth tokens in registries with paths specified (e.g. //npm.pkg.github.com/pnpm). [#​5970](https://togithub.com/pnpm/pnpm/issues/5970) [#​2933](https://togithub.com/pnpm/pnpm/issues/2933) #### Our Gold Sponsors
#### Our Silver Sponsors
### [`v8.10.5`](https://togithub.com/pnpm/pnpm/releases/tag/v8.10.5) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v8.10.4...v8.10.5) #### Patch Changes - Don't fail on an empty `pnpm-workspace.yaml` file [#​7307](https://togithub.com/pnpm/pnpm/issues/7307). #### Our Gold Sponsors
#### Our Silver Sponsors
### [`v8.10.4`](https://togithub.com/pnpm/pnpm/releases/tag/v8.10.4) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v8.10.3...v8.10.4) #### Patch Changes - Fixed out-of-memory exception that was happening on dependencies with many peer dependencies, when `node-linker` was set to `hoisted` [#​6227](https://togithub.com/pnpm/pnpm/issues/6227). #### Our Gold Sponsors
#### Our Silver Sponsors
### [`v8.10.3`](https://togithub.com/pnpm/pnpm/releases/tag/v8.10.3) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v8.10.2...v8.10.3) #### Patch Changes - (Important) Increased the default amount of allowed concurrent network request on systems that have more than 16 CPUs [#​7285](https://togithub.com/pnpm/pnpm/pull/7285). - `pnpm patch` should reuse existing patch when `shared-workspace-file=false` [#​7252](https://togithub.com/pnpm/pnpm/pull/7252). - Don't retry fetching missing packages, since the retries will never work [#​7276](https://togithub.com/pnpm/pnpm/pull/7276). - When using `pnpm store prune --force` alien directories are removed from the store [#​7272](https://togithub.com/pnpm/pnpm/pull/7272). - Downgraded `npm-packlist` because the newer version significantly slows down the installation of local directory dependencies, making it unbearably slow. `npm-packlist` was upgraded in [this PR](https://togithub.com/pnpm/pnpm/pull/7250) to fix [#​6997](https://togithub.com/pnpm/pnpm/issues/6997). We added our own file deduplication to fix the issue of duplicate file entries. - Fixed a performance regression on running installation on a project with an up to date lockfile [#​7297](https://togithub.com/pnpm/pnpm/issues/7297). - Throw an error on invalid `pnpm-workspace.yaml` file [#​7273](https://togithub.com/pnpm/pnpm/issues/7273). #### Our Gold Sponsors
#### Our Silver Sponsors
### [`v8.10.2`](https://togithub.com/pnpm/pnpm/releases/tag/v8.10.2) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v8.10.1...v8.10.2) #### Patch Changes - Fixed a regression that was shipped with pnpm v8.10.0. Dependencies that were already built should not be rebuilt on repeat install. This issue was introduced via the changes related to [supportedArchitectures](https://togithub.com/pnpm/pnpm/pull/7214). Related issue [#​7268](https://togithub.com/pnpm/pnpm/issues/7268). #### Our Gold Sponsors
#### Our Silver Sponsors
### [`v8.10.1`](https://togithub.com/pnpm/pnpm/releases/tag/v8.10.1) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v8.10.0...v8.10.1) #### Patch Changes - (Important) Tarball resolutions in `pnpm-lock.yaml` will no longer contain a `registry` field. This field has been unused for a long time. This change should not cause any issues besides backward compatible modifications to the lockfile [#​7262](https://togithub.com/pnpm/pnpm/pull/7262). - Fix issue when trying to use `pnpm dlx` in the root of a Windows Drive [#​7263](https://togithub.com/pnpm/pnpm/issues/7263). - Optional dependencies that do not have to be built will be reflinked (or hardlinked) to the store instead of copied [#​7046](https://togithub.com/pnpm/pnpm/issues/7046). - If a package's tarball cannot be fetched, print the dependency chain that leads to the failed package [#​7265](https://togithub.com/pnpm/pnpm/pull/7265). - After upgrading one of our dependencies, we started to sometimes have an error on publish. We have forked `@npmcli/arborist` to patch it with a fix [#​7269](https://togithub.com/pnpm/pnpm/pull/7269). #### Our Gold Sponsors
#### Our Silver Sponsors
prettier/prettier (prettier) ### [`v3.1.1`](https://togithub.com/prettier/prettier/blob/HEAD/CHANGELOG.md#311) [Compare Source](https://togithub.com/prettier/prettier/compare/3.1.0...3.1.1) [diff](https://togithub.com/prettier/prettier/compare/3.1.0...3.1.1) ##### Fix config file search ([#​15363](https://togithub.com/prettier/prettier/pull/15363) by [@​fisker](https://togithub.com/fisker)) Previously, we start search for config files from the filePath as a directory, if it happened to be a directory and contains config file, it will be used by mistake. ```text ├─ .prettierrc └─ test.js (A directory) └─ .prettierrc ``` ```js // Prettier 3.1.0 await prettier.resolveConfigFile(new URL("./test.js", import.meta.url)); // /test.js/.prettierrc // Prettier 3.1.1 await prettier.resolveConfigFile(new URL("./test.js", import.meta.url)); // /.prettierrc ``` ##### Skip explicitly passed symbolic links with `--no-error-on-unmatched-pattern` ([#​15533](https://togithub.com/prettier/prettier/pull/15533) by [@​sanmai-NL](https://togithub.com/sanmai-NL)) Since Prettier v3, we stopped following symbolic links, however in some use cases, the symbolic link patterns can't be filtered out, and there is no way to prevent Prettier from throwing errors. In Prettier 3.1.1, you can use `--no-error-on-unmatched-pattern` to simply skip symbolic links. ##### Consistently use tabs in ternaries when `useTabs` is `true` ([#​15662](https://togithub.com/prettier/prettier/pull/15662) by [@​auvred](https://togithub.com/auvred)) ```jsx // Input aaaaaaaaaaaaaaa ? bbbbbbbbbbbbbbbbbb : ccccccccccccccc ? ddddddddddddddd : eeeeeeeeeeeeeee ? fffffffffffffff : gggggggggggggggg; // Prettier 3.1.0 aaaaaaaaaaaaaaa ? bbbbbbbbbbbbbbbbbb : ccccccccccccccc ? ddddddddddddddd : eeeeeeeeeeeeeee ? fffffffffffffff : gggggggggggggggg; // Prettier 3.1.1 aaaaaaaaaaaaaaa ? bbbbbbbbbbbbbbbbbb : ccccccccccccccc ? ddddddddddddddd : eeeeeeeeeeeeeee ? fffffffffffffff : gggggggggggggggg; ``` ##### Improve config file search ([#​15663](https://togithub.com/prettier/prettier/pull/15663) by [@​fisker](https://togithub.com/fisker)) The Prettier config file search performance has been improved by more effective cache strategy. ##### Fix unstable and ugly formatting for comments in destructuring patterns ([#​15708](https://togithub.com/prettier/prettier/pull/15708) by [@​sosukesuzuki](https://togithub.com/sosukesuzuki)) ```tsx // Input const { foo, // bar // baz }: Foo = expr; // Prettier 3.1.0 const { foo1, } // bar // baz : Foo = expr; // Prettier 3.1.0 second output const { foo1, // bar } // baz : Foo = expr; // Prettier 3.1.1 const { foo1, // bar // baz }: Foo = expr; ``` ##### Support "Import Attributes" ([#​15718](https://togithub.com/prettier/prettier/pull/15718) by [@​fisker](https://togithub.com/fisker)) [TypeScript 5.3](https://devblogs.microsoft.com/typescript/announcing-typescript-5-3/#import-attributes) supports the latest updates to the [import attributes](https://togithub.com/tc39/proposal-import-attributes) proposal. ```tsx import something from "./something.json" with { type: "json" }; ``` ##### Fix false claim in docs that cursorOffset is incompatible with rangeStart/rangeEnd ([#​15750](https://togithub.com/prettier/prettier/pull/15750) by [@​ExplodingCabbage](https://togithub.com/ExplodingCabbage)) The cursorOffset option has in fact been compatible with rangeStart/rangeEnd for over 5 years, thanks to work by [@​ds300](https://togithub.com/ds300). However, Prettier's documentation (including the CLI `--help` text) continued to claim otherwise, falsely. The documentation is now fixed. ##### Keep curly braces and `from` keyword in empty `import` statements ([#​15756](https://togithub.com/prettier/prettier/pull/15756) by [@​fisker](https://togithub.com/fisker)) ```js // Input import { } from 'foo'; import { /* comment */ } from 'bar'; // Prettier 3.1.0 import {} from "foo"; import /* comment */ "bar"; // Prettier 3.1.1 import {} from "foo"; import {} from /* comment */ "bar"; ``` ##### Keep empty import attributes and assertions ([#​15757](https://togithub.com/prettier/prettier/pull/15757) by [@​fisker](https://togithub.com/fisker)) ```js // Input import foo from "foo" with {}; import bar from "bar" assert {}; // Prettier 3.1.0 import foo from "foo"; import bar from "bar"; // Prettier 3.1.1 import foo from "foo" with {}; import bar from "bar" assert {}; ``` ### [`v3.1.0`](https://togithub.com/prettier/prettier/blob/HEAD/CHANGELOG.md#310) [Compare Source](https://togithub.com/prettier/prettier/compare/3.0.3...3.1.0) [diff](https://togithub.com/prettier/prettier/compare/3.0.3...3.1.0) 🔗 [Release Notes](https://prettier.io/blog/2023/11/13/3.1.0.html)

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.



This PR has been generated by Mend Renovate. View repository job log here.