profile
viewpoint
Brandon Bayer flybayer @BeeDesignLLC Digital Nomad https://twitter.com/flybayer Creator of Blitz.js — Full-time Open Sourcerer

blitz-js/blitz 5418

⚡️The Fullstack React Framework — built on Next.js

blitz-js/superjson 324

Safely serialize JavaScript expressions to a superset of JSON, which includes Dates, BigInts, and more.

blitz-js/babel-plugin-superjson-next 13

Automatically transform your Next.js Pages to use SuperJSON

blitz-js/awesome-blitzjs 12

Curated list of awesome resources for blitz.js

flybayer/create-react-webextension 7

Create React WebExtensions with no build configuration.

flybayer/dot_vim 7

Simple, Beautiful, and Screaming Fast Vim Config

flybayer/dotfiles 3

My rcm dotfiles

flybayer/blitz-sentry 1

Example Blitz Sentry integration

flybayer/booking-js 1

:date: Make a beautiful embeddable booking widget in minutes

flybayer/ale 0

Asynchronous linting/fixing for Vim and Language Server Protocol (LSP) integration

issue openedblitz-js/blitz

Upon creating new project and running for the first time -> blank screen and "Uncaught TypeError: __webpack_require__(...) is not a function"

What is the problem?

When I create a fresh project and try to run it for the first time, I get the blank screen. In the console I get the following message: Uncaught TypeError: __webpack_require__(...) is not a function

Steps to Reproduce

  1. Create a new project with blitz new
  2. Run it with blitz start

Versions

Node 14.5.0

output of `blitz --version --verbose`

macOS Catalina | darwin-x64 | Node: v14.5.0

blitz: 0.26.0 (global) blitz: 0.26.0 (local)

Package manager: npm System: OS: macOS 10.15.7 CPU: (8) x64 Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz Memory: 959.67 MB / 16.00 GB Shell: 3.2.57 - /bin/bash Binaries: Node: 14.5.0 - ~/.nvm/versions/node/v14.5.0/bin/node Yarn: Not Found npm: 6.14.5 - ~/.nvm/versions/node/v14.5.0/bin/npm Watchman: Not Found npmPackages: @prisma/cli: 2.12.0 => 2.12.0 @prisma/client: 2.12.0 => 2.12.0 blitz: 0.26.0 => 0.26.0 react: 0.0.0-experimental-4ead6b530 => 0.0.0-experimental-4ead6b530 react-dom: 0.0.0-experimental-4ead6b530 => 0.0.0-experimental-4ead6b530 typescript: 4.1.2 => 4.1.2

Other

Please include applicable logs and screenshots that show your problem.

created time in 8 hours

issue commentblitz-js/blitz

UnhandledPromiseRejectionWarning: Error: Key - in file-pipeline

I started getting these as well, however, upon upgrade to v0.25.x canary, they just disappeared and now its all clean.

flybayer

comment created time in 11 hours

Pull request review commentblitz-js/blitz

WIP: Add theme ui recipe

 dist **/.envrc .blitz-* .blitz-cli-cache+<<<<<<< HEAD+todo-list.md+.vscode+*.code-workspace+======= .vscode .tsbuildinfo+>>>>>>> upstream/canary

thanks brandon!

tundera

comment created time in 14 hours

pull request commentblitz-js/blitz

Change base64 encoding/decoding methods to allow for unicode chars in session data

I think I should add b64-lite to package.json of core package since it hadn't been used there until this PR, shouldn't I?

konradkalemba

comment created time in 21 hours

issue commentblitz-js/blitz

Error "Failed to execute 'btoa'" occur when setting multibyte string to session.create

I think I should add b64-lite to package.json of core package since it hadn't been used there until this PR, shouldn't I?

kyken

comment created time in 21 hours

PR opened blitz-js/blitz

Reviewers
Change base64 encoding/decoding methods to allow for unicode chars in session data

Closes: #1455

What are the changes and their implications?

Originally used atob and btoa methods from b64-lite package don't support unicode characters. Fortunately, within the same package there are alternative methods that allow for unicode (fromBase64 and toBase64). This PR basically replaces the former methods with the latter ones.

As for decoding public data on browser-end, native atob method doesn't support unicode chars either. To fix this we could use code snippet provided in the linked SO answer, but since the package we use for base64 operations is very small I just used its fromBase64 method.

Checklist

  • [x] Tests added for changes
  • [ ] <s>PR submitted to blitzjs.com for any user facing changes</s>

<!-- IMPORTANT: Make sure to check the "Allow edits from maintainers" box below this window -->

+20 -11

0 comment

4 changed files

pr created time in a day

push eventblitz-js/blitz

depfu[bot]

commit sha 78007fc967c2af6c1f83af564387cbb439de5c19

Upgrade @prisma/client: 2.12.0-dev.53 → 2.12.0 (patch) (#1522) * Update @prisma/client to version 2.12.0 * fix Co-authored-by: depfu[bot] <23717796+depfu[bot]@users.noreply.github.com> Co-authored-by: Brandon Bayer <b@bayer.ws>

view details

push time in a day

delete branch blitz-js/blitz

delete branch : depfu/update/yarn/@prisma/client-2.12.0

delete time in a day

PR merged blitz-js/blitz

Upgrade @prisma/client: 2.12.0-dev.53 → 2.12.0 (patch) 0 - <(^_^)> - merge it! ✌️ depfu status/in-review

Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ @​prisma/client (2.10.0 → 2.12.0)

Sorry, we couldn't find anything useful about this release.


Depfu Status

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

<details><summary>All Depfu comment commands</summary> <blockquote><dl> <dt>@​depfu rebase</dt><dd>Rebases against your default branch and redoes this update</dd> <dt>@​depfu recreate</dt><dd>Recreates this PR, overwriting any edits that you've made to it</dd> <dt>@​depfu merge</dt><dd>Merges this PR once your tests are passing and conflicts are resolved</dd> <dt>@​depfu close</dt><dd>Closes this PR and deletes the branch</dd> <dt>@​depfu reopen</dt><dd>Restores the branch and reopens this PR (if it's closed)</dd> <dt>@​depfu pause</dt><dd>Ignores all future updates for this dependency and closes this PR</dd> <dt>@​depfu pause [minor|major]</dt><dd>Ignores all future minor/major updates for this dependency and closes this PR</dd> <dt>@​depfu resume</dt><dd>Future versions of this dependency will create PRs again (leaves this PR as is)</dd> </dl></blockquote> </details>

+14 -36

5 comments

5 changed files

depfu[bot]

pr closed time in a day

pull request commentblitz-js/blitz

Upgrade @prisma/client: 2.12.0-dev.53 → 2.12.0 (patch)

Sorry, but the merge failed with:

You're not authorized to push to this branch. Visit https://docs.github.com/articles/about-protected-branches/ for more information.

depfu[bot]

comment created time in a day

push eventblitz-js/blitz

depfu[bot]

commit sha aba7f64a1b1f1a15d321953f4c27d3a8515e7422

Update @prisma/client to version 2.12.0

view details

push time in a day

push eventblitz-js/blitz

depfu[bot]

commit sha 9e8582b9f86c139cc83b0703e3ce047defb4f6dc

Update @prisma/client to version 2.12.0

view details

push time in a day

push eventblitz-js/blitz

Abdullah Mzaien

commit sha 61bbc43497dbd0c2f3957eec88f7be18a8883fc9

