fix(deps): update dependencies (non-major)

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@aws-sdk/client-s3 (source)	3.379.1 -> 3.385.0
@aws-sdk/s3-request-presigner (source)	3.379.1 -> 3.385.0
@codemirror/view	6.15.3 -> 6.16.0
@prisma/client (source)	5.0.0 -> 5.1.1
@types/node (source)	18.17.1 -> 18.17.3
@types/react (source)	18.2.17 -> 18.2.18
@typescript-eslint/eslint-plugin	6.2.0 -> 6.2.1
@typescript-eslint/parser	6.2.0 -> 6.2.1
@vitejs/plugin-react (source)	4.0.3 -> 4.0.4
@vitest/coverage-v8 (source)	0.33.0 -> 0.34.1
eslint-config-prettier	8.9.0 -> 8.10.0
pnpm (source)	8.6.10 -> 8.6.12
prettier (source)	3.0.0 -> 3.0.1
prisma (source)	5.0.0 -> 5.1.1
react-hook-form (source)	7.45.2 -> 7.45.4
rehype-prism-plus	1.6.1 -> 1.6.2
sass	1.64.1 -> 1.64.2
vitest	0.33.0 -> 0.34.1

---

Release Notes

aws/aws-sdk-js-v3 (@​aws-sdk/client-s3)

v3.385.0

Note: Version bump only for package @​aws-sdk/client-s3

v3.383.0

Note: Version bump only for package @​aws-sdk/client-s3

v3.382.0

Note: Version bump only for package @​aws-sdk/client-s3

3.379.1 (2023-07-28)

Note: Version bump only for package @​aws-sdk/client-s3

aws/aws-sdk-js-v3 (@​aws-sdk/s3-request-presigner)

v3.385.0

Note: Version bump only for package @​aws-sdk/s3-request-presigner

v3.383.0

Note: Version bump only for package @​aws-sdk/s3-request-presigner

v3.382.0

Note: Version bump only for package @​aws-sdk/s3-request-presigner

3.379.1 (2023-07-28)

Note: Version bump only for package @​aws-sdk/s3-request-presigner

codemirror/view (@​codemirror/view)

v6.16.0

Compare Source

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

Compare Source

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
• Prisma Client: disconnect: true does not appear to delete the foreign key in the returned data
• 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

v5.1.0

Compare Source

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 about the release.

Highlights

