vercel[bot]
commented
1 year ago The latest updates on your projects. Learn more about Vercel for Git ↗︎
| Name | Status | Preview | Comments | Updated (UTC) |
|---|---|---|---|---|
| programming-in-th | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Aug 6, 2023 1:37pm |
github-actions[bot]
This PR contains the following updates:
3.379.1->3.385.03.379.1->3.385.06.15.3->6.16.05.0.0->5.1.118.17.1->18.17.318.2.17->18.2.186.2.0->6.2.16.2.0->6.2.14.0.3->4.0.40.33.0->0.34.18.9.0->8.10.08.6.10->8.6.123.0.0->3.0.15.0.0->5.1.17.45.2->7.45.41.6.1->1.6.21.64.1->1.64.20.33.0->0.34.1Release Notes
aws/aws-sdk-js-v3 (@aws-sdk/client-s3)
### [`v3.385.0`](https://togithub.com/aws/aws-sdk-js-v3/blob/HEAD/clients/client-s3/CHANGELOG.md#33850-2023-08-04) **Note:** Version bump only for package [@aws-sdk/client-s3](https://togithub.com/aws-sdk/client-s3) ### [`v3.383.0`](https://togithub.com/aws/aws-sdk-js-v3/blob/HEAD/clients/client-s3/CHANGELOG.md#33830-2023-08-02) **Note:** Version bump only for package [@aws-sdk/client-s3](https://togithub.com/aws-sdk/client-s3) ### [`v3.382.0`](https://togithub.com/aws/aws-sdk-js-v3/blob/HEAD/clients/client-s3/CHANGELOG.md#33820-2023-08-01) **Note:** Version bump only for package [@aws-sdk/client-s3](https://togithub.com/aws-sdk/client-s3) #### [3.379.1](https://togithub.com/aws/aws-sdk-js-v3/compare/v3.379.0...v3.379.1) (2023-07-28) **Note:** Version bump only for package [@aws-sdk/client-s3](https://togithub.com/aws-sdk/client-s3)aws/aws-sdk-js-v3 (@aws-sdk/s3-request-presigner)
### [`v3.385.0`](https://togithub.com/aws/aws-sdk-js-v3/blob/HEAD/packages/s3-request-presigner/CHANGELOG.md#33850-2023-08-04) **Note:** Version bump only for package [@aws-sdk/s3-request-presigner](https://togithub.com/aws-sdk/s3-request-presigner) ### [`v3.383.0`](https://togithub.com/aws/aws-sdk-js-v3/blob/HEAD/packages/s3-request-presigner/CHANGELOG.md#33830-2023-08-02) **Note:** Version bump only for package [@aws-sdk/s3-request-presigner](https://togithub.com/aws-sdk/s3-request-presigner) ### [`v3.382.0`](https://togithub.com/aws/aws-sdk-js-v3/blob/HEAD/packages/s3-request-presigner/CHANGELOG.md#33820-2023-08-01) **Note:** Version bump only for package [@aws-sdk/s3-request-presigner](https://togithub.com/aws-sdk/s3-request-presigner) #### [3.379.1](https://togithub.com/aws/aws-sdk-js-v3/compare/v3.379.0...v3.379.1) (2023-07-28) **Note:** Version bump only for package [@aws-sdk/s3-request-presigner](https://togithub.com/aws-sdk/s3-request-presigner)codemirror/view (@codemirror/view)
### [`v6.16.0`](https://togithub.com/codemirror/view/blob/HEAD/CHANGELOG.md#6160-2023-07-31) [Compare Source](https://togithub.com/codemirror/view/compare/6.15.3...6.16.0) ##### Bug fixes Fix an issue that made the gutter not stick in place when the editor was in a right-to-left context. ##### New features The new `EditorView.coordsForChar` method returns the client rectangle for a given character in the editor.prisma/prisma (@prisma/client)
### [`v5.1.1`](https://togithub.com/prisma/prisma/releases/tag/5.1.1) [Compare Source](https://togithub.com/prisma/prisma/compare/5.1.0...5.1.1) Today, we are issuing the `5.1.1` patch release. ##### Fixes in Prisma Client - [Browser bundle: Unhandled Runtime Error when upgrading to 5.1.0 from 5.0.0 ](https://togithub.com/prisma/prisma/issues/20480) - [Prisma Client: `disconnect: true` does not appear to delete the foreign key in the returned data](https://togithub.com/prisma/prisma/issues/20491) - [Prisma Client errors with "TypeError: Cannot create proxy with a non-object as target or handler" when using result client extension with no `needs` and `count` method](https://togithub.com/prisma/prisma/issues/20499) ### [`v5.1.0`](https://togithub.com/prisma/prisma/releases/tag/5.1.0) [Compare Source](https://togithub.com/prisma/prisma/compare/5.0.0...5.1.0) Today, we are excited to share the `5.1.0` stable release 🎉 🌟 **Help us spread the word about Prisma by starring the repo ☝️ or [tweeting](https://twitter.com/intent/tweet?text=Check%20out%20the%20latest%20@prisma%20release%20v5.1.0%20%F0%9F%9A%80%0D%0A%0D%0Ahttps://github.com/prisma/prisma/releases/tag/5.1.0) about the release.** ##### Highlights After two big releases where we released Client extensions for production usage ([`4.16.0`](https://togithub.com/prisma/prisma/releases/tag/4.16.0)) and made Prisma faster by default ([`5.0.0`](https://togithub.com/prisma/prisma/releases/tag/5.0.0)), we have focused on some smaller issues to make the experience with these new features even better. ##### Community contributions Our community has been on the roll! We appreciate everyone who helps us by opening a GitHub issue or proposing a fix via Pull Requests. In this release, we're excited to highlight multiple community contributions: - Fix IPv6 not working for relational databases: [https://github.com/prisma/prisma-engines/pull/4051](https://togithub.com/prisma/prisma-engines/pull/4051) by [@alula](https://togithub.com/alula) - Middlewares: Add to `PrismaAction` type, missing `findUniqueOrThrow` and `findFirstOrThrow` [https://github.com/prisma/prisma/pull/17471](https://togithub.com/prisma/prisma/pull/17471) by [@mejiaej](https://togithub.com/mejiaej) and missing `groupBy` [https://github.com/prisma/prisma/pull/19985](https://togithub.com/prisma/prisma/pull/19985) by [@iurylippo](https://togithub.com/iurylippo) - Better error message in currently non-supported runtimes like Browser or Vercel Edge Runtime [https://github.com/prisma/prisma/pull/20163](https://togithub.com/prisma/prisma/pull/20163) by [@andyjy](https://togithub.com/andyjy) - Remove error messages for valid NixOS setups [https://github.com/prisma/prisma/pull/20138](https://togithub.com/prisma/prisma/pull/20138) by [@Gerschtli](https://togithub.com/Gerschtli) ##### Better performance: Fewer SQL queries on PostgreSQL & CockroachDB In our continued and ongoing work to make Prisma faster, we identified some Prisma Client queries that led to multiple SQL statements being executed — although in specific databases, that was not necessary. Hence we optimized our internal SQL generation for PostgreSQL and CockroachDB to generate more efficient SQL queries: ##### Simple `create` query In a simple `create` query, `RETURNING` makes the second query and the transaction statements obsolete: ##### Prisma Client query ```ts prisma.user.create({ data: { name: "Original name" } }) ``` ##### Before v5.1.0 ```sql BEGIN INSERT INTO "User" ("name") VALUES ($1) RETURNING "User"."id" SELECT "User"."id", "User"."name" FROM "User" WHERE "User"."id" = $1; COMMIT ``` ##### 5.1.0 and later ```sql -- Sends 1 statement (instead of 2) and omits the transaction INSERT INTO "User" ("name") VALUES ($1) RETURNING "User"."id", "User"."name" ``` ##### Simple `update` query For a simple `update` query, `RETURNING` makes both additional queries and the transaction statements obsolete: ##### Prisma Client query ```ts prisma.user.update({ where: { id: 1 }, data: { name: "updated" } }) ``` ##### Before v5.1.0 ```sql BEGIN SELECT id FROM "User" WHERE "User".id = 1; UPDATE "User" SET name = 'updated' WHERE "User".id = 1; SELECT id, name FROM "User" WHERE "User".id = 1; COMMIT ``` ##### 5.1.0 and later ```sql -- Sends 1 statement (instead of 3) and omits the transaction UPDATE "User" SET name = 'updated' WHERE "User".id = 1 RETURNING "User".id, "User".name; ``` ##### Simple `update` query, return with relation value One `SELECT` query could easily be dropped in a simple `update` query that should return a relation value as well: ##### Prisma Client query ```ts prisma.user.update({ where: { id: 1 }, data: { name: "updated" }, includes: { posts: true } }) ``` ##### Before v5.1.0 ```sql BEGIN SELECT id FROM "User" WHERE "User".id = 1; UPDATE "User" SET name = 'updated' WHERE "User".id = 1; SELECT id, name FROM "User" WHERE "User".id = 1; SELECT id, title FROM "Post" WHERE "Post"."userId" = 1; COMMIT ``` ##### 5.1.0 and later ```sql -- Sends 3 statements (instead of 4) BEGIN UPDATE "User" SET name = 'updated' WHERE "User".id = 1 RETURNING "User".id; SELECT id, name FROM "User" WHERE "User".id = 1; SELECT id, title FROM "Post" WHERE "Post"."userId" = 1; COMMIT ``` ##### Empty `update` query An empty `update` query can be optimized to skip the transaction and the second identical query by creating specific handling for this edge case in our code: ##### Prisma Client query ```ts prisma.user.update({ where: { id: 1 }, data: {}, }) ``` ##### Before v5.1.0 ```sql BEGIN SELECT id, name FROM "User" WHERE "User".id = 1; SELECT id, name FROM "User" WHERE "User".id = 1; COMMIT ``` ##### 5.1.0 and later ```sql -- Sends 1 statement (instead of 2) and omits the transaction SELECT id, name FROM "User" WHERE "User".id = 1; ``` ##### Simple + relation `update` query (but do not return relation value) An update of both the model and its relation, we could drop 2 `SELECT` queries that we did before without ever using their return values: ##### Prisma Client query ```ts prisma.user.update({ where: { id: 1 }, data: { name: "updated", posts: { update: { where: { id: 1 }, data: { title: "updated" } } } } }) ``` ##### Before v5.1.0 ```sql BEGIN SELECT id, name FROM "User" WHERE "User".id = 1; UPDATE "User" SET name = 'updated' WHERE "User".id = 1 RETURNING "User".id; SELECT "id", "postId" FROM "Post" WHERE "Post".id = 1; UPDATE "Post" SET title = 'updated' WHERE "Post"."userId" = 1 AND "Post".id = 1; SELECT id, name FROM "User" WHERE "User".id = 1; COMMIT ``` ##### 5.1.0 and later ```sql -- Sends 3 statements (instead of 5) BEGIN UPDATE "User" SET name = 'updated' WHERE "User".id = 1 RETURNING "User".id, "User".name; SELECT "id", "postId" FROM "Post" WHERE "Post".id = 1; UPDATE "Post" SET title = 'updated' WHERE "Post"."userId" = 1 AND "Post".id = 1; COMMIT ``` In the next releases, we will continue optimizing Prisma Client queries to only run the minimal amount of SQL queries necessary. If you notice any Prisma Client queries that are affected right now, please check the issues under [our `performance/queries` label](https://togithub.com/prisma/prisma/labels/topic%3A%20performance%2Fqueries). If you didn’t find one for what you’re seeing, please [create a new issue](https://togithub.com/prisma/prisma/issues). This will be super useful for us to understand all (edge) cases. Thank you! ##### Prisma Studio now supports `directUrl` Our CLI command `prisma studio` that opens Prisma Studio now also can use the [`directUrl`](https://www.prisma.io/docs/guides/performance-and-optimization/connection-management#external-connection-poolers) property of the `datasource` block so you can make it talk to a different database than defined in `url`. This makes it easier to use Studio alongside the Prisma Data Proxy and [Accelerate](https://www.prisma.io/accelerate). ##### Prisma Client: No more type clashes We fixed (almost) all cases where using a specific term as a model name in your Prisma Schema would lead to a *type clash* due to Prisma’s generated typings. As a result of a type clash, it was not possible to use that model in your code (this was e.g. the case if you named a model `Model` or `ModelUpdate`). We also deprecated the `typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)
### [`v6.2.1`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#621-2023-07-31) [Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v6.2.0...v6.2.1) ##### Bug Fixes - **eslint-plugin:** \[no-inferrable-types] apply also for parameter properties ([#7288](https://togithub.com/typescript-eslint/typescript-eslint/issues/7288)) ([67f93b1](https://togithub.com/typescript-eslint/typescript-eslint/commit/67f93b19f2e481a4e441635d72e81de9d5d7ad44)) - **scope-manager:** correct decorators(.length) check in ClassVisitor for methods ([#7334](https://togithub.com/typescript-eslint/typescript-eslint/issues/7334)) ([abbb6c2](https://togithub.com/typescript-eslint/typescript-eslint/commit/abbb6c2c6d2bc1f8d4defd2060dbc473735b2cc7)) You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.typescript-eslint/typescript-eslint (@typescript-eslint/parser)
### [`v6.2.1`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/parser/CHANGELOG.md#621-2023-07-31) [Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v6.2.0...v6.2.1) **Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser) You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.vitejs/vite-plugin-react (@vitejs/plugin-react)
### [`v4.0.4`](https://togithub.com/vitejs/vite-plugin-react/blob/HEAD/packages/plugin-react/CHANGELOG.md#404-2023-07-31) [Compare Source](https://togithub.com/vitejs/vite-plugin-react/compare/v4.0.3...v4.0.4) - Fix [#198](https://togithub.com/vitejs/vite-plugin-react/discussions/198): Enable Babel if presets list is not emptyvitest-dev/vitest (@vitest/coverage-v8)
### [`v0.34.1`](https://togithub.com/vitest-dev/vitest/releases/tag/v0.34.1) [Compare Source](https://togithub.com/vitest-dev/vitest/compare/v0.34.0...v0.34.1) ##### 🐞 Bug Fixes - Pass `--experimental-vm-worker-memory-limit` to `tinypool` - by [@AriPerkkio](https://togithub.com/AriPerkkio) in [https://github.com/vitest-dev/vitest/issues/3856](https://togithub.com/vitest-dev/vitest/issues/3856) [(3c67a)](https://togithub.com/vitest-dev/vitest/commit/3c67a4cb) ##### [View changes on GitHub](https://togithub.com/vitest-dev/vitest/compare/v0.34.0...v0.34.1) ### [`v0.34.0`](https://togithub.com/vitest-dev/vitest/releases/tag/v0.34.0) [Compare Source](https://togithub.com/vitest-dev/vitest/compare/v0.33.0...v0.34.0) ##### 🚨 Breaking Changes - Transform mode affects only test files, not regular files - by [@sheremet-va](https://togithub.com/sheremet-va) in [https://github.com/vitest-dev/vitest/issues/3491](https://togithub.com/vitest-dev/vitest/issues/3491) [(9608b)](https://togithub.com/vitest-dev/vitest/commit/9608bf72) - `transformMode` is now moved to `server.transformMode`. This option is highly discouraged to use. If you need to change the transform mode, use the new option `testTransformMode` instead to control the mode based on the running test, not the current file path. By default, tests with `jsdom` or `happy-dom` use `web` transform mode, and tests using `node` or `edge` environment use `ssr` mode. If you have a custom environment, it should provide `transformMode` property. - Disable `coverage.reportOnFailure` by default - by [@AriPerkkio](https://togithub.com/AriPerkkio) in [https://github.com/vitest-dev/vitest/issues/3615](https://togithub.com/vitest-dev/vitest/issues/3615) [(0c6f6)](https://togithub.com/vitest-dev/vitest/commit/0c6f624f) - Remove `@vitest/coverage-c8` package - by [@AriPerkkio](https://togithub.com/AriPerkkio) in [https://github.com/vitest-dev/vitest/issues/3614](https://togithub.com/vitest-dev/vitest/issues/3614) [(a90d6)](https://togithub.com/vitest-dev/vitest/commit/a90d64fe) - `@vitest/coverage-c8` is no longer supported. Please, use `@vitest/coverage-v8` instead. - Support running tests using VM context - by [@sheremet-va](https://togithub.com/sheremet-va) and [@dammy001](https://togithub.com/dammy001) in [https://github.com/vitest-dev/vitest/issues/3203](https://togithub.com/vitest-dev/vitest/issues/3203) [(b0929)](https://togithub.com/vitest-dev/vitest/commit/b0929852) - To address speed issues in some applications, Vitest now provides `experimentalVmThreads` pool to run your tests using VM Sandboxes environment. Make sure you understand [all pitfalls](https://vitest.dev/config/#experimentalvmthreads) of this pool before opening an issue. - Introduce `server` option - by [@fenghan34](https://togithub.com/fenghan34) and [@sheremet-va](https://togithub.com/sheremet-va) in [https://github.com/vitest-dev/vitest/issues/3725](https://togithub.com/vitest-dev/vitest/issues/3725) [(dc4fa)](https://togithub.com/vitest-dev/vitest/commit/dc4faf64) - Most of `deps.` options are now moved to `server.deps` with a deprecation warning. Please, consider using `deps.optimizer` instead of `deps.inline`/`deps.external`. Ideally, we would like to move away from using `server.deps.inline` altogether. - **vite-node**: Make CLI arguments parsing behavior consistent with node/tsx/ts-node - by [@rxliuli](https://togithub.com/rxliuli) in [https://github.com/vitest-dev/vitest/issues/3574](https://togithub.com/vitest-dev/vitest/issues/3574) [(1cd4e)](https://togithub.com/vitest-dev/vitest/commit/1cd4eb0f) - You now have to provide CLI arguments before the entry point. For example, instead of `vite-node index.ts --watch`, you now have to do `vite-node --watch index.ts`. - Add preact example, remove optimizer experimental status, enable by default - by [@sheremet-va](https://togithub.com/sheremet-va) and [@eryue0220](https://togithub.com/eryue0220) in [https://github.com/vitest-dev/vitest/issues/3854](https://togithub.com/vitest-dev/vitest/issues/3854) [(4b946)](https://togithub.com/vitest-dev/vitest/commit/4b946ca9) - `deps.optimizer` is now enabled by default. This means that Vitest will bundle specified dependencies before running your tests. This field inherits options from `optimizeDeps` and `ssr.optimizeDeps` which are populated by other plugins (like, Svelte). ##### 🚀 Features - Support `describe.sequential` - by [@fenghan34](https://togithub.com/fenghan34) and [@dammy001](https://togithub.com/dammy001) in [https://github.com/vitest-dev/vitest/issues/3771](https://togithub.com/vitest-dev/vitest/issues/3771) [(86934)](https://togithub.com/vitest-dev/vitest/commit/8693449b) - Support config junit reporter className with env - by [@InfiniteXyy](https://togithub.com/InfiniteXyy) in [https://github.com/vitest-dev/vitest/issues/3808](https://togithub.com/vitest-dev/vitest/issues/3808) [(e8bc4)](https://togithub.com/vitest-dev/vitest/commit/e8bc46b6) - Running vitest with `--related --watch` reruns non-affected tests if they were changed during a run - by [@sheremet-va](https://togithub.com/sheremet-va) in [https://github.com/vitest-dev/vitest/issues/3844](https://togithub.com/vitest-dev/vitest/issues/3844) [(c9aea)](https://togithub.com/vitest-dev/vitest/commit/c9aeac4c) ##### 🐞 Bug Fixes - Isolate workers between envs and workspaces - by [@AriPerkkio](https://togithub.com/AriPerkkio) [(ed4e0)](https://togithub.com/vitest-dev/vitest/commit/ed4e0424) - Modify condition - by [@btea](https://togithub.com/btea) [(a78e6)](https://togithub.com/vitest-dev/vitest/commit/a78e6bd0) - Module Graph view is blocking the Console view - by [@g4rry420](https://togithub.com/g4rry420) [(3b5f9)](https://togithub.com/vitest-dev/vitest/commit/3b5f96bc) - Port the latest `defineConfig` type from vite - by [@sodatea](https://togithub.com/sodatea) in [https://github.com/vitest-dev/vitest/issues/3804](https://togithub.com/vitest-dev/vitest/issues/3804) [(9c8e3)](https://togithub.com/vitest-dev/vitest/commit/9c8e3083) - Don't overwrite Node.js URL global - by [@sheremet-va](https://togithub.com/sheremet-va) in [https://github.com/vitest-dev/vitest/issues/3828](https://togithub.com/vitest-dev/vitest/issues/3828) [(cdab4)](https://togithub.com/vitest-dev/vitest/commit/cdab4651) - ForceRerunTriggers correctly triggers a rerun - by [@sheremet-va](https://togithub.com/sheremet-va) in [https://github.com/vitest-dev/vitest/issues/3829](https://togithub.com/vitest-dev/vitest/issues/3829) [(17988)](https://togithub.com/vitest-dev/vitest/commit/17988e51) - **browser**: - Don't inline magic-string and estree-walker - by [@sheremet-va](https://togithub.com/sheremet-va) in [https://github.com/vitest-dev/vitest/issues/3726](https://togithub.com/vitest-dev/vitest/issues/3726) [(ee937)](https://togithub.com/vitest-dev/vitest/commit/ee93762a) - Multi-suite coverage - by [@elby22](https://togithub.com/elby22) in [https://github.com/vitest-dev/vitest/issues/3806](https://togithub.com/vitest-dev/vitest/issues/3806) [(5de9a)](https://togithub.com/vitest-dev/vitest/commit/5de9af26) - **core**: - DataView comparison does not work in `toStrictEqual` - by [@Dunqing](https://togithub.com/Dunqing) [(52aef)](https://togithub.com/vitest-dev/vitest/commit/52aef92e) - **coverage**: - V8 provider to pick source maps without url query params - by [@AriPerkkio](https://togithub.com/AriPerkkio) in [https://github.com/vitest-dev/vitest/issues/3784](https://togithub.com/vitest-dev/vitest/issues/3784) [(280e6)](https://togithub.com/vitest-dev/vitest/commit/280e6745) - Update `istanbul-lib-instrument` to v6 to fix vulnerable dependency - by [@AriPerkkio](https://togithub.com/AriPerkkio) in [https://github.com/vitest-dev/vitest/issues/3814](https://togithub.com/vitest-dev/vitest/issues/3814) [(f3bd9)](https://togithub.com/vitest-dev/vitest/commit/f3bd9102) - Exclude vite virtual modules by default - by [@AriPerkkio](https://togithub.com/AriPerkkio) in [https://github.com/vitest-dev/vitest/issues/3794](https://togithub.com/vitest-dev/vitest/issues/3794) [(3c851)](https://togithub.com/vitest-dev/vitest/commit/3c851872) - **node**: - Guard error info - by [@btea](https://togithub.com/btea) [(88b39)](https://togithub.com/vitest-dev/vitest/commit/88b39758) - **vite-node**: - Always treat node_modules as modulesDirectory - by [@sheremet-va](https://togithub.com/sheremet-va) in [https://github.com/vitest-dev/vitest/issues/3830](https://togithub.com/vitest-dev/vitest/issues/3830) [(51ab8)](https://togithub.com/vitest-dev/vitest/commit/51ab8d6c) - Normalize drive letter to keep the same reference to a module - by [@sheremet-va](https://togithub.com/sheremet-va) in [https://github.com/vitest-dev/vitest/issues/3836](https://togithub.com/vitest-dev/vitest/issues/3836) [(45521)](https://togithub.com/vitest-dev/vitest/commit/45521859) - Correctly resolve hmr filepath - by [@sheremet-va](https://togithub.com/sheremet-va) in [https://github.com/vitest-dev/vitest/issues/3834](https://togithub.com/vitest-dev/vitest/issues/3834) [(711a6)](https://togithub.com/vitest-dev/vitest/commit/711a6249) - **watch**: - Clear screen on all terminals - by [@AriPerkkio](https://togithub.com/AriPerkkio) in [https://github.com/vitest-dev/vitest/issues/3661](https://togithub.com/vitest-dev/vitest/issues/3661) [(8bd26)](https://togithub.com/vitest-dev/vitest/commit/8bd26b01) ##### 🏎 Performance - Deprecate deps.registerNodeLoader - by [@sheremet-va](https://togithub.com/sheremet-va) [(7f45b)](https://togithub.com/vitest-dev/vitest/commit/7f45bf2d) - This option was introduced to support aliasing inside external packages. Please, use `deps.optimizer.web` instead. If you test Node.js applications, consider adding external packages to `server.deps.inline`. ##### [View changes on GitHub](https://togithub.com/vitest-dev/vitest/compare/v0.33.0...v0.34.0)prettier/eslint-config-prettier (eslint-config-prettier)
### [`v8.10.0`](https://togithub.com/prettier/eslint-config-prettier/blob/HEAD/CHANGELOG.md#Version-8100-2023-08-03) [Compare Source](https://togithub.com/prettier/eslint-config-prettier/compare/v8.9.0...v8.10.0) - Added: \[max-statements-per-line]. Thanks to [@Zamiell](https://togithub.com/Zamiell)!pnpm/pnpm (pnpm)
### [`v8.6.12`](https://togithub.com/pnpm/pnpm/releases/tag/v8.6.12) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v8.6.11...v8.6.12) #### Patch Changes - Make the error message friendlier when a user attempts to run a command that does not exist [#6887](https://togithub.com/pnpm/pnpm/pull/6887). - `pnpm patch` should work correctly when `shared-workspace-file` is set to `false` [#6885](https://togithub.com/pnpm/pnpm/issues/6885). - `pnpm env use` should retry deleting the previous Node.js executable [#6587](https://togithub.com/pnpm/pnpm/issues/6587). - `pnpm dlx` should not print an error stack when the underlying script execution fails [#6698](https://togithub.com/pnpm/pnpm/issues/6698). - When showing the download progress of large tarball files, always display the same number of digits after the decimal point [#6901](https://togithub.com/pnpm/pnpm/issues/6901). - Report download progress less frequently to improve performance [#6906](https://togithub.com/pnpm/pnpm/pull/6906). - `pnpm install --frozen-lockfile --lockfile-only` should fail if the lockfile is not up to date with the `package.json` files [#6913](https://togithub.com/pnpm/pnpm/issues/6913). #### Our Gold Sponsorsprettier/prettier (prettier)
### [`v3.0.1`](https://togithub.com/prettier/prettier/blob/HEAD/CHANGELOG.md#301) [Compare Source](https://togithub.com/prettier/prettier/compare/3.0.0...3.0.1) [diff](https://togithub.com/prettier/prettier/compare/3.0.0...3.0.1) ##### Fix cursor positioning for a special case ([#14812](https://togithub.com/prettier/prettier/pull/14812) by [@fisker](https://togithub.com/fisker)) ```js // <|> is the cursor position /* Input */ // All messages are represented in JSON. // So, the prettier.py controls a subprocess which spawns "node {this_file}". import {<|> } from "fs" /* Prettier 3.0.0 */ // All messages are represented in JSON. // So, the prettier.py <|>controls a subprocess which spawns "node {this_file}". import {} from "fs" /* Prettier 3.0.1 */ // All messages are represented in JSON. // So, the prettier.py controls a subprocess which spawns "node {this_file}". import {<|>} from "fs" ``` ##### Fix plugins/estree.d.ts to make it a module ([#15018](https://togithub.com/prettier/prettier/pull/15018) by [@kingyue737](https://togithub.com/kingyue737)) Add `export {}` in `plugins/estree.d.ts` to fix the "File is not a module" error ##### Add parenthesis around leading multiline comment in return statement ([#15037](https://togithub.com/prettier/prettier/pull/15037) by [@auvred](https://togithub.com/auvred)) ```jsx // Input function fn() { return ( /** * @type {...} */ expresssion ) } // Prettier 3.0.0 function fn() { return /** * @type {...} */ expresssioConfiguration
📅 Schedule: Branch creation - "before 4am on sunday" (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.