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

renovate · 2022-12-04T00:45:43Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@prisma/client (source)	`^4.6.1` -> `^4.7.1`
@types/node (source)	`18.11.9` -> `18.11.10`
@types/react (source)	`18.0.25` -> `18.0.26`
@typescript-eslint/eslint-plugin	`^5.44.0` -> `^5.45.0`
@typescript-eslint/parser	`^5.44.0` -> `^5.45.0`
eslint (source)	`^8.28.0` -> `^8.29.0`
eslint-config-next	`13.0.5` -> `13.0.6`
framer-motion	`^7.6.12` -> `^7.6.18`
next (source)	`13.0.5` -> `13.0.6`
prisma (source)	`^4.6.1` -> `^4.7.1`
react-select (source)	`^5.6.1` -> `^5.7.0`
react-spinners (source)	`^0.13.6` -> `^0.13.7`

Release Notes

prisma/prisma

`v4.7.1`

Compare Source

Today, we are issuing the 4.7.1 patch release.

Fixes in Prisma Client

`v4.7.0`

Compare Source

🌟 Help us spread the word about Prisma by starring the repo or tweeting about the release. 🌟

Highlights

Interactive transactions are now Generally Available

After an extensive Preview phase and lots of great feedback from our community, we're excited to announce that interactiveTransactions is now Generally Available and production ready! 🚀

Interactive transactions allow you to pass an async function into a $transaction, and execute any code you like between the individual Prisma Client queries. Once the application reaches the end of the function, the transaction is committed to the database. If your application encounters an error as the transaction is being executed, the function will throw an exception and automatically rollback the transaction.

Here are some of the feature highlights we've built:

Support for defining transaction isolation levels — from 4.2.0
Support for the Prisma Data Proxy — from 4.6.0

Here's an example of an interactive transaction with a Serializable isolation level:

await prisma.$transaction(
  async (prisma) => {
    // Your transaction...
  },
  {
    isolationLevel: Prisma.TransactionIsolationLevel.Serializable,
    maxWait: 5000,
    timeout: 10000,
  }
)

You can now remove the interactiveTransactions Preview feature in your schema.

Relation mode is Generally Available

This release marks relationMode="prisma" as stable for our users working with databases that don't rely on foreign keys to manage relations. 🎉

Prisma’s relation mode started as a way to support PlanetScale which does not allow you to create foreign keys for better online migration support. We transformed that into our Referential Integrity Emulation in 3.1.1 when we realised that more users could benefit from it, and then integrated it as the default mode for MongoDB, which generally does not have foreign keys. Prisma needed to use emulation to give the same guarantees.

We then realized the feature was more than just referential integrity and affected how relations work. To reflect this, we renamed the feature to relation mode and the datasource property to relationMode in 4.5.0

Index warnings for `relationMode = "prisma"`

In this release, we've added a warning to our Prisma schema validation that informs you that the lack of foreign keys might result in slower performance — and that you should add an @@index manually to your schema to counter that. This ensures your queries are equally fast in relation mode prisma as they are with foreign keys.

With relationMode = "prisma", no foreign keys are used, so relation fields will not benefit from the index usually created by the relational database under the hood. This can lead to slower performance when querying these fields. We recommend manually adding an index.

We also added a fix to our VS Code extension to help adding the suggested index with minimal effort:

If you are currently using the Preview feature flag to enable relation mode, you can now remove referentialIntegrity from the previewFeatures in your generator client block in your Prisma schema.

For more information, check out our updated relation mode documentation.

Prisma Client Extensions (Preview)

This release adds Preview support for Prisma Client Extensions. This feature introduces new capabilities to customize and extend Prisma Client. Today we are opening up four areas for extending Prisma Client:

model: add custom methods or fields to your models
client: add client-level methods to Prisma Client
result: add custom fields to your query results
query: create custom Prisma Client queries

Prisma Client Extensions are self-contained scripts that can tweak the behavior of models, queries, results, and the client (Prisma Client) as a whole. You can associate a single or multiple extensions with an extended client to mix and match Prisma to your needs.

Prisma Client Extensions enables many use cases such as defining virtual fields, custom validation, and custom queries.

It also enables you to share your client extensions with others and import client extensions developed by others into your project.

For example, given the following schema:

datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["clientExtensions"]
}

model User {
  id        Int     @&#8203;id @&#8203;default(autoincrement())
  email     String  @&#8203;unique
  firstName String?
  lastName  String
}

You can create a computed field called fullName as follows:

import { PrismaClient } from "@&#8203;prisma/client"

const prisma = new PrismaClient()
  .$extends({
    result: {
      user: {
        fullName: {
          // the dependencies
          needs: { firstName: true, lastName: true },
          compute(user) {
            // the computation logic
            return `${user.firstName} ${user.lastName}`
          },
        },
      },
    },
  })

We're excited to see what you build with them! For more information, check out our docs and let us know what you think in this GitHub issue.

Multi-schema support for PostgreSQL (Preview)

We're pleased to announce that this release adds support for multi-schema support for PostgreSQL. The ability to query and manage multiple database schemas has been a long-standing feature request from our community.

This release adds support for the following:

Introspecting databases that organize objects in multiple database schemas
Managing multi-schema database setups directly from Prisma schema
Generating migrations that are database schema-aware with Prisma Migrate
Querying across multiple database schemas with Prisma Client

If you already have a PostgreSQL database using multiple schemas, you can quickly get up and running using prisma db pull — on enabling the Preview feature and specifying the schemas in the datasource block similar to the example below.

You can get started with defining multiple schemas in your Prisma schema as follows:

generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["multiSchema"]
}

datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
  schemas  = ["base", "transactional"]
}

model User {
  id     Int     @&#8203;id
  orders Order[]

  @&#8203;@&#8203;schema("base")
}

model Order {
  id      Int  @&#8203;id
  user    User @&#8203;relation(fields: [id], references: [id])
  user_id Int

  @&#8203;@&#8203;schema("transactional")
}

Then generate and apply the changes to your database with prisma migrate dev.

We want to thank all our users for helping us design the feature since the early proposal on GitHub up to our current Preview release.

For further details, refer to our documentation and let us know what you think in this GitHub issue.

Request for feedback

Our Product team is currently running a survey for designing Database Views support for Prisma and we would appreciate your feedback.

Fixes and improvements

Prisma Client

Prisma

Prisma Migrate

Language tools (e.g. VS Code)

Prisma Engines

bug(fmt): quick-fixes break with no newline after model in schema

Credits

Huge thanks to @cmd-johnson, @jsoref, @miguelgargallo for helping!

Prisma Data Platform

We're working on the Prisma Data Platform — a collaborative environment for connecting apps to databases. It includes the following:

Data Browser for navigating, editing, and querying data
Data Proxy for your database's persistent, reliable, and scalable connection pooling.
Query Console for experimenting with queries

Try it out. Let us know what you think!

📺 Join us for another "What's new in Prisma" live stream

Learn about the latest release and other news from the Prisma community by joining us for another "What's new in Prisma" live stream.

The stream takes place on YouTube on Thursday, December 1 at 5 pm Berlin | 8 am San Francisco.

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

`v5.45.0`

Compare Source

Bug Fixes

eslint-plugin: [array-type] --fix flag removes parentheses from type (#5997) (42b33af)
eslint-plugin: [keyword-spacing] prevent crash on no options (#6073) (1f19998)
eslint-plugin: [member-ordering] support private fields (#5859) (f02761a)
eslint-plugin: [prefer-readonly] report if a member's property is reassigned (#6043) (6e079eb)

Features

eslint-plugin: [member-ordering] add a required option for required vs. optional member ordering (#5965) (2abadc6)

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

`v5.45.0`

Compare Source

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

eslint/eslint

`v8.29.0`

Compare Source

Features

49a07c5 feat: add allowParensAfterCommentPattern option to no-extra-parens (#16561) (Nitin Kumar)
e6a865d feat: prefer-named-capture-group add suggestions (#16544) (Josh Goldberg)
a91332b feat: In no-invalid-regexp validate flags also for non-literal patterns (#16583) (trosos)

Documentation

0311d81 docs: Configuring Plugins page intro, page tweaks, and rename (#16534) (Ben Perlmutter)
57089b1 docs: add a property assignment example for camelcase rule (#16605) (Milos Djermanovic)
b6ab030 docs: add docs codeowners (#16601) (Strek)
6380c87 docs: fix sitemap and feed (#16592) (Milos Djermanovic)
ade621d docs: perf debounce the search query (#16586) (Shanmughapriyan S)
fbcf3ab docs: fix searchbar clear button (#16585) (Shanmughapriyan S)
f894035 docs: HTTPS link to yeoman.io (#16582) (Christian Oliff)
de12b26 docs: Update configuration file pages (#16509) (Ben Perlmutter)
1ae9f20 docs: update correct code examples for no-extra-parens rule (#16560) (Nitin Kumar)

Chores

7628403 chore: add discord channel link (#16590) (Amaresh S M)
f5808cb chore: fix rule doc headers check (#16564) (Milos Djermanovic)

vercel/next.js

`v13.0.6`

Compare Source

Core Changes

test(integration): allow to run --turbo dev server tests dynamically : #42967
Ensure loaderFile is included in webpack cache key: #43315
Improve @next/font error handling: #43298
Improve RSC plugin to provide better errors: #42435
fix appDir returning 404 in production with "output": "standalone": #43268
Fix outputting un-necessary trace files for edge functions: #43304
fix: apply default export interop to pages/_app: #43335
Fix package resolution issue in app dir: #43349
Get correct chunks in flight-manifest on Windows: #43334
Resolve RSC / HTML rendering errors in error overlay: #43332
App directory next/link dynamic href dev error: #43074
Add ref forwarding for next/image: #43193
Always transform styled-jsx for rsc and error with client-only condition: #43386
dynamic = 'error' should only throw if page didn't get exported: #43377
fix output: "standalone" returning 500 error on certain pages when built without pages/: #43336
Fix "apply() is only allowed in ready status (state: idle)" HMR errors: #43242
Add gSP and gSSP checks for both server and client layers in the SWC transform: #43391
Make sure the TS plugin works for src/app: #43412
Remove stack trace from full reload warning: #43453
Upgrade compiled undici: #43481
Fix missing cleanup process in flight plugin globals: #43297
Fix matchers in middleware manifest: #43549
rsc: bundle legacy head as client component: #43425
Remove useState from next/image: #43587
Group redirect status imports: #43480
Fix Failed to copy traced files for Edge functions and handle its files with middleware-manifest.json: #43326
Update next/link default legacyBehavior: #42623
fix: Dynamic Usage Error when using previewData with generateStaticParams and appDir: #43395
Minimized runtime errors in app dir: #43511

Documentation Changes

Add link back to font video in Font docs.: #43440
docs: update known Safari bug: #43513
Add yarn berry dependency upgrade example for Next 12 to 13 upgrade documentation.: #43472
Clarify that publicRuntimeConfig and serverRuntimeConfig do not work with Output File Tracing: #43443
adding note that edge api routes are not supported with ISR: #43572
Improve docs for URL Imports: #43615