After two big releases where we released Client extensions for production usage (4.16.0) and made Prisma faster by default (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 by @​alula
• Middlewares: Add to PrismaAction type, missing findUniqueOrThrow and findFirstOrThrow https://github.com/prisma/prisma/pull/17471 by @​mejiaej and missing groupBy https://github.com/prisma/prisma/pull/19985 by @​iurylippo
• Better error message in currently non-supported runtimes like Browser or Vercel Edge Runtime https://github.com/prisma/prisma/pull/20163 by @​andyjy
• Remove error messages for valid NixOS setups https://github.com/prisma/prisma/pull/20138 by @​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

prisma.user.create({ 
  data: { name: "Original name" } 
})

Before v5.1.0

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

-- 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

prisma.user.update({ 
  where: { id: 1 }, 
  data: { name: "updated" } 
})

Before v5.1.0

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

-- 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

prisma.user.update({ 
  where: { id: 1 }, 
  data: { name: "updated" }, 
  includes: { posts: true }  
})

Before v5.1.0

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

-- 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

prisma.user.update({ 
  where: { id: 1 }, 
  data: {}, 
})

Before v5.1.0

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

-- 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

prisma.user.update({ 
  where: { id: 1 }, 
  data: {
    name: "updated",
    posts: {
      update: {
        where: { id: 1 },
        data: {
          title: "updated"
        }
      }
    }
  }
})

Before v5.1.0

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

-- 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. If you didn’t find one for what you’re seeing, please create a new issue. 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 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.

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 <ModelName>Args type as part of that fix. Going forward, <ModelName>DefaultArgs should be used instead.

Fixes and improvements

Prisma Client

• Reduce the number of generated SQL statements for Updates/Inserts
• [v2.17.0] Missing client TS types Aggregate*Args
• Reduce transactions for writes
• Incorrect Include typings when having models called X and XUpdate
• Model named "Check" is incorrectly typed
• Models named Query cause an internal GraphQL Parse Error
• Naming an entity "Query" leads to an error
• Type name clash when Model and ModelUpdate is defined in the schema
• Duplicate identifier 'CheckSelect'
• @prisma/internals (previously @​prisma/sdk) uses deprecated dependencies [email protected] via temp-write 4.0.0
• naming a model Datasource breaks generated return types
• Certain model names cause clashes in generated types
• Type error on query with select field (although query runs successfully)
• $extends TS error: "Inferred type of this node exceeds the maximum length the compiler will serialize" with "declaration": true in tsconfig
• Update operation includes multiple where statements for the same fields
• Type conflict when naming a table {something} and a second table {something}Result
• Type '"findUniqueOrThrow"' is not assignable to type 'PrismaAction'
• Naming a model Promise breaks types for PrismaPromise
• Prisma can't connect with an IPv6 host (on e.g. Fly.io)
• include not working on models ending with ...Update with unique compound index
• Prisma Client: fixing type name clashes from generated client
• Prisma Client: wrong type when using spread operator to set default values on query args
• The generated updateArgs have no update attribute
• 4.16.1 breaks type check
• LogLevel enum conflicts with built-in Prisma type
• Using Prisma.XyzFindManyArgs breaks findMany typing in v4.16.0+
• this.$on("beforeExit") doesn't work anymore on 5.0.0
• Wrong nullable types with fluent API in Prisma 5.0
• Error: Unknown value type on nested create
• Prisma 5.0 Migration findUnique on @unique columns that are enums
• <Tablename>UpsertArgs select field does not match type for db.<tablename>.upsert(item)
• TypeScript Error TS2322 when assigning JavaScript Date object to Prisma DateTime field
• npm install of Prisma CLI fails on preinstall with no logs when Node.js version is lower than minimum
• Types wrongly accept non-array parameter by in groupBy in 5.0.0
• CLI errors with TypeError [ERR_INVALID_URL]: Invalid URL when HTTP(S)_PROXY en var has is set to a URL without a protocol
• tsc --watch fails with JavaScript heap out of memory error
• Hovering over types (intellisense) shows confusing GetResult
• Internal query batching fails when the table name is 'stores'
• Client extensions result extensions should be applied after query extensions

Prisma Studio

• Use directUrl in prisma studio

Language tools (e.g. VS Code)

• The extension for VS Code ignores the modern telemetry flag
• Prisma VS Code extension with mongodb provider crashes when a relation field/type is not defined
• Editing schema.prisma results in wasm panics

Credits

Huge thanks to @​skyzh, @​alula, @​michaelpoellath, @​RobertCraigie, @​Gerschtli, @​andyjy, @​mejiaej, @​iurylippo, @​mrazauskas for helping!

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

v6.2.1

Compare Source

Bug Fixes

• eslint-plugin: [no-inferrable-types] apply also for parameter properties (#​7288) (67f93b1)
• scope-manager: correct decorators(.length) check in ClassVisitor for methods (#​7334) (abbb6c2)

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

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

v6.2.1

Compare Source

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

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

vitejs/vite-plugin-react (@​vitejs/plugin-react)

v4.0.4

Compare Source

• Fix #​198: Enable Babel if presets list is not empty

vitest-dev/vitest (@​vitest/coverage-v8)

v0.34.1

Compare Source

   🐞 Bug Fixes

• Pass --experimental-vm-worker-memory-limit to tinypool  -  by @​AriPerkkio in https://github.com/vitest-dev/vitest/issues/3856 (3c67a)

    View changes on GitHub

v0.34.0

Compare Source

   🚨 Breaking Changes

• Transform mode affects only test files, not regular files  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/3491 (9608b)
  • 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 in https://github.com/vitest-dev/vitest/issues/3615 (0c6f6)
• Remove @vitest/coverage-c8 package  -  by @​AriPerkkio in https://github.com/vitest-dev/vitest/issues/3614 (a90d6)
  • @vitest/coverage-c8 is no longer supported. Please, use @vitest/coverage-v8 instead.
• Support running tests using VM context  -  by @​sheremet-va and @​dammy001 in https://github.com/vitest-dev/vitest/issues/3203 (b0929)
  • 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 of this pool before opening an issue.
• Introduce server option  -  by @​fenghan34 and @​sheremet-va in https://github.com/vitest-dev/vitest/issues/3725 (dc4fa)
  • 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 in https://github.com/vitest-dev/vitest/issues/3574 (1cd4e)
  • 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 and @​eryue0220 in https://github.com/vitest-dev/vitest/issues/3854 (4b946)
  • 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 and @​dammy001 in https://github.com/vitest-dev/vitest/issues/3771 (86934)
• Support config junit reporter className with env  -  by @​InfiniteXyy in https://github.com/vitest-dev/vitest/issues/3808 (e8bc4)
• Running vitest with --related --watch reruns non-affected tests if they were changed during a run  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/3844 (c9aea)

   🐞 Bug Fixes

• Isolate workers between envs and workspaces  -  by @​AriPerkkio (ed4e0)
• Modify condition  -  by @​btea (a78e6)
• Module Graph view is blocking the Console view  -  by @​g4rry420 (3b5f9)
• Port the latest defineConfig type from vite  -  by @​sodatea in https://github.com/vitest-dev/vitest/issues/3804 (9c8e3)
• Don't overwrite Node.js URL global  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/3828 (cdab4)
• ForceRerunTriggers correctly triggers a rerun  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/3829 (17988)
• browser:
  • Don't inline magic-string and estree-walker  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/3726 (ee937)
  • Multi-suite coverage  -  by @​elby22 in https://github.com/vitest-dev/vitest/issues/3806 (5de9a)
• core:
  • DataView comparison does not work in toStrictEqual  -  by @​Dunqing (52aef)
• coverage:
  • V8 provider to pick source maps without url query params  -  by @​AriPerkkio in https://github.com/vitest-dev/vitest/issues/3784 (280e6)
  • Update istanbul-lib-instrument to v6 to fix vulnerable dependency  -  by @​AriPerkkio in https://github.com/vitest-dev/vitest/issues/3814 (f3bd9)
  • Exclude vite virtual modules by default  -  by @​AriPerkkio in https://github.com/vitest-dev/vitest/issues/3794 (3c851)
• node:
  • Guard error info  -  by @​btea (88b39)
• vite-node:
  • Always treat node_modules as modulesDirectory  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/3830 (51ab8)
  • Normalize drive letter to keep the same reference to a module  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/3836 (45521)
  • Correctly resolve hmr filepath  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/3834 (711a6)
• watch:
  • Clear screen on all terminals  -  by @​AriPerkkio in https://github.com/vitest-dev/vitest/issues/3661 (8bd26)

   🏎 Performance

• Deprecate deps.registerNodeLoader  -  by @​sheremet-va (7f45b)
  • 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

prettier/eslint-config-prettier (eslint-config-prettier)

v8.10.0

Compare Source

• Added: [max-statements-per-line]. Thanks to @​Zamiell!

pnpm/pnpm (pnpm)

v8.6.12

Compare Source

Patch Changes

• Make the error message friendlier when a user attempts to run a command that does not exist #​6887.
• pnpm patch should work correctly when shared-workspace-file is set to false #​6885.
• pnpm env use should retry deleting the previous Node.js executable #​6587.
• pnpm dlx should not print an error stack when the underlying script execution fails #​6698.
• When showing the download progress of large tarball files, always display the same number of digits after the decimal point #​6901.
• Report download progress less frequently to improve performance #​6906.
• pnpm install --frozen-lockfile --lockfile-only should fail if the lockfile is not up to date with the package.json files #​6913.

Our Gold Sponsors

Our Silver Sponsors

v8.6.11

Compare Source

Patch Changes

• Change the install error message when a lockfile is wanted but absent to indicate the wanted lockfile is absent, not present. This now reflects the actual error #​6851.
• When dealing with a local dependency that is a path to a symlink, a new symlink should be created to the original symlink, not to the actual directory location.
• The length of the temporary file names in the content-addressable store reduced in order to prevent ENAMETOOLONG errors from happening #​6842.
• Don't print "added" stats, when installing with --lockfile-only.
• Installation of a git-hosted dependency should not fail if the pnpm-lock.yaml file of the installed dependency is not up-to-date #​6865.
• Don't ignore empty strings in params #​6594.
• Always set dedupe-peer-dependents to false, when running installation during deploy #​6858.
• When several containers use the same store simultaneously, there's a chance that multiple containers may create a temporary file at the same time. In such scenarios, pnpm could fail to rename the temporary file in one of the containers. This issue has been addressed: pnpm will no longer fail if the temporary file is absent but the destination file exists.
• Authorization token should be found in the configuration, when the requested URL is explicitly specified with a default port (443 on HTTPS or 80 on HTTP) #​6863.

Our Gold Sponsors

Our Silver Sponsors

prettier/prettier (prettier)

v3.0.1

Compare Source

diff

Fix cursor positioning for a special case (#​14812 by @​fisker)

// <|> 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 by @​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 by @​auvred)

// Input
function fn() {
  return (
    /**
     * @​type {...}
     */ expresssion
  )
}

// Prettier 3.0.0
function fn() {
  return /**
   * @​type {...}
   */ expresssio

</details>

---

### Configuration

📅 **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](https://togithub.com/renovatebot/renovate/discussions) if that's undesired.

---

 - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box

---

This PR has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://developer.mend.io/github/programming-in-th/programming.in.th).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNi4yNy4xIiwidXBkYXRlZEluVmVyIjoiMzYuMjcuMSIsInRhcmdldEJyYW5jaCI6Im1haW4ifQ==-->

[vercel]

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]

Coverage Report

Status	Category	Percentage	Covered / Total
🔵	Lines	100%	147 / 147
🔵	Statements	100%	147 / 147
🔵	Functions	100%	4 / 4
🔵	Branches	100%	17 / 17

File Coverage

No changed files found.

Generated in workflow #134