(recipe) Update tailwind recipe to v2 (#1486) Co-authored-by: Mzaien <s201540840@kfupm.edu.sa> Co-authored-by: Brandon Bayer <b@bayer.ws>

view details

allcontributors[bot]

commit sha 24082d53e0d57cfa20ea37e93006105ccd7412a9

docs: add Mzaien as a contributor (#1526) Co-authored-by: allcontributors[bot] <46447321+allcontributors[bot]@users.noreply.github.com> (meta)

view details

Alex Johansson

commit sha 1194ffde82e1631d9a20f8de027d8f734d604979

Change `useParam` / `useParams` to always return `undefined` for empty/invalid values instead of `""` and `NaN` (patch) (#1491) * do parsing in useParams instead of useParam * simplify # Conflicts: # packages/core/src/use-params.ts * fix typescript error Co-authored-by: Brandon Bayer <b@bayer.ws> Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>

view details

depfu[bot]

commit sha f96bcb80d0f0d98c4436a3f37a89bc056bba4315

Upgrade @prisma/cli: 2.10.0 → 2.12.0 (example) (#1523) Co-authored-by: depfu[bot] <23717796+depfu[bot]@users.noreply.github.com>

view details

depfu[bot]

commit sha b6b898c9b3baa9c5c9e8bb68f4a318de2399ab46

Upgrade @prisma/sdk: 2.10.0 → 2.12.0 (example) (#1524) Co-authored-by: depfu[bot] <23717796+depfu[bot]@users.noreply.github.com>

view details

Brandon Bayer

commit sha c1ac5b027e9e7cf70adb47f950a732b712e19a65

Change `prisma.findOne` to `prisma.findFirst` for Prisma 2.12 compatibility (#1525) (minor)

view details

depfu[bot]

commit sha a56006bee4eb7ea3720d88f315a3fb47a6fc02be

Update @prisma/client to version 2.12.0

view details

push time in a day

pull request commentblitz-js/blitz

Upgrade @prisma/client: 2.12.0-dev.53 → 2.12.0 (patch)

This PR currently has a merge conflict. Please resolve this and then re-add the 0 - <(^_^)> - merge it! ✌️ label.

depfu[bot]

comment created time in a day

push eventblitz-js/blitz

Alex Johansson

commit sha 1194ffde82e1631d9a20f8de027d8f734d604979

Change `useParam` / `useParams` to always return `undefined` for empty/invalid values instead of `""` and `NaN` (patch) (#1491) * do parsing in useParams instead of useParam * simplify # Conflicts: # packages/core/src/use-params.ts * fix typescript error Co-authored-by: Brandon Bayer <b@bayer.ws> Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>

view details

push time in a day

PR merged blitz-js/blitz

Change `useParam` / `useParams` to always return `undefined` for empty/invalid values instead of `""` and `NaN` (patch) 0 - <(^_^)> - merge it! ✌️ status/in-review

Related: #1427 #1474

What are the changes and their implications?

  • Refactor useParam / useParams so that useParams does all the typecasting magic and useParam simply gets params[key]
  • useParam with number will never return NaN

Checklist.

  • [x] Tests added for changes
  • [ ] PR submitted to blitzjs.com for any user facing changes
+37 -52

1 comment

3 changed files

KATT

pr closed time in a day

pull request commentblitz-js/blitz

docs: add Mzaien as a contributor

Size Change: 0 B

Total Size: 195 kB

<details><summary>ℹ️ <strong>View Unchanged</strong></summary>

Filename Size Change
packages/blitz/dist/cli.js 15.7 kB 0 B
packages/blitz/dist/index.js 245 B 0 B
packages/config/dist/config.cjs.development.js 1.35 kB 0 B
packages/config/dist/config.cjs.production.min.js 917 B 0 B
packages/config/dist/config.esm.js 1.28 kB 0 B
packages/config/dist/index.js 143 B 0 B
packages/core/dist/core.cjs.development.js 12.9 kB 0 B
packages/core/dist/core.cjs.production.min.js 6.99 kB 0 B
packages/core/dist/core.esm.js 12.5 kB 0 B
packages/core/dist/index.js 141 B 0 B
packages/display/dist/display.cjs.development.js 1.43 kB 0 B
packages/display/dist/display.cjs.production.min.js 819 B 0 B
packages/display/dist/display.esm.js 1.33 kB 0 B
packages/display/dist/index.js 144 B 0 B
packages/file-pipeline/dist/file-pipeline.cjs.development.js 5.9 kB 0 B
packages/file-pipeline/dist/file-pipeline.cjs.production.min.js 3.02 kB 0 B
packages/file-pipeline/dist/file-pipeline.esm.js 5.76 kB 0 B
packages/file-pipeline/dist/index.js 147 B 0 B
packages/generator/dist/generator.cjs.development.js 15.6 kB 0 B
packages/generator/dist/generator.cjs.production.min.js 9.47 kB 0 B
packages/generator/dist/generator.esm.js 15.3 kB 0 B
packages/generator/dist/index.js 145 B 0 B
packages/generator/dist/templates/app/babel.config.js 77 B 0 B
packages/generator/dist/templates/app/blitz.config.js 324 B 0 B
packages/generator/dist/templates/app/jest.config.js 682 B 0 B
packages/generator/dist/templates/app/test/__mocks__/fileMock.js 54 B 0 B
packages/installer/dist/index.js 145 B 0 B
packages/installer/dist/installer.cjs.development.js 7.69 kB 0 B
packages/installer/dist/installer.cjs.production.min.js 5.14 kB 0 B
packages/installer/dist/installer.esm.js 7.54 kB 0 B
packages/repl/dist/index.js 141 B 0 B
packages/repl/dist/repl.cjs.development.js 1.81 kB 0 B
packages/repl/dist/repl.cjs.production.min.js 1.08 kB 0 B
packages/repl/dist/repl.esm.js 1.69 kB 0 B
packages/server/dist/index.js 142 B 0 B
packages/server/dist/server.cjs.development.js 22.2 kB 0 B
packages/server/dist/server.cjs.production.min.js 12.7 kB 0 B
packages/server/dist/server.esm.js 22.3 kB 0 B

</details>

<a href="https://github.com/preactjs/compressed-size-action"><sub>compressed-size-action</sub></a>

allcontributors[bot]

comment created time in a day

pull request commentblitz-js/blitz

Upgrade @prisma/cli: 2.10.0 → 2.12.0 (minor)

Sorry, but the merge failed with:

You're not authorized to push to this branch. Visit https://docs.github.com/articles/about-protected-branches/ for more information.

depfu[bot]

comment created time in a day

pull request commentblitz-js/blitz

Change `prisma.findOne` to `prisma.findFirst` for Prisma 2.12 compatibility

Size Change: +8 B (0%)

Total Size: 195 kB

Filename Size Change
packages/server/dist/server.cjs.development.js 22.2 kB +3 B (0%)
packages/server/dist/server.cjs.production.min.js 12.7 kB +2 B (0%)
packages/server/dist/server.esm.js 22.3 kB +3 B (0%)

<details><summary>ℹ️ <strong>View Unchanged</strong></summary>

Filename Size Change
packages/blitz/dist/cli.js 15.7 kB 0 B
packages/blitz/dist/index.js 245 B 0 B
packages/config/dist/config.cjs.development.js 1.35 kB 0 B
packages/config/dist/config.cjs.production.min.js 917 B 0 B
packages/config/dist/config.esm.js 1.28 kB 0 B
packages/config/dist/index.js 143 B 0 B
packages/core/dist/core.cjs.development.js 12.9 kB 0 B
packages/core/dist/core.cjs.production.min.js 6.99 kB 0 B
packages/core/dist/core.esm.js 12.5 kB 0 B
packages/core/dist/index.js 141 B 0 B
packages/display/dist/display.cjs.development.js 1.43 kB 0 B
packages/display/dist/display.cjs.production.min.js 819 B 0 B
packages/display/dist/display.esm.js 1.33 kB 0 B
packages/display/dist/index.js 144 B 0 B
packages/file-pipeline/dist/file-pipeline.cjs.development.js 5.9 kB 0 B
packages/file-pipeline/dist/file-pipeline.cjs.production.min.js 3.02 kB 0 B
packages/file-pipeline/dist/file-pipeline.esm.js 5.76 kB 0 B
packages/file-pipeline/dist/index.js 147 B 0 B
packages/generator/dist/generator.cjs.development.js 15.6 kB 0 B
packages/generator/dist/generator.cjs.production.min.js 9.47 kB 0 B
packages/generator/dist/generator.esm.js 15.3 kB 0 B
packages/generator/dist/index.js 145 B 0 B
packages/generator/dist/templates/app/babel.config.js 77 B 0 B
packages/generator/dist/templates/app/blitz.config.js 324 B 0 B
packages/generator/dist/templates/app/jest.config.js 682 B 0 B
packages/generator/dist/templates/app/test/__mocks__/fileMock.js 54 B 0 B
packages/installer/dist/index.js 145 B 0 B
packages/installer/dist/installer.cjs.development.js 7.69 kB 0 B
packages/installer/dist/installer.cjs.production.min.js 5.14 kB 0 B
packages/installer/dist/installer.esm.js 7.54 kB 0 B
packages/repl/dist/index.js 141 B 0 B
packages/repl/dist/repl.cjs.development.js 1.81 kB 0 B
packages/repl/dist/repl.cjs.production.min.js 1.08 kB 0 B
packages/repl/dist/repl.esm.js 1.69 kB 0 B
packages/server/dist/index.js 142 B 0 B

</details>

<a href="https://github.com/preactjs/compressed-size-action"><sub>compressed-size-action</sub></a>

flybayer

comment created time in a day

pull request commentblitz-js/blitz

Upgrade @prisma/client: 2.12.0-dev.53 → 2.12.0 (patch)

Size Change: 0 B

Total Size: 195 kB

<details><summary>ℹ️ <strong>View Unchanged</strong></summary>

Filename Size Change
packages/blitz/dist/cli.js 15.7 kB 0 B
packages/blitz/dist/index.js 245 B 0 B
packages/config/dist/config.cjs.development.js 1.35 kB 0 B
packages/config/dist/config.cjs.production.min.js 917 B 0 B
packages/config/dist/config.esm.js 1.28 kB 0 B
packages/config/dist/index.js 143 B 0 B
packages/core/dist/core.cjs.development.js 12.9 kB 0 B
packages/core/dist/core.cjs.production.min.js 6.99 kB 0 B
packages/core/dist/core.esm.js 12.5 kB 0 B
packages/core/dist/index.js 141 B 0 B
packages/display/dist/display.cjs.development.js 1.43 kB 0 B
packages/display/dist/display.cjs.production.min.js 819 B 0 B
packages/display/dist/display.esm.js 1.33 kB 0 B
packages/display/dist/index.js 144 B 0 B
packages/file-pipeline/dist/file-pipeline.cjs.development.js 5.9 kB 0 B
packages/file-pipeline/dist/file-pipeline.cjs.production.min.js 3.02 kB 0 B
packages/file-pipeline/dist/file-pipeline.esm.js 5.76 kB 0 B
packages/file-pipeline/dist/index.js 147 B 0 B
packages/generator/dist/generator.cjs.development.js 15.6 kB 0 B
packages/generator/dist/generator.cjs.production.min.js 9.47 kB 0 B
packages/generator/dist/generator.esm.js 15.3 kB 0 B
packages/generator/dist/index.js 145 B 0 B
packages/generator/dist/templates/app/babel.config.js 77 B 0 B
packages/generator/dist/templates/app/blitz.config.js 324 B 0 B
packages/generator/dist/templates/app/jest.config.js 682 B 0 B
packages/generator/dist/templates/app/test/__mocks__/fileMock.js 54 B 0 B
packages/installer/dist/index.js 145 B 0 B
packages/installer/dist/installer.cjs.development.js 7.69 kB 0 B
packages/installer/dist/installer.cjs.production.min.js 5.14 kB 0 B
packages/installer/dist/installer.esm.js 7.54 kB 0 B
packages/repl/dist/index.js 141 B 0 B
packages/repl/dist/repl.cjs.development.js 1.81 kB 0 B
packages/repl/dist/repl.cjs.production.min.js 1.08 kB 0 B
packages/repl/dist/repl.esm.js 1.69 kB 0 B
packages/server/dist/index.js 142 B 0 B
packages/server/dist/server.cjs.development.js 22.2 kB 0 B
packages/server/dist/server.cjs.production.min.js 12.7 kB 0 B
packages/server/dist/server.esm.js 22.3 kB 0 B

</details>

<a href="https://github.com/preactjs/compressed-size-action"><sub>compressed-size-action</sub></a>

depfu[bot]

comment created time in a day

pull request commentblitz-js/blitz

Upgrade @prisma/sdk: 2.10.0 → 2.12.0 (minor)

Size Change: 0 B

Total Size: 195 kB

<details><summary>ℹ️ <strong>View Unchanged</strong></summary>

Filename Size Change
packages/blitz/dist/cli.js 15.7 kB 0 B
packages/blitz/dist/index.js 245 B 0 B
packages/config/dist/config.cjs.development.js 1.35 kB 0 B
packages/config/dist/config.cjs.production.min.js 917 B 0 B
packages/config/dist/config.esm.js 1.28 kB 0 B
packages/config/dist/index.js 143 B 0 B
packages/core/dist/core.cjs.development.js 12.9 kB 0 B
packages/core/dist/core.cjs.production.min.js 6.99 kB 0 B
packages/core/dist/core.esm.js 12.5 kB 0 B
packages/core/dist/index.js 141 B 0 B
packages/display/dist/display.cjs.development.js 1.43 kB 0 B
packages/display/dist/display.cjs.production.min.js 819 B 0 B
packages/display/dist/display.esm.js 1.33 kB 0 B
packages/display/dist/index.js 144 B 0 B
packages/file-pipeline/dist/file-pipeline.cjs.development.js 5.9 kB 0 B
packages/file-pipeline/dist/file-pipeline.cjs.production.min.js 3.02 kB 0 B
packages/file-pipeline/dist/file-pipeline.esm.js 5.76 kB 0 B
packages/file-pipeline/dist/index.js 147 B 0 B
packages/generator/dist/generator.cjs.development.js 15.6 kB 0 B
packages/generator/dist/generator.cjs.production.min.js 9.47 kB 0 B
packages/generator/dist/generator.esm.js 15.3 kB 0 B
packages/generator/dist/index.js 145 B 0 B
packages/generator/dist/templates/app/babel.config.js 77 B 0 B
packages/generator/dist/templates/app/blitz.config.js 324 B 0 B
packages/generator/dist/templates/app/jest.config.js 682 B 0 B
packages/generator/dist/templates/app/test/__mocks__/fileMock.js 54 B 0 B
packages/installer/dist/index.js 145 B 0 B
packages/installer/dist/installer.cjs.development.js 7.69 kB 0 B
packages/installer/dist/installer.cjs.production.min.js 5.14 kB 0 B
packages/installer/dist/installer.esm.js 7.54 kB 0 B
packages/repl/dist/index.js 141 B 0 B
packages/repl/dist/repl.cjs.development.js 1.81 kB 0 B
packages/repl/dist/repl.cjs.production.min.js 1.08 kB 0 B
packages/repl/dist/repl.esm.js 1.69 kB 0 B
packages/server/dist/index.js 142 B 0 B
packages/server/dist/server.cjs.development.js 22.2 kB 0 B
packages/server/dist/server.cjs.production.min.js 12.7 kB 0 B
packages/server/dist/server.esm.js 22.3 kB 0 B

</details>

<a href="https://github.com/preactjs/compressed-size-action"><sub>compressed-size-action</sub></a>

depfu[bot]

comment created time in a day

pull request commentblitz-js/blitz

Upgrade @prisma/cli: 2.10.0 → 2.12.0 (minor)

Size Change: 0 B

Total Size: 195 kB

<details><summary>ℹ️ <strong>View Unchanged</strong></summary>

Filename Size Change
packages/blitz/dist/cli.js 15.7 kB 0 B
packages/blitz/dist/index.js 245 B 0 B
packages/config/dist/config.cjs.development.js 1.35 kB 0 B
packages/config/dist/config.cjs.production.min.js 917 B 0 B
packages/config/dist/config.esm.js 1.28 kB 0 B
packages/config/dist/index.js 143 B 0 B
packages/core/dist/core.cjs.development.js 12.9 kB 0 B
packages/core/dist/core.cjs.production.min.js 6.99 kB 0 B
packages/core/dist/core.esm.js 12.5 kB 0 B
packages/core/dist/index.js 141 B 0 B
packages/display/dist/display.cjs.development.js 1.43 kB 0 B
packages/display/dist/display.cjs.production.min.js 819 B 0 B
packages/display/dist/display.esm.js 1.33 kB 0 B
packages/display/dist/index.js 144 B 0 B
packages/file-pipeline/dist/file-pipeline.cjs.development.js 5.9 kB 0 B
packages/file-pipeline/dist/file-pipeline.cjs.production.min.js 3.02 kB 0 B
packages/file-pipeline/dist/file-pipeline.esm.js 5.76 kB 0 B
packages/file-pipeline/dist/index.js 147 B 0 B
packages/generator/dist/generator.cjs.development.js 15.6 kB 0 B
packages/generator/dist/generator.cjs.production.min.js 9.47 kB 0 B
packages/generator/dist/generator.esm.js 15.3 kB 0 B
packages/generator/dist/index.js 145 B 0 B
packages/generator/dist/templates/app/babel.config.js 77 B 0 B
packages/generator/dist/templates/app/blitz.config.js 324 B 0 B
packages/generator/dist/templates/app/jest.config.js 682 B 0 B
packages/generator/dist/templates/app/test/__mocks__/fileMock.js 54 B 0 B
packages/installer/dist/index.js 145 B 0 B
packages/installer/dist/installer.cjs.development.js 7.69 kB 0 B
packages/installer/dist/installer.cjs.production.min.js 5.14 kB 0 B
packages/installer/dist/installer.esm.js 7.54 kB 0 B
packages/repl/dist/index.js 141 B 0 B
packages/repl/dist/repl.cjs.development.js 1.81 kB 0 B
packages/repl/dist/repl.cjs.production.min.js 1.08 kB 0 B
packages/repl/dist/repl.esm.js 1.69 kB 0 B
packages/server/dist/index.js 142 B 0 B
packages/server/dist/server.cjs.development.js 22.2 kB 0 B
packages/server/dist/server.cjs.production.min.js 12.7 kB 0 B
packages/server/dist/server.esm.js 22.3 kB 0 B

</details>

<a href="https://github.com/preactjs/compressed-size-action"><sub>compressed-size-action</sub></a>

depfu[bot]

comment created time in a day

pull request commentblitz-js/blitz

Update tailwind to V2

@flybayer

I've put up a pull request to add @Mzaien! :tada:

Mzaien

comment created time in a day

PR opened blitz-js/blitz

Reviewers
docs: add Mzaien as a contributor

Adds @Mzaien as a contributor for code.

This was requested by flybayer in this comment

+11 -1

0 comment

2 changed files

pr created time in a day

push eventblitz-js/blitz

allcontributors[bot]

commit sha 311e179e06b73cbb247806223510fe72db733368

docs: update .all-contributorsrc [skip ci]

view details

push time in a day

push eventblitz-js/blitz

allcontributors[bot]

commit sha 499139289f84432b4640d82505eb9baab8fb662f

docs: update README.md [skip ci]

view details

push time in a day

create barnchblitz-js/blitz

branch : all-contributors/add-Mzaien

created branch time in a day

PR opened blitz-js/blitz

Reviewers
Upgrade @prisma/sdk: 2.10.0 → 2.12.0 (minor)

Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ @​prisma/sdk (2.10.0 → 2.12.0) · Repo

<details> <summary>Release Notes</summary> <h4><a href="https://github.com/prisma/prisma/releases/tag/2.12.0">2.12.0</a></h4>

<blockquote><p>Today, we are excited to share the <code>2.12.0</code> stable release <g-emoji class="g-emoji" alias="tada" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f389.png">🎉</g-emoji></p> <p><g-emoji class="g-emoji" alias="star2" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f31f.png">🌟</g-emoji> <strong>Help us spread the word about Prisma by starring the repo or <a href="https://twitter.com/intent/tweet?text=Check%20out%20the%20latest%20Prisma%20release%202.12.0%20%F0%9F%9A%80%0D%0A%0D%0Ahttps://github.com/prisma/prisma/releases/tag/2.12.0">tweeting</a> about the release.</strong></p> <h2>Major improvements</h2> <h3>Prisma codemods help upgrading your codebase</h3> <p>With today's release, we took the opportunity to cleanup some rough edges in the Prisma Client API which partially results in <em>breaking changes</em>. To help you with upgrading your codebase to <code>2.12.0</code>, we're introducing <a href="https://bounce.depfu.com/github.com/prisma/codemods"><code>@prisma/codemods</code></a>.</p> <p>The <code>@prisma/codemods</code> package provides a powerful CLI that scans your codebase and automatically updates the code to the new API calls from the provided version.</p> <p>The upgrade workflow looks like this:</p> <div class="highlight highlight-source-shell"><pre><span class="pl-c1">cd</span> my-app npm install @prisma/cli @prisma/client npx @prisma/codemods update-2.12 ./</pre></div> <h3>Microsoft SQL Server now supports native database types (Preview)</h3> <p>Hot off the presses: You can now use database native types with Microsoft SQL Server! You'll need to specify both <code>previewFeatures = ["microsoftSqlServer", "nativeTypes"]</code> to get started:</p> <div class="highlight highlight-source-js-jsx"><pre><span class="pl-smi">generator</span> <span class="pl-smi">js</span> { <span class="pl-smi">provider</span> <span class="pl-k">=</span> <span class="pl-s"><span class="pl-pds">"</span>prisma-client-js<span class="pl-pds">"</span></span> <span class="pl-smi">previewFeatures</span> <span class="pl-k">=</span> [<span class="pl-s"><span class="pl-pds">"</span>microsoftSqlServer<span class="pl-pds">"</span></span>, <span class="pl-s"><span class="pl-pds">"</span>nativeTypes<span class="pl-pds">"</span></span>] }

<span class="pl-smi">datasource</span> <span class="pl-smi">ms</span> { <span class="pl-smi">provider</span> <span class="pl-k">=</span> <span class="pl-s"><span class="pl-pds">"</span>sqlserver<span class="pl-pds">"</span></span> <span class="pl-smi">url</span> <span class="pl-k">=</span> <span class="pl-en">env</span>(<span class="pl-s"><span class="pl-pds">"</span>DATABASE_URL<span class="pl-pds">"</span></span>) }

<span class="pl-smi">model</span> <span class="pl-smi">User</span> { <span class="pl-smi">id</span> <span class="pl-smi">BigInt</span> @<span class="pl-ent">id</span> @<span class="pl-ent">default</span>(<span class="pl-en">autoincrement</span>()) @<span class="pl-ent">ms</span><span class="pl-k">.</span><span class="pl-smi">BigInt</span> <span class="pl-smi">name</span> <span class="pl-c1">String</span><span class="pl-k">?</span> @<span class="pl-ent">ms</span><span class="pl-k">.</span><span class="pl-en">VarChar</span>(<span class="pl-c1">255</span>) }

<span class="pl-smi">model</span> <span class="pl-smi">Post</span> { <span class="pl-smi">id</span> <span class="pl-smi">BigInt</span> @<span class="pl-ent">id</span> @<span class="pl-ent">default</span>(<span class="pl-en">autoincrement</span>()) @<span class="pl-ent">ms</span><span class="pl-k">.</span><span class="pl-smi">BigInt</span> <span class="pl-smi">title</span> <span class="pl-c1">String</span> @<span class="pl-ent">ms</span><span class="pl-k">.</span><span class="pl-en">VarChar</span>(<span class="pl-c1">100</span>) <span class="pl-smi">views</span> <span class="pl-smi">BigInt</span> @<span class="pl-ent">default</span>(<span class="pl-c1">0</span>) @<span class="pl-ent">ms</span><span class="pl-k">.</span><span class="pl-smi">BigInt</span> <span class="pl-smi">wordCount</span> <span class="pl-smi">Int</span> @<span class="pl-ent">default</span>(<span class="pl-c1">0</span>) @<span class="pl-ent">ms</span><span class="pl-k">.</span><span class="pl-smi">SmallInt</span> }</pre></div> <p>Note that Prisma Migrate does not yet work with Microsoft SQL Server, nor does Prisma Client Go.</p> <h3>Upcoming Prisma Migrate Preview Release</h3> <p>We’ve got a Preview release of Prisma Migrate nearing up with a large set of changes. You can test it in Early Access, see the upcoming changes, and provide feedback! Get started with the Early Access version <a href="http://pris.ly/migrate-early-access">here</a>.</p> <p>To join the conversation, join the <a href="https://app.slack.com/client/T0MQBS8JG/C01739JGFCM"><code>#product-feedback</code></a> channel on our <a href="https://slack.prisma.io">Slack</a>.</p> <h2>Breaking changes</h2> <p>As mentioned before, we're cleaning up the Prisma Client API which partially results in breaking changes. You can upgrade to the latest version using the new <code>@prisma/codemods</code> package as explained above.</p> <h3>Remove non-<code>$</code> methods</h3> <p>A few months back, we began prefixing our top-level Prisma methods with <code>$</code>. For example, <code>prisma.transaction</code> became <code>prisma.$transaction</code>. We did this to avoid clashes with your application's model names.</p> <p>The non-<code>$</code> methods were deprecated but continued to work until this release. In this release, we removed the deprecated methods.</p> <p>This means <strong>if you are still using calls like <code>prisma.transaction</code> or <code>prisma.disconnect</code> instead of <code>prisma.$transaction</code> or <code>prisma.$disconnect</code> in your code, your app is going to break after upgrading to <code>2.12.0</code></strong>.</p> <p>The <code>@prisma/codemods</code> workflow describe above will automatically fix any remaining non-$ methods in your codebase.</p> <p>You can read more about this change in on <a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/4206">Github</a>.</p> <h3>1-1-relations must now have an optional side</h3> <p>In this version, we're adding a new requirement for <a href="https://www.prisma.io/docs/concepts/components/prisma-schema/relations#one-to-one-relations">1-1-relations</a> that you define in your Prisma schema. In previous versions, it used to be allowed to have both sides of the relation <em>required</em>. As of this release, the <em>virtual</em> side of the relation (i.e. the side that does <em>not</em> store the foreign key in the underlying database) must be optional.</p> <p><strong>Before</strong></p> <div class="highlight highlight-source-prisma"><pre><span class="pl-s1"><span class="pl-k">model</span> <span class="pl-en">User</span> {</span> <span class="pl-s1"> <span class="pl-smi">id</span> <span class="pl-c1">Int</span> <span class="pl-s1"><span class="pl-en">@id</span></span> <span class="pl-s1"><span class="pl-en">@default</span>(<span class="pl-s1"><span class="pl-c1">autoincrement</span>()</span>)</span></span> <span class="pl-s1"> <span class="pl-smi">name</span> <span class="pl-c1">String</span><span class="pl-k">?</span></span> <span class="pl-s1"> <span class="pl-smi">profile</span> <span class="pl-c1">Profile</span> <span class="pl-c">// ❌ this is not allowed as of 2.12.0</span></span> <span class="pl-s1">}</span>

<span class="pl-s1"><span class="pl-k">model</span> <span class="pl-en">Profile</span> {</span> <span class="pl-s1"> <span class="pl-smi">id</span> <span class="pl-c1">Int</span> <span class="pl-s1"><span class="pl-en">@id</span></span> <span class="pl-s1"><span class="pl-en">@default</span>(<span class="pl-s1"><span class="pl-c1">autoincrement</span>()</span>)</span></span> <span class="pl-s1"> <span class="pl-smi">user</span> <span class="pl-c1">User</span> <span class="pl-s1"><span class="pl-en">@relation</span>(<span class="pl-v">fields</span>: <span class="pl-s1">[<span class="pl-c1">userId</span>]</span>, <span class="pl-v">references</span>: <span class="pl-s1">[<span class="pl-c1">id</span>]</span>)</span></span> <span class="pl-s1"> <span class="pl-smi">userId</span> <span class="pl-c1">Int</span></span> <span class="pl-s1">}</span></pre></div> <p><strong>After</strong></p> <div class="highlight highlight-source-prisma"><pre><span class="pl-s1"><span class="pl-k">model</span> <span class="pl-en">User</span> {</span> <span class="pl-s1"> <span class="pl-smi">id</span> <span class="pl-c1">Int</span> <span class="pl-s1"><span class="pl-en">@id</span></span> <span class="pl-s1"><span class="pl-en">@default</span>(<span class="pl-s1"><span class="pl-c1">autoincrement</span>()</span>)</span></span> <span class="pl-s1"> <span class="pl-smi">profile</span> <span class="pl-c1">Profile</span><span class="pl-k">?</span> <span class="pl-c">// ✅ the virtual side of the relation needs to be optional</span></span> <span class="pl-s1">}</span>

<span class="pl-s1"><span class="pl-k">model</span> <span class="pl-en">Profile</span> {</span> <span class="pl-s1"> <span class="pl-smi">id</span> <span class="pl-c1">Int</span> <span class="pl-s1"><span class="pl-en">@id</span></span> <span class="pl-s1"><span class="pl-en">@default</span>(<span class="pl-s1"><span class="pl-c1">autoincrement</span>()</span>)</span></span> <span class="pl-s1"> <span class="pl-smi">user</span> <span class="pl-c1">User</span> <span class="pl-s1"><span class="pl-en">@relation</span>(<span class="pl-v">fields</span>: <span class="pl-s1">[<span class="pl-c1">userId</span>]</span>, <span class="pl-v">references</span>: <span class="pl-s1">[<span class="pl-c1">id</span>]</span>)</span></span> <span class="pl-s1"> <span class="pl-smi">userId</span> <span class="pl-c1">Int</span></span> <span class="pl-s1">}</span></pre></div> <p>The easiest way to adjust your schema to these new requirements is by running the <code>introspect</code> command which will automatically make the virtual relation fields optional on 1-1-relations:</p> <pre><code>npx prisma introspect </code></pre> <h2>Fix how data for <code>Json[]</code> fields is stored</h2> <p>We fixed how the <code>Json[]</code> type is stored in <code>2.12.0</code>. Previously, we were storing JSON arrays as a string inside a your database's <code>JSON</code> column. Now, we properly encode JSON arrays as <code>JSON</code> in the database. This fix will allow us to add database native JSON operations down the line.</p> <p>If you are using the <code>Json[]</code> type in your schema, you'll need to migrate your data. We anticipate this breaking change will only affect a handful of folks. Please reach out to us in <a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/4346">this issue</a> and we'll help you with the migration.</p> <p>Here is an overview of how the behaviour changes in <code>2.12.0</code>:</p> <table role="table"> <thead> <tr> <th align="left">Given</th> <th align="left"><code>2.11.0</code></th> <th align="left"><code>2.12.0</code></th> </tr> </thead> <tbody> <tr> <td align="left"><code>[]</code></td> <td align="left"><code>[[]]</code></td> <td align="left"><code>[]</code></td> </tr> <tr> <td align="left"><code>[{test:"test"}]</code></td> <td align="left"><code>["{"test":"test"}"]</code></td> <td align="left"><code>[{"test":"test"}]</code></td> </tr> <tr> <td align="left"><code>[{ test: "test" }, { test: "test2" }]</code></td> <td align="left"><code>["[{"test": "test"}, {"test": "test2"}]"]</code></td> <td align="left"><code>[{"test": "test"},{"test": "test2"}]</code></td> </tr> <tr> <td align="left"><code>[3]</code></td> <td align="left"><code>3</code></td> <td align="left"><code>[3]</code></td> </tr> </tbody> </table> <h2>Deprecations</h2> <h3>Rename <code>findOne</code> to <code>findUnique</code> </h3> <p>This release renames <code>findOne</code> to <code>findUnique</code> and deprecates <code>findOne</code>.</p> <p>We made this change to reduce confusion. Many people expected <code>findOne</code> to be more loose, e.g: "Find the first record that matches my conditions.".</p> <p>The <code>@prisma/codemods</code> workflow describe above will automatically rename <code>findOne</code> to <code>findUnique</code> across your codebase.</p> <h3>Move most types under the <code>Prisma</code> namespace</h3> <p>We moved most of the generated types under a new <code>Prisma</code> namespace and are deprecating the top-level exports. This change also resolves some existing namespace clashes.</p> <p><strong>Before</strong></p> <div class="highlight highlight-source-ts"><pre><span class="pl-k">import</span> <span class="pl-kos">{</span> <span class="pl-smi">PrismaClient</span><span class="pl-kos">,</span> <span class="pl-smi">User</span><span class="pl-kos">,</span> <span class="pl-smi">UserCreateInput</span> <span class="pl-kos">}</span> <span class="pl-k">from</span> <span class="pl-s">'@prisma/client'</span>

<span class="pl-k">async</span> <span class="pl-k">function</span> <span class="pl-en">createUser</span><span class="pl-kos">(</span><span class="pl-s1">input</span>: <span class="pl-smi">UserCreateInput</span><span class="pl-kos">)</span>: <span class="pl-smi">Promise</span><span class="pl-kos"><</span><span class="pl-smi">User</span><span class="pl-kos">></span> <span class="pl-kos">{</span> <span class="pl-k">return</span> <span class="pl-s1">prisma</span><span class="pl-kos">.</span><span class="pl-c1">user</span><span class="pl-kos">.</span><span class="pl-en">create</span><span class="pl-kos">(</span><span class="pl-s1">input</span><span class="pl-kos">)</span> <span class="pl-kos">}</span></pre></div> <p><strong>After</strong></p> <div class="highlight highlight-source-ts"><pre><span class="pl-k">import</span> <span class="pl-kos">{</span> <span class="pl-smi">PrismaClient</span><span class="pl-kos">,</span> <span class="pl-smi">User</span><span class="pl-kos">,</span> <span class="pl-smi">Prisma</span> <span class="pl-kos">}</span> <span class="pl-k">from</span> <span class="pl-s">'@prisma/client'</span>

<span class="pl-k">async</span> <span class="pl-k">function</span> <span class="pl-en">createUser</span><span class="pl-kos">(</span><span class="pl-s1">input</span>: <span class="pl-smi">Prisma</span><span class="pl-kos">.</span><span class="pl-smi">UserCreateInput</span><span class="pl-kos">)</span>: <span class="pl-smi">Promise</span><span class="pl-kos"><</span><span class="pl-smi">User</span><span class="pl-kos">></span> <span class="pl-kos">{</span> <span class="pl-k">return</span> <span class="pl-s1">prisma</span><span class="pl-kos">.</span><span class="pl-c1">user</span><span class="pl-kos">.</span><span class="pl-en">create</span><span class="pl-kos">(</span><span class="pl-s1">input</span><span class="pl-kos">)</span> <span class="pl-kos">}</span></pre></div> <p>This means that with this release, there are exactly three kinds of exports in <code>@prisma/client</code>:</p> <ol> <li> <code>PrismaClient</code> is the constructor your Prisma Client instance</li> <li>Model types, e.g. <code>User</code> and <code>Post</code> </li> <li> <code>Prisma</code> as the new namespace under which you can now access the remaining generarted types</li> </ol> <p>The <code>@prisma/codemods</code> workflow describe above will automatically fix the type names in your code!</p> <p>With this change, we've greatly reduced the number of <em>reserved words</em> that could clash with your application's names. Go forth and add models with names like <code>Transaction</code> or <code>Aggregate</code>!</p> <h2>Fixes and improvements</h2> <h3><a href="https://bounce.depfu.com/github.com/prisma/prisma"><code>prisma</code></a></h3> <ul> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/3223">Remove GraphQL related reserved words</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/3290">Collect <code>dbgenerated()</code> values in an issue via "warning" output in Introspection</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/3603">Json arrays are not properly stored in underlying postgres jsonb array type </a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/3697">Replace <code>findOne</code> with <code>findUnique</code></a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/3747">Schema validator is not validating optionality of relations on both ends</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/3755">Use TypeScript namespaces to separate Prisma & Application types</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/3780">Gather example schemas for MS SQL Server</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/3887">Enable updating foreign keys in updateMany</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/3897">Json[] isn't working anymore</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/3985">Fields are ignored in WHERE clause</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/4053">Native Types Postgres: Creating a record with empty arrays for field types json[], jsonb[] not working</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/4150">Create codemod for namespace change</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/4205">Prisma2 blocks prisma generate on unsupported platforms, even when providing custom binaries</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/4206">Cleanup old non-$ methods</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/4213">Fix version pinning logic</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/4222">Warn, if more than <code>n</code> Prisma Client instances are instantiated</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/4300">Add codemod for $ deprecation</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/4332">SQL Server raw queries panic when having multiple result sets</a></li> </ul> <h3><a href="https://bounce.depfu.com/github.com/prisma/prisma-client-js"><code>prisma-client-js</code></a></h3> <ul> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma-client-js/issues/312">Improve debug output of array values</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma-client-js/issues/585">[Javascript] Better error message than <code>TypeError: Cannot read property 'findMany' of undefined</code> for non existing model?</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma-client-js/issues/811">Remove Aggregate as reserved word</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma-client-js/issues/837">Test and stabilize Unix Domain Sockets</a></li> </ul> <h3><a href="https://bounce.depfu.com/github.com/prisma/migrate"><code>migrate</code></a></h3> <ul> <li><a href="https://bounce.depfu.com/github.com/prisma/migrate/issues/418">ERROR: there is no unique constraint matching given keys for referenced table "User"</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/migrate/issues/472">Suggest using <code>name</code> on index when creation fails because of length</a></li> </ul> <h3><a href="https://bounce.depfu.com/github.com/prisma/language-tools"><code>language-tools</code></a></h3> <ul> <li><a href="https://bounce.depfu.com/github.com/prisma/language-tools/issues/41">Display relation fields differently than scalar fields</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/language-tools/issues/522">Warn about provider array deprecation in the VSCode plugin</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/language-tools/issues/627">Improve logging of language server</a></li> </ul> <h3><a href="https://bounce.depfu.com/github.com/prisma/studio"><code>studio</code></a></h3> <ul> <li><a href="https://bounce.depfu.com/github.com/prisma/studio/issues/578">When saving changes to the database, do it one transaction</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/studio/issues/579">Studio server does not resolve environment variables correctly</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/studio/issues/580">Focus first cell of a newly created record</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/studio/issues/581">When you start typing in a number cell directly, it is considered an invalid change</a></li> </ul> <h3><a href="https://bounce.depfu.com/github.com/prisma/prisma-engines"><code>prisma-engines</code></a></h3> <ul> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma-engines/issues/1173">Send the "server listening" message only after the server has started</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma-engines/issues/1183">Supporting native types on SQL Server</a></li> </ul> <h2>Credits</h2> <p>Huge thanks to <a href="https://bounce.depfu.com/github.com/matt-eric">@matt-eric</a>, <a href="https://bounce.depfu.com/github.com/muxahuk">@muxahuk</a> for helping!</p></blockquote> <h4><a href="https://github.com/prisma/prisma/releases/tag/2.11.0">2.11.0</a></h4>

<blockquote><p>Today, we are excited to share the <code>2.11.0</code> stable release <g-emoji class="g-emoji" alias="tada" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f389.png">🎉</g-emoji></p> <p><g-emoji class="g-emoji" alias="star2" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f31f.png">🌟</g-emoji> <strong>Help us spread the word about Prisma by starring the repo <g-emoji class="g-emoji" alias="point_up" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/261d.png">☝️</g-emoji> or <a href="https://twitter.com/intent/tweet?text=Check%20out%20the%20latest%20Prisma%20release%202.11.0%20%F0%9F%9A%80%0D%0A%0D%0Ahttps://github.com/prisma/prisma/releases/tag/2.11.0">tweeting</a> about the release.</strong></p> <h2>Major Improvements</h2> <h3>Native database types in the Prisma schema (Preview)</h3> <p>We are super excited to share that this release brings you one of the most requested features since we released the initial version of Prisma: The representation of native database types in the Prisma schema.</p> <p>Up to this release, the Prisma schema only allowed to represent a limited set of types: <code>String</code>, <code>Int</code>, <code>Float</code>, <code>Boolean</code>, <code>DateTime</code>, <code>Json</code>. Each of these types has a <em>default mapping</em> to an underlying database type that's specified for each connector (see the mappings for <a href="https://www.prisma.io/docs/reference/database-connectors/postgresql#type-mapping-between-postgresql-to-prisma-schema">PostgreSQL</a> and <a href="https://www.prisma.io/docs/reference/database-connectors/mysql#type-mapping-between-mysql-to-prisma-schema">MySQL</a>).</p> <p>With this release, you can now add an attribute to a field definition in order to determine which <em>specific</em> database type it should be mapped to. Here is an example for a PostgreSQL database that specifies the underlying database types more specifically. Note that you also need to enable the feature via the the <code>nativeTypes</code> feature flag:</p> <div class="highlight highlight-source-prisma"><pre><span class="pl-s1"><span class="pl-k">generator</span> <span class="pl-en">client</span> {</span> <span class="pl-s1"> <span class="pl-smi">provider</span> <span class="pl-k">=</span> <span class="pl-s">"</span><span class="pl-s">prisma-client-js</span><span class="pl-s">"</span></span> <span class="pl-s1"> <span class="pl-smi">previewFeatures</span> <span class="pl-k">=</span> <span class="pl-s1">[<span class="pl-s">"</span><span class="pl-s">nativeTypes</span><span class="pl-s">"</span>]</span></span> <span class="pl-s1">}</span>

<span class="pl-s1"><span class="pl-k">datasource</span> <span class="pl-en">db</span> {</span> <span class="pl-s1"> <span class="pl-smi">provider</span> <span class="pl-k">=</span> <span class="pl-s">"</span><span class="pl-s">postgresql</span><span class="pl-s">"</span></span> <span class="pl-s1"> <span class="pl-smi">url</span> <span class="pl-k">=</span> <span class="pl-s1"><span class="pl-c1">env</span>(<span class="pl-s">"</span><span class="pl-s">DATABASE_URL</span><span class="pl-s">"</span>)</span></span> <span class="pl-s1">}</span>

<span class="pl-s1"><span class="pl-k">model</span> <span class="pl-en">User</span> {</span> <span class="pl-s1"> <span class="pl-smi">id</span> <span class="pl-c1">Int</span> <span class="pl-s1"><span class="pl-en">@id</span></span> <span class="pl-s1"><span class="pl-en">@default</span>(<span class="pl-s1"><span class="pl-c1">autoincrement</span>()</span>)</span> </span> <span class="pl-s1"> <span class="pl-smi">name</span> <span class="pl-c1">String</span><span class="pl-k">?</span> <span class="pl-s1"><span class="pl-en">@db.VarChar</span>(<span class="pl-c1">255</span>)</span></span> <span class="pl-s1">}</span>

<span class="pl-s1"><span class="pl-k">model</span> <span class="pl-en">Post</span> {</span> <span class="pl-s1"> <span class="pl-smi">id</span> <span class="pl-c1">Int</span> <span class="pl-s1"><span class="pl-en">@id</span></span> <span class="pl-s1"><span class="pl-en">@default</span>(<span class="pl-s1"><span class="pl-c1">autoincrement</span>()</span>)</span> </span> <span class="pl-s1"> <span class="pl-smi">title</span> <span class="pl-c1">String</span> <span class="pl-s1"><span class="pl-en">@db.VarChar</span>(<span class="pl-c1">100</span>)</span></span> <span class="pl-s1"> <span class="pl-smi">createdAt</span> <span class="pl-c1">DateTime</span> <span class="pl-s1"><span class="pl-en">@db.Timestamp</span>(<span class="pl-c1">6</span>)</span></span> <span class="pl-s1"> <span class="pl-smi">wordCount</span> <span class="pl-c1">Int</span> <span class="pl-s1"><span class="pl-en">@db.SmallInt</span></span></span> <span class="pl-s1">}</span></pre></div> <p>In the above code snippet, all fields of the two Prisma models are annotated with attributes to diverge from the default mapping and determine the exact type that is used in the underlying database. For example, the <code>id</code> fields are represented as <code>db.BigInt</code> which maps to the <code>BIGINT</code> PostgreSQL type. You can find out more about which Prisma types can be annotated with which native type attributes in the docs for the <a href="https://www.prisma.io/docs/reference/database-connectors/postgresql#type-mapping-between-postgresql-to-prisma-schema">PostgreSQL</a> and <a href="https://www.prisma.io/docs/reference/database-connectors/mysql#type-mapping-between-mysql-to-prisma-schema">MySQL</a> connectors.</p> <p>Please <a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/4045">share your feedback</a> on how this feature works for you. We are interested in both positive and negative feedback, so we know if this feature is already ready for production! (If encounter any problems, please open a new issue <a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/new/choose">here</a>).</p> <p><g-emoji class="g-emoji" alias="books" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f4da.png">📚</g-emoji> <strong>Documentation</strong>: <a href="https://www.prisma.io/docs/concepts/components/preview-features/native-types">Extended native type support</a></p> <h3>New types in the Prisma schema: <code>BigInt</code>, <code>Bytes</code> and <code>Decimal</code> (Preview)</h3> <p>With this release, we are further introducing three new <em>scalar types</em> in the Prisma schema: <code>BigInt</code>, <code>Bytes</code> and <code>Decimal</code>. Here is an overview for how they map to the different databases that are supported by Prisma and how they're represented when queried with Prisma Client JS:</p> <table role="table"> <thead> <tr> <th>Prisma</th> <th>PostgreSQL</th> <th>MySQL</th> <th>SQLite</th> <th>JavaScript / TypeScript</th> </tr> </thead> <tbody> <tr> <td><code>Bytes</code></td> <td><code>BYTEA</code></td> <td><code>LONGBLOB</code></td> <td>n/a</td> <td><code>Buffer</code></td> </tr> <tr> <td><code>Decimal</code></td> <td><code>DECIMAL(65,30)</code></td> <td><code>DECIMAL(65,30)</code></td> <td>n/a</td> <td><a href="https://bounce.depfu.com/github.com/MikeMcl/decimal.js/">Decimal.js</a></td> </tr> <tr> <td><code>BigInt</code></td> <td><code>BIGINT</code></td> <td><code>BIGINT</code></td> <td>n/a</td> <td><code>BigInt</code></td> </tr> </tbody> </table> <p>To make use of these new types, you need to enable the <code>nativeTypes</code> feature flag in your Prisma schema:</p> <div class="highlight highlight-source-diff"><pre>generator client { provider = "prisma-client-js" <span class="pl-mi1"><span class="pl-mi1">+</span> previewFeatures = ["nativeTypes"]</span> }</pre></div> <p>Once you added the feature flag, be sure to run <code>prisma generate</code> again to update your local version of Prisma Client.</p> <p><g-emoji class="g-emoji" alias="books" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f4da.png">📚</g-emoji> <strong>Documentation</strong>: <a href="https://www.prisma.io/docs/concepts/components/preview-features/native-types/native-types-mappings">Prisma types in the <code>nativeTypes</code> preview</a></p> <h3>Set foreign keys directly (Preview)</h3> <p>We now support writing foreign keys (also known as <a href="https://www.prisma.io/docs/concepts/components/prisma-schema/relations#annotated-relation-fields-and-relation-scalar-fields">relation scalars</a>) directly with the <code>uncheckedScalarInputs</code> preview feature.</p> <p>Consider this sample Prisma schema:</p> <div class="highlight highlight-source-prisma"><pre><span class="pl-s1"><span class="pl-k">generator</span> <span class="pl-en">client</span> {</span> <span class="pl-s1"> <span class="pl-smi">provider</span> <span class="pl-k">=</span> <span class="pl-s">"</span><span class="pl-s">prisma-client-js</span><span class="pl-s">"</span></span> <span class="pl-s1"> <span class="pl-smi">previewFeatures</span> <span class="pl-k">=</span> <span class="pl-s1">[<span class="pl-s">"</span><span class="pl-s">uncheckedScalarInputs</span><span class="pl-s">"</span>]</span></span> <span class="pl-s1">}</span>

<span class="pl-s1"><span class="pl-k">model</span> <span class="pl-en">User</span> {</span> <span class="pl-s1"> <span class="pl-smi">id</span> <span class="pl-c1">Int</span> <span class="pl-s1"><span class="pl-en">@id</span></span> <span class="pl-s1"><span class="pl-en">@default</span>(<span class="pl-s1"><span class="pl-c1">autoincrement</span>()</span>)</span></span> <span class="pl-s1"> <span class="pl-smi">posts</span> <span class="pl-c1">Post</span><span class="pl-k">[]</span></span> <span class="pl-s1">}</span>

<span class="pl-s1"><span class="pl-k">model</span> <span class="pl-en">Post</span> {</span> <span class="pl-s1"> <span class="pl-smi">id</span> <span class="pl-c1">Int</span> <span class="pl-s1"><span class="pl-en">@id</span></span> <span class="pl-s1"><span class="pl-en">@default</span>(<span class="pl-s1"><span class="pl-c1">autoincrement</span>()</span>)</span></span> <span class="pl-s1"> <span class="pl-smi">authorId</span> <span class="pl-c1">Int</span></span> <span class="pl-s1"> <span class="pl-smi">author</span> <span class="pl-c1">User</span> <span class="pl-s1"><span class="pl-en">@relation</span>(<span class="pl-v">fields</span>: <span class="pl-s1">[<span class="pl-c1">authorId</span>]</span>, <span class="pl-v">references</span>: <span class="pl-s1">[<span class="pl-c1">id</span>]</span>)</span></span> <span class="pl-s1">}</span></pre></div> <p>Instead of using <code>connect</code> when creating a new <code>Post</code> record to wire up a relation with a <code>User</code> record, you can now directly set the <code>authorId</code> value:</p> <div class="highlight highlight-source-ts"><pre><span class="pl-k">await</span> <span class="pl-s1">prisma</span><span class="pl-kos">.</span><span class="pl-c1">post</span><span class="pl-kos">.</span><span class="pl-en">create</span><span class="pl-kos">(</span><span class="pl-kos">{</span> <span class="pl-c1">data</span>: <span class="pl-kos">{</span> <span class="pl-c">// You can now set the foreign key directly...</span> <span class="pl-c1">authorId</span>: <span class="pl-c1">1</span><span class="pl-kos">,</span> <span class="pl-c">// ... or connect the relationship...</span> <span class="pl-c">// author: {</span> <span class="pl-c">// connect: {</span> <span class="pl-c">// id: 1</span> <span class="pl-c">// }</span> <span class="pl-c">// }</span> <span class="pl-c">// ... but not both at the same time</span> <span class="pl-kos">}</span><span class="pl-kos">,</span> <span class="pl-kos">}</span><span class="pl-kos">)</span><span class="pl-kos">;</span></pre></div> <p>We'd love for you to give it a try. You can give us feedback in <a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/4209">this issue</a>.</p> <h3>The <code>$transaction</code> API is now stable</h3> <p>You can now use <a href="https://www.prisma.io/docs/concepts/components/prisma-client/transactions#the-transaction-api"><code>$transaction</code></a> API without the <code>transactionApi</code> feature flag.</p> <div class="highlight highlight-source-diff"><pre>generator client { provider = "prisma-client-js" <span class="pl-md"><span class="pl-md">-</span> previewFeatures = ["transactionApi"]</span> }</pre></div> <h3>The <code>connectOrCreate</code> API is now stable</h3> <p>The <a href="https://www.prisma.io/docs/concepts/components/prisma-client/relation-queries#nested-writes"><code>connectOrCreate</code></a> API offers a convenient way to link or insert nested records.</p> <p>You can now use it without the <code>connectOrCreate</code> feature flag.</p> <div class="highlight highlight-source-diff"><pre>generator client { provider = "prisma-client-js" <span class="pl-md"><span class="pl-md">-</span> previewFeatures = ["connectOrCreate"]</span> }</pre></div> <h3>Middleware model parameter is now typed</h3> <p>This is a small quality-of-life improvement for developers using the Prisma <a href="https://www.prisma.io/docs/concepts/components/prisma-client/middleware">middleware</a>. The <code>params.model</code> parameter that's passed into a middleware function is now typed to your model so you can now reliably tie middleware to models:</p> <div class="highlight highlight-source-ts"><pre><span class="pl-s1">prisma</span><span class="pl-kos">.</span><span class="pl-en">$use</span><span class="pl-kos">(</span><span class="pl-k">async</span> <span class="pl-kos">(</span><span class="pl-s1">params</span><span class="pl-kos">,</span> <span class="pl-s1">next</span><span class="pl-kos">)</span> <span class="pl-c1">=></span> <span class="pl-kos">{</span> <span class="pl-k">switch</span> <span class="pl-kos">(</span><span class="pl-s1">params</span><span class="pl-kos">.</span><span class="pl-c1">model</span><span class="pl-kos">)</span> <span class="pl-kos">{</span> <span class="pl-k">case</span> <span class="pl-s">'user'</span>: <span class="pl-c">// ...</span> <span class="pl-k">case</span> 'project: <span class="pl-c">// ...</span> <span class="pl-kos">}</span> <span class="pl-kos">}</span><span class="pl-kos">)</span></pre></div> <p>If you need the old behavior you can cast <code>params.model</code> back to a <code>string</code> by wrapping it <code>String(params.model)</code>.</p> <p><g-emoji class="g-emoji" alias="books" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f4da.png">📚</g-emoji> <strong>Documentation</strong>: <a href="https://www.prisma.io/docs/concepts/components/prisma-client/middleware">Middleware</a></p> <h3>Deprecation of multi-provider array</h3> <p>You will now see a warning if you have multiple providers in your <code>datasource</code>. We recently realized that supporting an array of providers in the Prisma schema was premature, adding complexity in the process of improving the product, and causing some confusion about our intent.</p> <p>You can read more about the decision and what to do about it in <a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/3834">this issue</a>.</p> <h3>Validate <code>PrismaClient</code> inputs at runtime</h3> <p>We now validate the <code>parameters</code> we accept in <code>new PrismaClient(parameters)</code>. This is unlikely to affect you unless you were passing invalid parameters into <code>PrismaClient</code> before.</p> <h2>Prisma Client Go is now Early Access <g-emoji class="g-emoji" alias="tada" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f389.png">🎉</g-emoji> </h2> <p>We're happy to announce that <a href="https://bounce.depfu.com/github.com/prisma/prisma-client-go">Prisma Client Go</a> has graduated from experimental to <a href="https://www.prisma.io/docs/about/releases#early-access">Early Access</a>.</p> <p>You can <a href="https://bounce.depfu.com/github.com/prisma/prisma-client-go/blob/master/docs/quickstart.md">get started here</a>. We'd love to learn more about how you use the Go Client during Early Access. You can schedule a <a href="https://calendly.com/c/DDAUQECG7NYIBU5Q">call with us</a> or <a href="https://slack.prisma.io/">chat with us on Slack</a> in the #prisma-client-go channel. We're looking forward to hearing from you!</p> <h2> <g-emoji class="g-emoji" alias="tv" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f4fa.png">📺</g-emoji> Join us for another "What's new in Prisma" livestream</h2> <p>Learn about the latest release and other news from the Prisma community by joining us for another <a href="https://www.youtube.com/watch?v=XFCGpwcVUCY&ab_channel=Prisma">"What's new in Prisma"</a> livestream.</p> <p>The stream takes place <a href="https://www.youtube.com/watch?v=XFCGpwcVUCY&ab_channel=Prisma">on Youtube</a> on <strong>Thursday, November 12</strong> at <strong>5pm Berlin | 8am San Francisco</strong>.</p> <h2> <g-emoji class="g-emoji" alias="eyes" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f440.png">👀</g-emoji> Make your online talk recordings more accessible with subtitles</h2> <p>We'd love to help you make your talk recordings (no matter if Meetup or conference talk) more accessible by <a href="https://twitter.com/prisma/status/1325744486425780224">adding subtitles</a> to it <strong>for free</strong>! Reach out to <a href="sponsorships@prisma.io">sponsorships@prisma.io</a> if you are interested in getting subtitles for your videos!</p> <h2>Fixes and improvements</h2> <h3><a href="https://bounce.depfu.com/github.com/prisma/prisma"><code>prisma</code></a></h3> <ul> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/2152">Can't create a record with only the foreign key to another table</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/3081">Foreign key field is not being set when using a nested create for a one-to-one relation</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/3517">Prisma Client is unable to fetch DateTime lists</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/3545">Middleware params model should be an enum or union of strings.</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/3571">vercel/pkg broken on windows</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/3572">vercel/pkg errors on windows</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/3708">Introspection fails instantly MariaDB</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/3750">DATABASE_URL verification still attempted when datasource override provided in PrismaClient constructor</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/3802">Introspection should try to preserve custom Enum names on MySQL even without @map</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/3805">Mutliple 1-n self relations break migrations</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/3892">.transaction([]) fails with Request Timeout Error on large dataset</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/3918">JSON value truncate floating numbers</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/3923">Postgresql: Large double precision float values cause panic</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/3945">Error in prisma results in unhandled promise rejection</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/3989">Consolidate Undici error handling</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/3994">Internal: update our <code>pnpm</code> version used for development and CI</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/4000">Internal: Create new milestone check GitHub Action</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/4011">Prisma and Netlify, binary is not downloaded automatically since 2.8.0</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/4035">Detect and enforce Node Version in <code>preinstall</code> hook so pnpm fails clearly</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/4048">Package name reuse (.prisma/client) when generating multiple prisma clients causes issues with some other libraries (e.g. jest)</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/4050">Native Types: @db.BigInt should be BigInt</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/4064">Prisma generate or introspect don't work when nativeTypes preview is enabled</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/4082">Cannot update a model with composite keys through a referenced model</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/4083">RangeError: Invalid count value during create</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/4096">Prisma Client doesn't load root .env</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/4098">You are trying to load env variables which are already present in your project root .env</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/4125">Stabilize connectOrCreate</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/4126">Stabilize transactionApi</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/4144">Add integration test to trigger env var warning in Prisma Client</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/4186">Improve error when using prisma migrate --experimental with native types</a></li> </ul> <h3><a href="https://bounce.depfu.com/github.com/prisma/prisma-client-js"><code>prisma-client-js</code></a></h3> <ul> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma-client-js/issues/889">Runtime validation for Prisma client constructor parameters</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma-client-js/issues/894">$transaction spread operator</a></li> </ul> <h3><a href="https://bounce.depfu.com/github.com/prisma/language-tools"><code>language-tools</code></a></h3> <ul> <li><a href="https://bounce.depfu.com/github.com/prisma/language-tools/issues/158">Add Prisma icon to standard icon theme in VSCode</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/language-tools/issues/424">Gitpod Support</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/language-tools/issues/602">prisma.plugin.nextjs.addTypesOnSave broken</a></li> </ul> <h3><a href="https://bounce.depfu.com/github.com/prisma/studio"><code>studio</code></a></h3> <ul> <li><a href="https://bounce.depfu.com/github.com/prisma/studio/issues/529">Unable to view / edit DateTime lists</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/studio/issues/561">Case insensitive searching</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/studio/issues/563">npx prisma studio doesn't work on WSL 1</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/studio/issues/571">Cannot type "." in a float column</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/studio/issues/572">Websockets fails when studio is behind a reverse proxy</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/studio/issues/576">[design] Cell overflow</a></li> </ul> <h3><a href="https://bounce.depfu.com/github.com/prisma/prisma-engines"><code>prisma-engines</code></a></h3> <ul> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma-engines/issues/1284">Introduce support for scalar type <code>BigInt</code></a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma-engines/issues/1291">Native Type Precisions</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma-engines/issues/1317">Remove Scalar Type <code>Duration</code></a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma-engines/issues/1318">Feature gate scalar types <code>Decimal</code> and <code>Bytes</code></a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma-engines/issues/1323">Remove TimestampWithTimeZone, TimeWithTimeZone and Intervall</a></li> </ul></blockquote> <h4><a href="https://github.com/prisma/prisma/releases/tag/2.10.2">2.10.2</a></h4>

<blockquote><p>Today, we are issuing the <code>2.10.2</code> patch release.</p> <h2>Fixes</h2> <h3>Client</h3> <ul> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/4098">You are trying to load env variables which are already present in your project root .env #4098</a></li> </ul> <h3>Language Tools</h3> <ul> <li><a href="https://bounce.depfu.com/github.com/prisma/language-tools/issues/605">Prisma vscode extension is autoformating typescript react code on save #605</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/language-tools/issues/606">Npm throws error on build creation while Prisma extension is enabled #606</a></li> </ul></blockquote> <h4><a href="https://github.com/prisma/prisma/releases/tag/2.10.1">2.10.1</a></h4>

<blockquote><p>Today, we are issuing the <code>2.10.1</code> patch release.</p> <h2>Fixes</h2> <h3>CLI</h3> <ul> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/4097">@prisma/engines are not used by CLI #4097</a></li> </ul> <h3>Client</h3> <ul> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/4096">Prisma Client doesn't load root .env #4096</a></li> </ul> <h3>Migrate</h3> <ul> <li><a href="https://bounce.depfu.com/github.com/prisma/migrate/issues/626">Prisma Migrate Crash on change required foreign key to not-required #626</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/migrate/issues/627">v2.10.0 #627</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/migrate/issues/625">crashed after the first migration #625</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/migrate/issues/623">Error in migration engine. #623</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/migrate/issues/621">Migration issue on changing userId field to unique. related to #619 #621</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/migrate/issues/619">Migration crashed with code #619</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/migrate/issues/618">Crash Report #618</a></li> </ul> <h3>Language Tools</h3> <ul> <li><a href="https://bounce.depfu.com/github.com/prisma/language-tools/pull/603">prisma.plugin.nextjs.addTypesOnSave broken #602</a></li> </ul></blockquote> <p><em>Does any of this look wrong? <a href="https://depfu.com/packages/npm/@prisma%2Fsdk/feedback">Please let us know.</a></em></p> </details>

<details> <summary>Commits</summary> <p><a href="https://github.com/prisma/prisma/compare/139ad870db512c26b331d812fa38a2174b85dff8...1cb154de53598bf1e7c438293f4babffe81fbf8a">See the full diff on Github</a>. The new version differs by more commits than we can show here.</p> </details>

✳️ jest (24.9.0 → 26.5.3) · Repo · Changelog

<details> <summary>Release Notes</summary> <p><em>Too many releases to show here. View the <a href="https://github.com/facebook/jest/blob/master/CHANGELOG.md">full release notes</a>.</em></p> </details>

<details> <summary>Commits</summary> <p><a href="https://github.com/facebook/jest/compare/3cdbd556948b4974b2cc23178977eb159d343df8...71152afbbda76fd09ddb2527b54c365d753f42aa">See the full diff on Github</a>. The new version differs by more commits than we can show here.</p> </details>

✳️ ts-jest (24.3.0 → 26.4.1) · Repo · Changelog

<details> <summary>Release Notes</summary> <p><em>Too many releases to show here. View the <a href="https://github.com/kulshekhar/ts-jest/blob/master/CHANGELOG.md">full release notes</a>.</em></p> </details>

<details> <summary>Commits</summary> <p><a href="https://github.com/kulshekhar/ts-jest/compare/51f8f826eca9072ba70fd8c5998392381f3a5721...2caeaf4747cc0b61ac503b9b50b08221b261075b">See the full diff on Github</a>. The new version differs by more commits than we can show here.</p> </details>


Depfu Status

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

<details><summary>All Depfu comment commands</summary> <blockquote><dl> <dt>@​depfu rebase</dt><dd>Rebases against your default branch and redoes this update</dd> <dt>@​depfu recreate</dt><dd>Recreates this PR, overwriting any edits that you've made to it</dd> <dt>@​depfu merge</dt><dd>Merges this PR once your tests are passing and conflicts are resolved</dd> <dt>@​depfu close</dt><dd>Closes this PR and deletes the branch</dd> <dt>@​depfu reopen</dt><dd>Restores the branch and reopens this PR (if it's closed)</dd> <dt>@​depfu pause</dt><dd>Ignores all future updates for this dependency and closes this PR</dd> <dt>@​depfu pause [minor|major]</dt><dd>Ignores all future minor/major updates for this dependency and closes this PR</dd> <dt>@​depfu resume</dt><dd>Future versions of this dependency will create PRs again (leaves this PR as is)</dd> </dl></blockquote> </details>

+970 -61

0 comment

2 changed files

pr created time in a day

PR opened blitz-js/blitz

Reviewers
Upgrade @prisma/cli: 2.10.0 → 2.12.0 (minor)

Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ @​prisma/cli (2.10.0 → 2.12.0) · Repo

<details> <summary>Release Notes</summary> <h4><a href="https://github.com/prisma/prisma/releases/tag/2.12.0">2.12.0</a></h4>

<blockquote><p>Today, we are excited to share the <code>2.12.0</code> stable release <g-emoji class="g-emoji" alias="tada" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f389.png">🎉</g-emoji></p> <p><g-emoji class="g-emoji" alias="star2" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f31f.png">🌟</g-emoji> <strong>Help us spread the word about Prisma by starring the repo or <a href="https://twitter.com/intent/tweet?text=Check%20out%20the%20latest%20Prisma%20release%202.12.0%20%F0%9F%9A%80%0D%0A%0D%0Ahttps://github.com/prisma/prisma/releases/tag/2.12.0">tweeting</a> about the release.</strong></p> <h2>Major improvements</h2> <h3>Prisma codemods help upgrading your codebase</h3> <p>With today's release, we took the opportunity to cleanup some rough edges in the Prisma Client API which partially results in <em>breaking changes</em>. To help you with upgrading your codebase to <code>2.12.0</code>, we're introducing <a href="https://bounce.depfu.com/github.com/prisma/codemods"><code>@prisma/codemods</code></a>.</p> <p>The <code>@prisma/codemods</code> package provides a powerful CLI that scans your codebase and automatically updates the code to the new API calls from the provided version.</p> <p>The upgrade workflow looks like this:</p> <div class="highlight highlight-source-shell"><pre><span class="pl-c1">cd</span> my-app npm install @prisma/cli @prisma/client npx @prisma/codemods update-2.12 ./</pre></div> <h3>Microsoft SQL Server now supports native database types (Preview)</h3> <p>Hot off the presses: You can now use database native types with Microsoft SQL Server! You'll need to specify both <code>previewFeatures = ["microsoftSqlServer", "nativeTypes"]</code> to get started:</p> <div class="highlight highlight-source-js-jsx"><pre><span class="pl-smi">generator</span> <span class="pl-smi">js</span> { <span class="pl-smi">provider</span> <span class="pl-k">=</span> <span class="pl-s"><span class="pl-pds">"</span>prisma-client-js<span class="pl-pds">"</span></span> <span class="pl-smi">previewFeatures</span> <span class="pl-k">=</span> [<span class="pl-s"><span class="pl-pds">"</span>microsoftSqlServer<span class="pl-pds">"</span></span>, <span class="pl-s"><span class="pl-pds">"</span>nativeTypes<span class="pl-pds">"</span></span>] }

<span class="pl-smi">datasource</span> <span class="pl-smi">ms</span> { <span class="pl-smi">provider</span> <span class="pl-k">=</span> <span class="pl-s"><span class="pl-pds">"</span>sqlserver<span class="pl-pds">"</span></span> <span class="pl-smi">url</span> <span class="pl-k">=</span> <span class="pl-en">env</span>(<span class="pl-s"><span class="pl-pds">"</span>DATABASE_URL<span class="pl-pds">"</span></span>) }

<span class="pl-smi">model</span> <span class="pl-smi">User</span> { <span class="pl-smi">id</span> <span class="pl-smi">BigInt</span> @<span class="pl-ent">id</span> @<span class="pl-ent">default</span>(<span class="pl-en">autoincrement</span>()) @<span class="pl-ent">ms</span><span class="pl-k">.</span><span class="pl-smi">BigInt</span> <span class="pl-smi">name</span> <span class="pl-c1">String</span><span class="pl-k">?</span> @<span class="pl-ent">ms</span><span class="pl-k">.</span><span class="pl-en">VarChar</span>(<span class="pl-c1">255</span>) }

<span class="pl-smi">model</span> <span class="pl-smi">Post</span> { <span class="pl-smi">id</span> <span class="pl-smi">BigInt</span> @<span class="pl-ent">id</span> @<span class="pl-ent">default</span>(<span class="pl-en">autoincrement</span>()) @<span class="pl-ent">ms</span><span class="pl-k">.</span><span class="pl-smi">BigInt</span> <span class="pl-smi">title</span> <span class="pl-c1">String</span> @<span class="pl-ent">ms</span><span class="pl-k">.</span><span class="pl-en">VarChar</span>(<span class="pl-c1">100</span>) <span class="pl-smi">views</span> <span class="pl-smi">BigInt</span> @<span class="pl-ent">default</span>(<span class="pl-c1">0</span>) @<span class="pl-ent">ms</span><span class="pl-k">.</span><span class="pl-smi">BigInt</span> <span class="pl-smi">wordCount</span> <span class="pl-smi">Int</span> @<span class="pl-ent">default</span>(<span class="pl-c1">0</span>) @<span class="pl-ent">ms</span><span class="pl-k">.</span><span class="pl-smi">SmallInt</span> }</pre></div> <p>Note that Prisma Migrate does not yet work with Microsoft SQL Server, nor does Prisma Client Go.</p> <h3>Upcoming Prisma Migrate Preview Release</h3> <p>We’ve got a Preview release of Prisma Migrate nearing up with a large set of changes. You can test it in Early Access, see the upcoming changes, and provide feedback! Get started with the Early Access version <a href="http://pris.ly/migrate-early-access">here</a>.</p> <p>To join the conversation, join the <a href="https://app.slack.com/client/T0MQBS8JG/C01739JGFCM"><code>#product-feedback</code></a> channel on our <a href="https://slack.prisma.io">Slack</a>.</p> <h2>Breaking changes</h2> <p>As mentioned before, we're cleaning up the Prisma Client API which partially results in breaking changes. You can upgrade to the latest version using the new <code>@prisma/codemods</code> package as explained above.</p> <h3>Remove non-<code>$</code> methods</h3> <p>A few months back, we began prefixing our top-level Prisma methods with <code>$</code>. For example, <code>prisma.transaction</code> became <code>prisma.$transaction</code>. We did this to avoid clashes with your application's model names.</p> <p>The non-<code>$</code> methods were deprecated but continued to work until this release. In this release, we removed the deprecated methods.</p> <p>This means <strong>if you are still using calls like <code>prisma.transaction</code> or <code>prisma.disconnect</code> instead of <code>prisma.$transaction</code> or <code>prisma.$disconnect</code> in your code, your app is going to break after upgrading to <code>2.12.0</code></strong>.</p> <p>The <code>@prisma/codemods</code> workflow describe above will automatically fix any remaining non-$ methods in your codebase.</p> <p>You can read more about this change in on <a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/4206">Github</a>.</p> <h3>1-1-relations must now have an optional side</h3> <p>In this version, we're adding a new requirement for <a href="https://www.prisma.io/docs/concepts/components/prisma-schema/relations#one-to-one-relations">1-1-relations</a> that you define in your Prisma schema. In previous versions, it used to be allowed to have both sides of the relation <em>required</em>. As of this release, the <em>virtual</em> side of the relation (i.e. the side that does <em>not</em> store the foreign key in the underlying database) must be optional.</p> <p><strong>Before</strong></p> <div class="highlight highlight-source-prisma"><pre><span class="pl-s1"><span class="pl-k">model</span> <span class="pl-en">User</span> {</span> <span class="pl-s1"> <span class="pl-smi">id</span> <span class="pl-c1">Int</span> <span class="pl-s1"><span class="pl-en">@id</span></span> <span class="pl-s1"><span class="pl-en">@default</span>(<span class="pl-s1"><span class="pl-c1">autoincrement</span>()</span>)</span></span> <span class="pl-s1"> <span class="pl-smi">name</span> <span class="pl-c1">String</span><span class="pl-k">?</span></span> <span class="pl-s1"> <span class="pl-smi">profile</span> <span class="pl-c1">Profile</span> <span class="pl-c">// ❌ this is not allowed as of 2.12.0</span></span> <span class="pl-s1">}</span>

<span class="pl-s1"><span class="pl-k">model</span> <span class="pl-en">Profile</span> {</span> <span class="pl-s1"> <span class="pl-smi">id</span> <span class="pl-c1">Int</span> <span class="pl-s1"><span class="pl-en">@id</span></span> <span class="pl-s1"><span class="pl-en">@default</span>(<span class="pl-s1"><span class="pl-c1">autoincrement</span>()</span>)</span></span> <span class="pl-s1"> <span class="pl-smi">user</span> <span class="pl-c1">User</span> <span class="pl-s1"><span class="pl-en">@relation</span>(<span class="pl-v">fields</span>: <span class="pl-s1">[<span class="pl-c1">userId</span>]</span>, <span class="pl-v">references</span>: <span class="pl-s1">[<span class="pl-c1">id</span>]</span>)</span></span> <span class="pl-s1"> <span class="pl-smi">userId</span> <span class="pl-c1">Int</span></span> <span class="pl-s1">}</span></pre></div> <p><strong>After</strong></p> <div class="highlight highlight-source-prisma"><pre><span class="pl-s1"><span class="pl-k">model</span> <span class="pl-en">User</span> {</span> <span class="pl-s1"> <span class="pl-smi">id</span> <span class="pl-c1">Int</span> <span class="pl-s1"><span class="pl-en">@id</span></span> <span class="pl-s1"><span class="pl-en">@default</span>(<span class="pl-s1"><span class="pl-c1">autoincrement</span>()</span>)</span></span> <span class="pl-s1"> <span class="pl-smi">profile</span> <span class="pl-c1">Profile</span><span class="pl-k">?</span> <span class="pl-c">// ✅ the virtual side of the relation needs to be optional</span></span> <span class="pl-s1">}</span>

<span class="pl-s1"><span class="pl-k">model</span> <span class="pl-en">Profile</span> {</span> <span class="pl-s1"> <span class="pl-smi">id</span> <span class="pl-c1">Int</span> <span class="pl-s1"><span class="pl-en">@id</span></span> <span class="pl-s1"><span class="pl-en">@default</span>(<span class="pl-s1"><span class="pl-c1">autoincrement</span>()</span>)</span></span> <span class="pl-s1"> <span class="pl-smi">user</span> <span class="pl-c1">User</span> <span class="pl-s1"><span class="pl-en">@relation</span>(<span class="pl-v">fields</span>: <span class="pl-s1">[<span class="pl-c1">userId</span>]</span>, <span class="pl-v">references</span>: <span class="pl-s1">[<span class="pl-c1">id</span>]</span>)</span></span> <span class="pl-s1"> <span class="pl-smi">userId</span> <span class="pl-c1">Int</span></span> <span class="pl-s1">}</span></pre></div> <p>The easiest way to adjust your schema to these new requirements is by running the <code>introspect</code> command which will automatically make the virtual relation fields optional on 1-1-relations:</p> <pre><code>npx prisma introspect </code></pre> <h2>Fix how data for <code>Json[]</code> fields is stored</h2> <p>We fixed how the <code>Json[]</code> type is stored in <code>2.12.0</code>. Previously, we were storing JSON arrays as a string inside a your database's <code>JSON</code> column. Now, we properly encode JSON arrays as <code>JSON</code> in the database. This fix will allow us to add database native JSON operations down the line.</p> <p>If you are using the <code>Json[]</code> type in your schema, you'll need to migrate your data. We anticipate this breaking change will only affect a handful of folks. Please reach out to us in <a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/4346">this issue</a> and we'll help you with the migration.</p> <p>Here is an overview of how the behaviour changes in <code>2.12.0</code>:</p> <table role="table"> <thead> <tr> <th align="left">Given</th> <th align="left"><code>2.11.0</code></th> <th align="left"><code>2.12.0</code></th> </tr> </thead> <tbody> <tr> <td align="left"><code>[]</code></td> <td align="left"><code>[[]]</code></td> <td align="left"><code>[]</code></td> </tr> <tr> <td align="left"><code>[{test:"test"}]</code></td> <td align="left"><code>["{"test":"test"}"]</code></td> <td align="left"><code>[{"test":"test"}]</code></td> </tr> <tr> <td align="left"><code>[{ test: "test" }, { test: "test2" }]</code></td> <td align="left"><code>["[{"test": "test"}, {"test": "test2"}]"]</code></td> <td align="left"><code>[{"test": "test"},{"test": "test2"}]</code></td> </tr> <tr> <td align="left"><code>[3]</code></td> <td align="left"><code>3</code></td> <td align="left"><code>[3]</code></td> </tr> </tbody> </table> <h2>Deprecations</h2> <h3>Rename <code>findOne</code> to <code>findUnique</code> </h3> <p>This release renames <code>findOne</code> to <code>findUnique</code> and deprecates <code>findOne</code>.</p> <p>We made this change to reduce confusion. Many people expected <code>findOne</code> to be more loose, e.g: "Find the first record that matches my conditions.".</p> <p>The <code>@prisma/codemods</code> workflow describe above will automatically rename <code>findOne</code> to <code>findUnique</code> across your codebase.</p> <h3>Move most types under the <code>Prisma</code> namespace</h3> <p>We moved most of the generated types under a new <code>Prisma</code> namespace and are deprecating the top-level exports. This change also resolves some existing namespace clashes.</p> <p><strong>Before</strong></p> <div class="highlight highlight-source-ts"><pre><span class="pl-k">import</span> <span class="pl-kos">{</span> <span class="pl-smi">PrismaClient</span><span class="pl-kos">,</span> <span class="pl-smi">User</span><span class="pl-kos">,</span> <span class="pl-smi">UserCreateInput</span> <span class="pl-kos">}</span> <span class="pl-k">from</span> <span class="pl-s">'@prisma/client'</span>

<span class="pl-k">async</span> <span class="pl-k">function</span> <span class="pl-en">createUser</span><span class="pl-kos">(</span><span class="pl-s1">input</span>: <span class="pl-smi">UserCreateInput</span><span class="pl-kos">)</span>: <span class="pl-smi">Promise</span><span class="pl-kos"><</span><span class="pl-smi">User</span><span class="pl-kos">></span> <span class="pl-kos">{</span> <span class="pl-k">return</span> <span class="pl-s1">prisma</span><span class="pl-kos">.</span><span class="pl-c1">user</span><span class="pl-kos">.</span><span class="pl-en">create</span><span class="pl-kos">(</span><span class="pl-s1">input</span><span class="pl-kos">)</span> <span class="pl-kos">}</span></pre></div> <p><strong>After</strong></p> <div class="highlight highlight-source-ts"><pre><span class="pl-k">import</span> <span class="pl-kos">{</span> <span class="pl-smi">PrismaClient</span><span class="pl-kos">,</span> <span class="pl-smi">User</span><span class="pl-kos">,</span> <span class="pl-smi">Prisma</span> <span class="pl-kos">}</span> <span class="pl-k">from</span> <span class="pl-s">'@prisma/client'</span>

<span class="pl-k">async</span> <span class="pl-k">function</span> <span class="pl-en">createUser</span><span class="pl-kos">(</span><span class="pl-s1">input</span>: <span class="pl-smi">Prisma</span><span class="pl-kos">.</span><span class="pl-smi">UserCreateInput</span><span class="pl-kos">)</span>: <span class="pl-smi">Promise</span><span class="pl-kos"><</span><span class="pl-smi">User</span><span class="pl-kos">></span> <span class="pl-kos">{</span> <span class="pl-k">return</span> <span class="pl-s1">prisma</span><span class="pl-kos">.</span><span class="pl-c1">user</span><span class="pl-kos">.</span><span class="pl-en">create</span><span class="pl-kos">(</span><span class="pl-s1">input</span><span class="pl-kos">)</span> <span class="pl-kos">}</span></pre></div> <p>This means that with this release, there are exactly three kinds of exports in <code>@prisma/client</code>:</p> <ol> <li> <code>PrismaClient</code> is the constructor your Prisma Client instance</li> <li>Model types, e.g. <code>User</code> and <code>Post</code> </li> <li> <code>Prisma</code> as the new namespace under which you can now access the remaining generarted types</li> </ol> <p>The <code>@prisma/codemods</code> workflow describe above will automatically fix the type names in your code!</p> <p>With this change, we've greatly reduced the number of <em>reserved words</em> that could clash with your application's names. Go forth and add models with names like <code>Transaction</code> or <code>Aggregate</code>!</p> <h2>Fixes and improvements</h2> <h3><a href="https://bounce.depfu.com/github.com/prisma/prisma"><code>prisma</code></a></h3> <ul> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/3223">Remove GraphQL related reserved words</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/3290">Collect <code>dbgenerated()</code> values in an issue via "warning" output in Introspection</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/3603">Json arrays are not properly stored in underlying postgres jsonb array type </a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/3697">Replace <code>findOne</code> with <code>findUnique</code></a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/3747">Schema validator is not validating optionality of relations on both ends</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/3755">Use TypeScript namespaces to separate Prisma & Application types</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/3780">Gather example schemas for MS SQL Server</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/3887">Enable updating foreign keys in updateMany</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/3897">Json[] isn't working anymore</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/3985">Fields are ignored in WHERE clause</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/4053">Native Types Postgres: Creating a record with empty arrays for field types json[], jsonb[] not working</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/4150">Create codemod for namespace change</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/4205">Prisma2 blocks prisma generate on unsupported platforms, even when providing custom binaries</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/4206">Cleanup old non-$ methods</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/4213">Fix version pinning logic</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/4222">Warn, if more than <code>n</code> Prisma Client instances are instantiated</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/4300">Add codemod for $ deprecation</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/4332">SQL Server raw queries panic when having multiple result sets</a></li> </ul> <h3><a href="https://bounce.depfu.com/github.com/prisma/prisma-client-js"><code>prisma-client-js</code></a></h3> <ul> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma-client-js/issues/312">Improve debug output of array values</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma-client-js/issues/585">[Javascript] Better error message than <code>TypeError: Cannot read property 'findMany' of undefined</code> for non existing model?</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma-client-js/issues/811">Remove Aggregate as reserved word</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma-client-js/issues/837">Test and stabilize Unix Domain Sockets</a></li> </ul> <h3><a href="https://bounce.depfu.com/github.com/prisma/migrate"><code>migrate</code></a></h3> <ul> <li><a href="https://bounce.depfu.com/github.com/prisma/migrate/issues/418">ERROR: there is no unique constraint matching given keys for referenced table "User"</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/migrate/issues/472">Suggest using <code>name</code> on index when creation fails because of length</a></li> </ul> <h3><a href="https://bounce.depfu.com/github.com/prisma/language-tools"><code>language-tools</code></a></h3> <ul> <li><a href="https://bounce.depfu.com/github.com/prisma/language-tools/issues/41">Display relation fields differently than scalar fields</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/language-tools/issues/522">Warn about provider array deprecation in the VSCode plugin</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/language-tools/issues/627">Improve logging of language server</a></li> </ul> <h3><a href="https://bounce.depfu.com/github.com/prisma/studio"><code>studio</code></a></h3> <ul> <li><a href="https://bounce.depfu.com/github.com/prisma/studio/issues/578">When saving changes to the database, do it one transaction</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/studio/issues/579">Studio server does not resolve environment variables correctly</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/studio/issues/580">Focus first cell of a newly created record</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/studio/issues/581">When you start typing in a number cell directly, it is considered an invalid change</a></li> </ul> <h3><a href="https://bounce.depfu.com/github.com/prisma/prisma-engines"><code>prisma-engines</code></a></h3> <ul> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma-engines/issues/1173">Send the "server listening" message only after the server has started</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma-engines/issues/1183">Supporting native types on SQL Server</a></li> </ul> <h2>Credits</h2> <p>Huge thanks to <a href="https://bounce.depfu.com/github.com/matt-eric">@matt-eric</a>, <a href="https://bounce.depfu.com/github.com/muxahuk">@muxahuk</a> for helping!</p></blockquote> <h4><a href="https://github.com/prisma/prisma/releases/tag/2.11.0">2.11.0</a></h4>

<blockquote><p>Today, we are excited to share the <code>2.11.0</code> stable release <g-emoji class="g-emoji" alias="tada" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f389.png">🎉</g-emoji></p> <p><g-emoji class="g-emoji" alias="star2" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f31f.png">🌟</g-emoji> <strong>Help us spread the word about Prisma by starring the repo <g-emoji class="g-emoji" alias="point_up" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/261d.png">☝️</g-emoji> or <a href="https://twitter.com/intent/tweet?text=Check%20out%20the%20latest%20Prisma%20release%202.11.0%20%F0%9F%9A%80%0D%0A%0D%0Ahttps://github.com/prisma/prisma/releases/tag/2.11.0">tweeting</a> about the release.</strong></p> <h2>Major Improvements</h2> <h3>Native database types in the Prisma schema (Preview)</h3> <p>We are super excited to share that this release brings you one of the most requested features since we released the initial version of Prisma: The representation of native database types in the Prisma schema.</p> <p>Up to this release, the Prisma schema only allowed to represent a limited set of types: <code>String</code>, <code>Int</code>, <code>Float</code>, <code>Boolean</code>, <code>DateTime</code>, <code>Json</code>. Each of these types has a <em>default mapping</em> to an underlying database type that's specified for each connector (see the mappings for <a href="https://www.prisma.io/docs/reference/database-connectors/postgresql#type-mapping-between-postgresql-to-prisma-schema">PostgreSQL</a> and <a href="https://www.prisma.io/docs/reference/database-connectors/mysql#type-mapping-between-mysql-to-prisma-schema">MySQL</a>).</p> <p>With this release, you can now add an attribute to a field definition in order to determine which <em>specific</em> database type it should be mapped to. Here is an example for a PostgreSQL database that specifies the underlying database types more specifically. Note that you also need to enable the feature via the the <code>nativeTypes</code> feature flag:</p> <div class="highlight highlight-source-prisma"><pre><span class="pl-s1"><span class="pl-k">generator</span> <span class="pl-en">client</span> {</span> <span class="pl-s1"> <span class="pl-smi">provider</span> <span class="pl-k">=</span> <span class="pl-s">"</span><span class="pl-s">prisma-client-js</span><span class="pl-s">"</span></span> <span class="pl-s1"> <span class="pl-smi">previewFeatures</span> <span class="pl-k">=</span> <span class="pl-s1">[<span class="pl-s">"</span><span class="pl-s">nativeTypes</span><span class="pl-s">"</span>]</span></span> <span class="pl-s1">}</span>

<span class="pl-s1"><span class="pl-k">datasource</span> <span class="pl-en">db</span> {</span> <span class="pl-s1"> <span class="pl-smi">provider</span> <span class="pl-k">=</span> <span class="pl-s">"</span><span class="pl-s">postgresql</span><span class="pl-s">"</span></span> <span class="pl-s1"> <span class="pl-smi">url</span> <span class="pl-k">=</span> <span class="pl-s1"><span class="pl-c1">env</span>(<span class="pl-s">"</span><span class="pl-s">DATABASE_URL</span><span class="pl-s">"</span>)</span></span> <span class="pl-s1">}</span>

<span class="pl-s1"><span class="pl-k">model</span> <span class="pl-en">User</span> {</span> <span class="pl-s1"> <span class="pl-smi">id</span> <span class="pl-c1">Int</span> <span class="pl-s1"><span class="pl-en">@id</span></span> <span class="pl-s1"><span class="pl-en">@default</span>(<span class="pl-s1"><span class="pl-c1">autoincrement</span>()</span>)</span> </span> <span class="pl-s1"> <span class="pl-smi">name</span> <span class="pl-c1">String</span><span class="pl-k">?</span> <span class="pl-s1"><span class="pl-en">@db.VarChar</span>(<span class="pl-c1">255</span>)</span></span> <span class="pl-s1">}</span>

<span class="pl-s1"><span class="pl-k">model</span> <span class="pl-en">Post</span> {</span> <span class="pl-s1"> <span class="pl-smi">id</span> <span class="pl-c1">Int</span> <span class="pl-s1"><span class="pl-en">@id</span></span> <span class="pl-s1"><span class="pl-en">@default</span>(<span class="pl-s1"><span class="pl-c1">autoincrement</span>()</span>)</span> </span> <span class="pl-s1"> <span class="pl-smi">title</span> <span class="pl-c1">String</span> <span class="pl-s1"><span class="pl-en">@db.VarChar</span>(<span class="pl-c1">100</span>)</span></span> <span class="pl-s1"> <span class="pl-smi">createdAt</span> <span class="pl-c1">DateTime</span> <span class="pl-s1"><span class="pl-en">@db.Timestamp</span>(<span class="pl-c1">6</span>)</span></span> <span class="pl-s1"> <span class="pl-smi">wordCount</span> <span class="pl-c1">Int</span> <span class="pl-s1"><span class="pl-en">@db.SmallInt</span></span></span> <span class="pl-s1">}</span></pre></div> <p>In the above code snippet, all fields of the two Prisma models are annotated with attributes to diverge from the default mapping and determine the exact type that is used in the underlying database. For example, the <code>id</code> fields are represented as <code>db.BigInt</code> which maps to the <code>BIGINT</code> PostgreSQL type. You can find out more about which Prisma types can be annotated with which native type attributes in the docs for the <a href="https://www.prisma.io/docs/reference/database-connectors/postgresql#type-mapping-between-postgresql-to-prisma-schema">PostgreSQL</a> and <a href="https://www.prisma.io/docs/reference/database-connectors/mysql#type-mapping-between-mysql-to-prisma-schema">MySQL</a> connectors.</p> <p>Please <a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/4045">share your feedback</a> on how this feature works for you. We are interested in both positive and negative feedback, so we know if this feature is already ready for production! (If encounter any problems, please open a new issue <a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/new/choose">here</a>).</p> <p><g-emoji class="g-emoji" alias="books" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f4da.png">📚</g-emoji> <strong>Documentation</strong>: <a href="https://www.prisma.io/docs/concepts/components/preview-features/native-types">Extended native type support</a></p> <h3>New types in the Prisma schema: <code>BigInt</code>, <code>Bytes</code> and <code>Decimal</code> (Preview)</h3> <p>With this release, we are further introducing three new <em>scalar types</em> in the Prisma schema: <code>BigInt</code>, <code>Bytes</code> and <code>Decimal</code>. Here is an overview for how they map to the different databases that are supported by Prisma and how they're represented when queried with Prisma Client JS:</p> <table role="table"> <thead> <tr> <th>Prisma</th> <th>PostgreSQL</th> <th>MySQL</th> <th>SQLite</th> <th>JavaScript / TypeScript</th> </tr> </thead> <tbody> <tr> <td><code>Bytes</code></td> <td><code>BYTEA</code></td> <td><code>LONGBLOB</code></td> <td>n/a</td> <td><code>Buffer</code></td> </tr> <tr> <td><code>Decimal</code></td> <td><code>DECIMAL(65,30)</code></td> <td><code>DECIMAL(65,30)</code></td> <td>n/a</td> <td><a href="https://bounce.depfu.com/github.com/MikeMcl/decimal.js/">Decimal.js</a></td> </tr> <tr> <td><code>BigInt</code></td> <td><code>BIGINT</code></td> <td><code>BIGINT</code></td> <td>n/a</td> <td><code>BigInt</code></td> </tr> </tbody> </table> <p>To make use of these new types, you need to enable the <code>nativeTypes</code> feature flag in your Prisma schema:</p> <div class="highlight highlight-source-diff"><pre>generator client { provider = "prisma-client-js" <span class="pl-mi1"><span class="pl-mi1">+</span> previewFeatures = ["nativeTypes"]</span> }</pre></div> <p>Once you added the feature flag, be sure to run <code>prisma generate</code> again to update your local version of Prisma Client.</p> <p><g-emoji class="g-emoji" alias="books" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f4da.png">📚</g-emoji> <strong>Documentation</strong>: <a href="https://www.prisma.io/docs/concepts/components/preview-features/native-types/native-types-mappings">Prisma types in the <code>nativeTypes</code> preview</a></p> <h3>Set foreign keys directly (Preview)</h3> <p>We now support writing foreign keys (also known as <a href="https://www.prisma.io/docs/concepts/components/prisma-schema/relations#annotated-relation-fields-and-relation-scalar-fields">relation scalars</a>) directly with the <code>uncheckedScalarInputs</code> preview feature.</p> <p>Consider this sample Prisma schema:</p> <div class="highlight highlight-source-prisma"><pre><span class="pl-s1"><span class="pl-k">generator</span> <span class="pl-en">client</span> {</span> <span class="pl-s1"> <span class="pl-smi">provider</span> <span class="pl-k">=</span> <span class="pl-s">"</span><span class="pl-s">prisma-client-js</span><span class="pl-s">"</span></span> <span class="pl-s1"> <span class="pl-smi">previewFeatures</span> <span class="pl-k">=</span> <span class="pl-s1">[<span class="pl-s">"</span><span class="pl-s">uncheckedScalarInputs</span><span class="pl-s">"</span>]</span></span> <span class="pl-s1">}</span>

<span class="pl-s1"><span class="pl-k">model</span> <span class="pl-en">User</span> {</span> <span class="pl-s1"> <span class="pl-smi">id</span> <span class="pl-c1">Int</span> <span class="pl-s1"><span class="pl-en">@id</span></span> <span class="pl-s1"><span class="pl-en">@default</span>(<span class="pl-s1"><span class="pl-c1">autoincrement</span>()</span>)</span></span> <span class="pl-s1"> <span class="pl-smi">posts</span> <span class="pl-c1">Post</span><span class="pl-k">[]</span></span> <span class="pl-s1">}</span>

<span class="pl-s1"><span class="pl-k">model</span> <span class="pl-en">Post</span> {</span> <span class="pl-s1"> <span class="pl-smi">id</span> <span class="pl-c1">Int</span> <span class="pl-s1"><span class="pl-en">@id</span></span> <span class="pl-s1"><span class="pl-en">@default</span>(<span class="pl-s1"><span class="pl-c1">autoincrement</span>()</span>)</span></span> <span class="pl-s1"> <span class="pl-smi">authorId</span> <span class="pl-c1">Int</span></span> <span class="pl-s1"> <span class="pl-smi">author</span> <span class="pl-c1">User</span> <span class="pl-s1"><span class="pl-en">@relation</span>(<span class="pl-v">fields</span>: <span class="pl-s1">[<span class="pl-c1">authorId</span>]</span>, <span class="pl-v">references</span>: <span class="pl-s1">[<span class="pl-c1">id</span>]</span>)</span></span> <span class="pl-s1">}</span></pre></div> <p>Instead of using <code>connect</code> when creating a new <code>Post</code> record to wire up a relation with a <code>User</code> record, you can now directly set the <code>authorId</code> value:</p> <div class="highlight highlight-source-ts"><pre><span class="pl-k">await</span> <span class="pl-s1">prisma</span><span class="pl-kos">.</span><span class="pl-c1">post</span><span class="pl-kos">.</span><span class="pl-en">create</span><span class="pl-kos">(</span><span class="pl-kos">{</span> <span class="pl-c1">data</span>: <span class="pl-kos">{</span> <span class="pl-c">// You can now set the foreign key directly...</span> <span class="pl-c1">authorId</span>: <span class="pl-c1">1</span><span class="pl-kos">,</span> <span class="pl-c">// ... or connect the relationship...</span> <span class="pl-c">// author: {</span> <span class="pl-c">// connect: {</span> <span class="pl-c">// id: 1</span> <span class="pl-c">// }</span> <span class="pl-c">// }</span> <span class="pl-c">// ... but not both at the same time</span> <span class="pl-kos">}</span><span class="pl-kos">,</span> <span class="pl-kos">}</span><span class="pl-kos">)</span><span class="pl-kos">;</span></pre></div> <p>We'd love for you to give it a try. You can give us feedback in <a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/4209">this issue</a>.</p> <h3>The <code>$transaction</code> API is now stable</h3> <p>You can now use <a href="https://www.prisma.io/docs/concepts/components/prisma-client/transactions#the-transaction-api"><code>$transaction</code></a> API without the <code>transactionApi</code> feature flag.</p> <div class="highlight highlight-source-diff"><pre>generator client { provider = "prisma-client-js" <span class="pl-md"><span class="pl-md">-</span> previewFeatures = ["transactionApi"]</span> }</pre></div> <h3>The <code>connectOrCreate</code> API is now stable</h3> <p>The <a href="https://www.prisma.io/docs/concepts/components/prisma-client/relation-queries#nested-writes"><code>connectOrCreate</code></a> API offers a convenient way to link or insert nested records.</p> <p>You can now use it without the <code>connectOrCreate</code> feature flag.</p> <div class="highlight highlight-source-diff"><pre>generator client { provider = "prisma-client-js" <span class="pl-md"><span class="pl-md">-</span> previewFeatures = ["connectOrCreate"]</span> }</pre></div> <h3>Middleware model parameter is now typed</h3> <p>This is a small quality-of-life improvement for developers using the Prisma <a href="https://www.prisma.io/docs/concepts/components/prisma-client/middleware">middleware</a>. The <code>params.model</code> parameter that's passed into a middleware function is now typed to your model so you can now reliably tie middleware to models:</p> <div class="highlight highlight-source-ts"><pre><span class="pl-s1">prisma</span><span class="pl-kos">.</span><span class="pl-en">$use</span><span class="pl-kos">(</span><span class="pl-k">async</span> <span class="pl-kos">(</span><span class="pl-s1">params</span><span class="pl-kos">,</span> <span class="pl-s1">next</span><span class="pl-kos">)</span> <span class="pl-c1">=></span> <span class="pl-kos">{</span> <span class="pl-k">switch</span> <span class="pl-kos">(</span><span class="pl-s1">params</span><span class="pl-kos">.</span><span class="pl-c1">model</span><span class="pl-kos">)</span> <span class="pl-kos">{</span> <span class="pl-k">case</span> <span class="pl-s">'user'</span>: <span class="pl-c">// ...</span> <span class="pl-k">case</span> 'project: <span class="pl-c">// ...</span> <span class="pl-kos">}</span> <span class="pl-kos">}</span><span class="pl-kos">)</span></pre></div> <p>If you need the old behavior you can cast <code>params.model</code> back to a <code>string</code> by wrapping it <code>String(params.model)</code>.</p> <p><g-emoji class="g-emoji" alias="books" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f4da.png">📚</g-emoji> <strong>Documentation</strong>: <a href="https://www.prisma.io/docs/concepts/components/prisma-client/middleware">Middleware</a></p> <h3>Deprecation of multi-provider array</h3> <p>You will now see a warning if you have multiple providers in your <code>datasource</code>. We recently realized that supporting an array of providers in the Prisma schema was premature, adding complexity in the process of improving the product, and causing some confusion about our intent.</p> <p>You can read more about the decision and what to do about it in <a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/3834">this issue</a>.</p> <h3>Validate <code>PrismaClient</code> inputs at runtime</h3> <p>We now validate the <code>parameters</code> we accept in <code>new PrismaClient(parameters)</code>. This is unlikely to affect you unless you were passing invalid parameters into <code>PrismaClient</code> before.</p> <h2>Prisma Client Go is now Early Access <g-emoji class="g-emoji" alias="tada" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f389.png">🎉</g-emoji> </h2> <p>We're happy to announce that <a href="https://bounce.depfu.com/github.com/prisma/prisma-client-go">Prisma Client Go</a> has graduated from experimental to <a href="https://www.prisma.io/docs/about/releases#early-access">Early Access</a>.</p> <p>You can <a href="https://bounce.depfu.com/github.com/prisma/prisma-client-go/blob/master/docs/quickstart.md">get started here</a>. We'd love to learn more about how you use the Go Client during Early Access. You can schedule a <a href="https://calendly.com/c/DDAUQECG7NYIBU5Q">call with us</a> or <a href="https://slack.prisma.io/">chat with us on Slack</a> in the #prisma-client-go channel. We're looking forward to hearing from you!</p> <h2> <g-emoji class="g-emoji" alias="tv" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f4fa.png">📺</g-emoji> Join us for another "What's new in Prisma" livestream</h2> <p>Learn about the latest release and other news from the Prisma community by joining us for another <a href="https://www.youtube.com/watch?v=XFCGpwcVUCY&ab_channel=Prisma">"What's new in Prisma"</a> livestream.</p> <p>The stream takes place <a href="https://www.youtube.com/watch?v=XFCGpwcVUCY&ab_channel=Prisma">on Youtube</a> on <strong>Thursday, November 12</strong> at <strong>5pm Berlin | 8am San Francisco</strong>.</p> <h2> <g-emoji class="g-emoji" alias="eyes" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f440.png">👀</g-emoji> Make your online talk recordings more accessible with subtitles</h2> <p>We'd love to help you make your talk recordings (no matter if Meetup or conference talk) more accessible by <a href="https://twitter.com/prisma/status/1325744486425780224">adding subtitles</a> to it <strong>for free</strong>! Reach out to <a href="sponsorships@prisma.io">sponsorships@prisma.io</a> if you are interested in getting subtitles for your videos!</p> <h2>Fixes and improvements</h2> <h3><a href="https://bounce.depfu.com/github.com/prisma/prisma"><code>prisma</code></a></h3> <ul> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/2152">Can't create a record with only the foreign key to another table</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/3081">Foreign key field is not being set when using a nested create for a one-to-one relation</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/3517">Prisma Client is unable to fetch DateTime lists</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/3545">Middleware params model should be an enum or union of strings.</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/3571">vercel/pkg broken on windows</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/3572">vercel/pkg errors on windows</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/3708">Introspection fails instantly MariaDB</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/3750">DATABASE_URL verification still attempted when datasource override provided in PrismaClient constructor</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/3802">Introspection should try to preserve custom Enum names on MySQL even without @map</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/3805">Mutliple 1-n self relations break migrations</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/3892">.transaction([]) fails with Request Timeout Error on large dataset</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/3918">JSON value truncate floating numbers</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/3923">Postgresql: Large double precision float values cause panic</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/3945">Error in prisma results in unhandled promise rejection</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/3989">Consolidate Undici error handling</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/3994">Internal: update our <code>pnpm</code> version used for development and CI</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/4000">Internal: Create new milestone check GitHub Action</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/4011">Prisma and Netlify, binary is not downloaded automatically since 2.8.0</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/4035">Detect and enforce Node Version in <code>preinstall</code> hook so pnpm fails clearly</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/4048">Package name reuse (.prisma/client) when generating multiple prisma clients causes issues with some other libraries (e.g. jest)</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/4050">Native Types: @db.BigInt should be BigInt</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/4064">Prisma generate or introspect don't work when nativeTypes preview is enabled</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/4082">Cannot update a model with composite keys through a referenced model</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/4083">RangeError: Invalid count value during create</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/4096">Prisma Client doesn't load root .env</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/4098">You are trying to load env variables which are already present in your project root .env</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/4125">Stabilize connectOrCreate</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/4126">Stabilize transactionApi</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/4144">Add integration test to trigger env var warning in Prisma Client</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/4186">Improve error when using prisma migrate --experimental with native types</a></li> </ul> <h3><a href="https://bounce.depfu.com/github.com/prisma/prisma-client-js"><code>prisma-client-js</code></a></h3> <ul> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma-client-js/issues/889">Runtime validation for Prisma client constructor parameters</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma-client-js/issues/894">$transaction spread operator</a></li> </ul> <h3><a href="https://bounce.depfu.com/github.com/prisma/language-tools"><code>language-tools</code></a></h3> <ul> <li><a href="https://bounce.depfu.com/github.com/prisma/language-tools/issues/158">Add Prisma icon to standard icon theme in VSCode</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/language-tools/issues/424">Gitpod Support</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/language-tools/issues/602">prisma.plugin.nextjs.addTypesOnSave broken</a></li> </ul> <h3><a href="https://bounce.depfu.com/github.com/prisma/studio"><code>studio</code></a></h3> <ul> <li><a href="https://bounce.depfu.com/github.com/prisma/studio/issues/529">Unable to view / edit DateTime lists</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/studio/issues/561">Case insensitive searching</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/studio/issues/563">npx prisma studio doesn't work on WSL 1</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/studio/issues/571">Cannot type "." in a float column</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/studio/issues/572">Websockets fails when studio is behind a reverse proxy</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/studio/issues/576">[design] Cell overflow</a></li> </ul> <h3><a href="https://bounce.depfu.com/github.com/prisma/prisma-engines"><code>prisma-engines</code></a></h3> <ul> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma-engines/issues/1284">Introduce support for scalar type <code>BigInt</code></a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma-engines/issues/1291">Native Type Precisions</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma-engines/issues/1317">Remove Scalar Type <code>Duration</code></a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma-engines/issues/1318">Feature gate scalar types <code>Decimal</code> and <code>Bytes</code></a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma-engines/issues/1323">Remove TimestampWithTimeZone, TimeWithTimeZone and Intervall</a></li> </ul></blockquote> <h4><a href="https://github.com/prisma/prisma/releases/tag/2.10.2">2.10.2</a></h4>

<blockquote><p>Today, we are issuing the <code>2.10.2</code> patch release.</p> <h2>Fixes</h2> <h3>Client</h3> <ul> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/4098">You are trying to load env variables which are already present in your project root .env #4098</a></li> </ul> <h3>Language Tools</h3> <ul> <li><a href="https://bounce.depfu.com/github.com/prisma/language-tools/issues/605">Prisma vscode extension is autoformating typescript react code on save #605</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/language-tools/issues/606">Npm throws error on build creation while Prisma extension is enabled #606</a></li> </ul></blockquote> <h4><a href="https://github.com/prisma/prisma/releases/tag/2.10.1">2.10.1</a></h4>

<blockquote><p>Today, we are issuing the <code>2.10.1</code> patch release.</p> <h2>Fixes</h2> <h3>CLI</h3> <ul> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/4097">@prisma/engines are not used by CLI #4097</a></li> </ul> <h3>Client</h3> <ul> <li><a href="https://bounce.depfu.com/github.com/prisma/prisma/issues/4096">Prisma Client doesn't load root .env #4096</a></li> </ul> <h3>Migrate</h3> <ul> <li><a href="https://bounce.depfu.com/github.com/prisma/migrate/issues/626">Prisma Migrate Crash on change required foreign key to not-required #626</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/migrate/issues/627">v2.10.0 #627</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/migrate/issues/625">crashed after the first migration #625</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/migrate/issues/623">Error in migration engine. #623</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/migrate/issues/621">Migration issue on changing userId field to unique. related to #619 #621</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/migrate/issues/619">Migration crashed with code #619</a></li> <li><a href="https://bounce.depfu.com/github.com/prisma/migrate/issues/618">Crash Report #618</a></li> </ul> <h3>Language Tools</h3> <ul> <li><a href="https://bounce.depfu.com/github.com/prisma/language-tools/pull/603">prisma.plugin.nextjs.addTypesOnSave broken #602</a></li> </ul></blockquote> <p><em>Does any of this look wrong? <a href="https://depfu.com/packages/npm/@prisma%2Fcli/feedback">Please let us know.</a></em></p> </details>

<details> <summary>Commits</summary> <p><a href="https://github.com/prisma/prisma/compare/139ad870db512c26b331d812fa38a2174b85dff8...1cb154de53598bf1e7c438293f4babffe81fbf8a">See the full diff on Github</a>. The new version differs by more commits than we can show here.</p> </details>

✳️ jest (24.9.0 → 26.5.3) · Repo · Changelog

<details> <summary>Release Notes</summary> <p><em>Too many releases to show here. View the <a href="https://github.com/facebook/jest/blob/master/CHANGELOG.md">full release notes</a>.</em></p> </details>

<details> <summary>Commits</summary> <p><a href="https://github.com/facebook/jest/compare/3cdbd556948b4974b2cc23178977eb159d343df8...71152afbbda76fd09ddb2527b54c365d753f42aa">See the full diff on Github</a>. The new version differs by more commits than we can show here.</p> </details>

✳️ ts-jest (24.3.0 → 26.4.1) · Repo · Changelog

<details> <summary>Release Notes</summary> <p><em>Too many releases to show here. View the <a href="https://github.com/kulshekhar/ts-jest/blob/master/CHANGELOG.md">full release notes</a>.</em></p> </details>

<details> <summary>Commits</summary> <p><a href="https://github.com/kulshekhar/ts-jest/compare/51f8f826eca9072ba70fd8c5998392381f3a5721...2caeaf4747cc0b61ac503b9b50b08221b261075b">See the full diff on Github</a>. The new version differs by more commits than we can show here.</p> </details>


Depfu Status

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

<details><summary>All Depfu comment commands</summary> <blockquote><dl> <dt>@​depfu rebase</dt><dd>Rebases against your default branch and redoes this update</dd> <dt>@​depfu recreate</dt><dd>Recreates this PR, overwriting any edits that you've made to it</dd> <dt>@​depfu merge</dt><dd>Merges this PR once your tests are passing and conflicts are resolved</dd> <dt>@​depfu close</dt><dd>Closes this PR and deletes the branch</dd> <dt>@​depfu reopen</dt><dd>Restores the branch and reopens this PR (if it's closed)</dd> <dt>@​depfu pause</dt><dd>Ignores all future updates for this dependency and closes this PR</dd> <dt>@​depfu pause [minor|major]</dt><dd>Ignores all future minor/major updates for this dependency and closes this PR</dd> <dt>@​depfu resume</dt><dd>Future versions of this dependency will create PRs again (leaves this PR as is)</dd> </dl></blockquote> </details>

+897 -41

0 comment

5 changed files

pr created time in a day

more