The purpose of this RFC (Request For Comments) is to gather as much feedback as possible before building everything outlined in it.

We welcome all feedback, whether good or bad! This is your chance to ensure Blitz meets the needs for your company or project.

👉 View the Rendered RFC 👈

Also, there are now two other open issues for defining more details on Blitz queries and mutations:

1. Query & Mutation Usage: https://github.com/blitz-js/blitz/issues/89
2. Query & Mutation Error Handling: https://github.com/blitz-js/blitz/issues/87

Please also check those out and provide any feedback!

Pull Request Type

• [ ] Feature
• [ ] Bug fix
• [x] Refactoring (no functional changes, no api changes)
• [ ] Build related changes
• [ ] Tests related changes
• [ ] Other (please describe): Dependency updates

Checklist

• [x] Tests added for changes (or N/A)
• [x] Any added terminal logging uses packages/server/src/log.ts (or N/A)
• [x] Code Coverage stayed the same or increased

What's the reason for the change? :question:

Synchronizer was not structured in an extensible way that allows us to move forward quickly.

What are the changes and their implications? :gear:

• [x] Agnostic input file watcher / glob = no watcher in unit tests
• [x] Define stream error rendering
• [x] Related logic needs to live together
• [x] Everything is a stream
• [x] More efficiency potential
• [x] Parallel processing
• [x] Cleaner Architecture
• [x] Prepare for dirty restart functionality
• [x] Migrate existing functionality over to streams
  • [x] Incorporate zeit now build logic
  • [x] Incorporate duplicate page detection logic
  • [x] Add app/foo/api/bar -> pages/api/bar to paths rule
• [x] Simplify tests
• [x] Docs
• [x] Move deps to root
• [x] Support VERCEL_BUILDER
• [x] "stuck" on the last file progress indicator
• [x] ~~Cross package loader animation~~ (probably best done in the cli package)

Does this introduce a breaking change? :warning:

• [ ] Yes
• [x] No

Closes blitz-js/legacy-framework#897

Synchronizer Refactor

Rendered docs

Design goals

• [x] Rules: Related logic needs to live together
• [x] Everything is a rule
• [x] Efficiency
• [x] Parallel processing via streams
• [x] Cleaner Architecture to allow for future Dirty restart functionality
• [x] Agnostic input file watcher / glob
• [x] Define error decoration pattern

Tasks

Fuzzy / Concerns

• How do we handle calls to process.exit()? Currently I handle exit in a try catch for upfront stuff that prevents execution but that is wrong as it doesn't take into account what happens after the promise has resolved and the watcher

Things to look at still possibly later PR

• Use in memory fs for tests

Closes: blitz-js/legacy-framework#513

What are the changes and their implications?

Give users a Route manifest as described in blitz-js/legacy-framework#513.

ToDo:

• [x] Generate manifest
• [x] Decide on where the manifest should be generated into
• [x] Do TypeScript shenanigans to allow importing from blitz

Checklist

• [x] Changes covered by tests (tests added if needed)
• [x] PR submitted to blitzjs.com for any user facing changes

The purpose of this RFC (Request for Comments) is to gather as much feedback as possible.

We welcome all feedback, whether good or bad! This is your chance to ensure Blitz meets the needs of your company or project.

👉 View the Rendered RFC 👈

What is the problem?

I tested this only happens when adding passport auth with Google (tried to add the auth file to a new sample repo, reproduced the issue).

Paste all your error logs here:

Server side log:

xiaoshundan-macbookpro2:tokenpass xiaoshundan$ blitz dev
Loaded env from /Users/xiaoshundan/workspace/tokenpass/.env.local
Loaded env from /Users/xiaoshundan/workspace/tokenpass/.env
ready - started server on 0.0.0.0:3000, url: http://localhost:3000
event - compiled client and server successfully in 647 ms (275 modules)
wait  - compiling /404 (client and server)...
event - compiled client and server successfully in 176 ms (280 modules)
warn  - Fast Refresh had to perform a full reload. Read more: https://nextjs.org/docs/basic-features/fast-refresh#how-it-works
wait  - compiling / (client and server)...
event - compiled client and server successfully in 128 ms (325 modules)
[Rendering Suspense fallback...]
warn  - Fast Refresh had to perform a full reload. Read more: https://nextjs.org/docs/basic-features/fast-refresh#how-it-works
[Rendering Suspense fallback...]
[Rendering Suspense fallback...]
wait  - compiling /api/rpc/[[...blitz]]...
event - compiled successfully in 136 ms (91 modules)
[blitzSessionMiddleware] Starting handler...
Starting sessionMiddleware...
Starting with input: null
Result: null
Next.js serialization:1ms
Finished: resolver:0ms serializer:1ms total:1ms

Client side error:

Unhandled Runtime Error
Error: The server could not finish this Suspense boundary, likely due to an error during server rendering. Switched to client rendering.

Call Stack
updateDehydratedSuspenseComponent
node_modules/react-dom/cjs/react-dom.development.js (21469:0)
updateSuspenseComponent
node_modules/react-dom/cjs/react-dom.development.js (21129:0)
beginWork
node_modules/react-dom/cjs/react-dom.development.js (22379:0)
beginWork$1
node_modules/react-dom/cjs/react-dom.development.js (27219:0)
performUnitOfWork
node_modules/react-dom/cjs/react-dom.development.js (26392:0)
workLoopSync
node_modules/react-dom/cjs/react-dom.development.js (26303:0)
renderRootSync
node_modules/react-dom/cjs/react-dom.development.js (26271:0)
performConcurrentWorkOnRoot
node_modules/react-dom/cjs/react-dom.development.js (25577:0)
workLoop
node_modules/scheduler/cjs/scheduler.development.js (266:0)
flushWork
node_modules/scheduler/cjs/scheduler.development.js (239:0)
MessagePort.performWorkUntilDeadline
node_modules/scheduler/cjs/scheduler.development.js (533:0)

Paste all relevant code snippets here:

Please check: https://github.com/sherryxiao1988/blitz-passport-error/blob/main/pages/api/auth/%5B...auth%5D.ts

What are detailed steps to reproduce this?

I created a repo with this error:

https://github.com/sherryxiao1988/blitz-passport-error

Run blitz -v and paste the output here:

xiaoshundan-macbookpro2:blitz-example xiaoshundan$ blitz -v
Loaded env from /Users/xiaoshundan/workspace/blitz-example/.env.local
Loaded env from /Users/xiaoshundan/workspace/blitz-example/.env
Blitz version: 2.0.0-alpha.58 (global)
Blitz version: 2.0.0-alpha.58 (local)
macOS Monterey | darwin-x64 | Node: v16.15.1


 Package manager: npm

  System:
    OS: macOS 12.4
    CPU: (16) x64 Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz
    Memory: 557.58 MB / 32.00 GB
    Shell: 3.2.57 - /bin/bash
  Binaries:
    Node: 16.15.1 - ~/.nvm/versions/node/v16.15.1/bin/node
    Yarn: 1.22.19 - ~/.nvm/versions/node/v16.15.1/bin/yarn
    npm: 8.11.0 - ~/.nvm/versions/node/v16.15.1/bin/npm
  npmPackages:
    @blitzjs/auth: alpha => 2.0.0-alpha.58
    @blitzjs/next: alpha => 2.0.0-alpha.58
    @blitzjs/rpc: 2.0.0-alpha.58 => 2.0.0-alpha.58
    @prisma/client: 3.9.0 => 3.9.0
    blitz: 2.0.0-alpha.58 => 2.0.0-alpha.58
    next: 12.2.0 => 12.2.0
    prisma: 4.0.0 => 4.0.0
    react: 18.0.0 => 18.0.0
    react-dom: 18.0.0 => 18.0.0
    typescript: ^4.5.3 => 4.7.4

Please include below any other applicable logs and screenshots that show your problem:

No response

Closes: blitz-js/legacy-framework#233

What are the changes and their implications?

If a user doesn't provide a recipe name, the command will show a prompt to choose a recipe from a list of available recipes.

Bug Checklist

• [x] Integration test added (see test docs if needed)

Feature Checklist

• [ ] Integration test added (see test docs if needed)
• [x] Documentation added/updated (submit PR to blitzjs.com repo) document page pull request

This issue is for defining the RPC specification used for Blitz queries and mutations. Each query and mutation can be used by third parties, so the specification must be clear and documented publicly.

This initial specification is my first pass. I haven't thought real deeply about this, so please help me refine it!

• [x] Define the specification
• [ ] Implement versioning (#98)
• [x] Add comprehensive tests (#99)
• [x] Add specification to the Blitz docs (https://github.com/blitz-js/blitzjs.com/issues/21)

Specification

This specification is used for both queries and mutations. From an HTTP perspective, there is no difference between a query and mutation because they are both function calls.

Details

HEAD

This will be used to warm the lambda. For example, when a component renders on the client that uses a mutation, it will issue a HEAD request to the mutation endpoint immediately on page load so that there's a much higher chance the actual mutation request will hit a warm lambda.

• Must always return HTTP 200

POST

Used to actually execute the RPC

• Request body must be JSON with the following keys:
  • params (required) - This will be provided as the first argument to the query or mutation
  • version (optional) - String containing the version of the built RPC client
• Response body is JSON with the following keys:
  • result - the exact result returned from the query/mutation function or null if there was an error
  • error - null if success, otherwise an object.

Example:

// Valid request
{
  params: {id: 1},
}

// Success response
{
  result: {id: 1, name: "Brandon"},
  error: null
}

Responses

| | HTTP Response Code | Response result value | Response error value | | --------------------------------- | ------------- | ------------------------------------------- | ---------------------------------------------------------- | | HEAD | 200 | - | - | | Valid request | 200 | - | - | | Invalid request, not JSON | 400 | null | {message: "Request body is not valid JSON"} | | Invalid request, missing params | 400 | null | {message: "Request body is missing the 'params' key"} | | Execution success | 200 | Exact value returned from query/mutation function | null | | Execution error | 200 | null | TBD | | All other HTTP verbs, like GET | 404 | - | - |

Versioning

Any time you have client-server communication, there is a very real risk of the client & server code becoming out of sync and causing an error. For example, let's say you have a mutation function whose input is a single object. You decide to change the mutation input to be a single array. You make the change and deploy it. Your server code is now updated, but all your users still have the old client code running in the browser. So it's likely you now have client code sending an object to your mutation which is going to error because it's expecting an array.

Now one obvious solution is to only make changes that are backwards compatible, but sometimes you can't do this.

The other solution is to track the version of your client code and your server code. If there is a version mismatch, you can display a friendly message to the user, telling them they need to reload the webpage to continue.

Blitz is well positioned to provide this, so let's do.

• During the build, we generate a unique version number that's embedded in both the rpc client and the server handlers.
• The RPC client will automatically send it's version to the server in the request body.
• The server will check for a version match.
• If the versions don't match, we let the handler run as usual, resulting in execution success or error. But we also need to return an indicator in the response about whether the versions match. Maybe we can add a versionMismatch to the error object if execution fails. Then the Blitz dev can check that field in their error handler if they want.

Notes

• I'll create another issue for defining how error handling works. I.e. how queries and mutations can return error data to the client.

What is the problem?

Using the latest toolkit .60.

Home.authenticate = { redirectTo: Routes.LoginPage() }

Doesn't seem to do anything. Have confirmed nothing in the application Tab in dev tools.

Also

LoginPage.redirectAuthenticatedTo = Routes.Home()

Seems to create the following error, when authenticated and hitting the page:

Run blitz -v and paste the output here:

Blitz version: 2.0.0-alpha.53 (global)
Blitz version: 2.0.0-alpha.60 (local)
macOS Monterey | darwin-arm64 | Node: v18.4.0


 Package manager: npm

  System:
    OS: macOS 12.4
    CPU: (10) arm64 Apple M1 Pro
    Memory: 556.45 MB / 32.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 18.4.0 - ~/.nvm/versions/node/v18.4.0/bin/node
    Yarn: 1.22.19 - ~/.nvm/versions/node/v18.4.0/bin/yarn
    npm: 8.12.1 - ~/.nvm/versions/node/v18.4.0/bin/npm
  npmPackages:
    @prisma/client: Not Found
    blitz: Not Found
    next: Not Found
    prisma: Not Found
    react: Not Found
    react-dom: Not Found
    typescript: Not Found

Closes: blitz-js/legacy-framework#759 Closes: blitz-js/legacy-framework#683

What are the changes and their implications?

Blitz's file pipeline moves files from A to B, but doesn't update any imports to A. This PR makes sure that imports are rewritten, such that importing from any of the moved files doesn't break compilation.

Checklist

• [X] Tests added for changes
• [ ] PR submitted to blitzjs.com for any user facing changes

What are the changes and their implications?

Since VSCode is the most used JavaScript editor, I think we should add recommended extensions and configuration to new apps.

The extensions are:

• ESLint
• EditorConfig for VSCode
• Prettier - Code formatter
• DotENV
• Babel JavaScript
• Jest
• Prisma

The default configuration is:

• Format (with Prettier) on Save
• Fix ESLint errors on Save

Also, there is a basic EditorConfig!

Type: feature

Closes: https://github.com/blitz-js/legacy-framework/issues/825

What are the changes and their implications? :gear:

Adds a CLI flag for the user to specify a --parent while generating pages. These pages will be nested under {{parentModelName}}/{{parentModelId}}, enabling the user to generate pages for dependent data models:

$ blitz g pages tasks --parent=projects
You are using alpha software - if you have any problems, please open an issue here:
  https://github.com/blitz-js/blitz/issues/new/choose

CREATE    app/tasks/pages/projects/[projectId]/tasks/[id]/edit.tsx
CREATE    app/tasks/pages/projects/[projectId]/tasks/[id].tsx
CREATE    app/tasks/pages/projects/[projectId]/tasks/index.tsx
CREATE    app/tasks/pages/projects/[projectId]/tasks/new.tsx

Checklist

• [ ] Tests added for changes
• [ ] Any added terminal logging uses packages/server/src/log.ts

Breaking change: no

Closes: #4014

What are the changes and their implications?

• Add digest property when throwing an error and use the new nextjs constant (NEXT_DYNAMIC_NO_SSR_CODE) per (https://github.com/vercel/next.js/blob/canary/packages/next/shared/lib/no-ssr-error.ts).
• Use the semver package to ensure previous codegen patch satisfies versions 13-13.0.6

Bug Checklist

• [x] Changeset added (run pnpm changeset in the root directory)
• [ ] Integration test added (see test docs if needed)

Feature Checklist

• [x] Changeset added (run pnpm changeset in the root directory)
• [ ] Integration test added (see test docs if needed)
• [ ] Documentation added/updated (submit PR to blitzjs.com repo main branch)

What is the problem?

I am trying to prefetch whether or not the user is logged in to avoid rendering the suspense fallback. My understanding is that if the user data is available, the suspense fallback shouldn't be rendered.

However, when I prefetch the user, the suspense callback gets rendered anyway. Is this the correct behavior?

Paste all relevant code snippets here:

useCurrentUser.ts:

import { useQuery } from "@blitzjs/rpc"
import getCurrentUser from "src/users/queries/getCurrentUser"
import { Ctx } from "blitz"

export const useCurrentUser = () => {
  const [user] = useQuery(getCurrentUser, null)
  return user
}

export const prefetchCurrentUser = async (ctx: Ctx) => {
  await ctx.prefetchQuery(getCurrentUser, null)
}

index.tsx

import { Suspense } from "react"
import Layout from "src/core/layouts/Layout"
import { prefetchCurrentUser, useCurrentUser } from "src/users/hooks/useCurrentUser"
import { BlitzPage } from "@blitzjs/next"
import { gSSP } from "../blitz-server"

export const getServerSideProps = gSSP(async ({ ctx }) => {
  await prefetchCurrentUser(ctx)

  return { props: {} }
})

const UserInfo = () => {
  const currentUser = useCurrentUser()

  if (currentUser) {
    return (
      <>
        logged in
      </>
    )
  } else {
    return <>
      logged out
    </>
  }
}

const Home: BlitzPage = () => {
  return (
    <Layout title="Home">
      <Suspense fallback="Loading...">
        <UserInfo />
      </Suspense>
    </Layout>
  )
}

export default Home

What are detailed steps to reproduce this?

1. run blitz new with typescript, db & auth, pnpm
2. Change the files mentioned above
3. Run blitz dev
4. Observe [Rendering Suspense fallback...] in logs

Run blitz -v and paste the output here:

Blitz version: 2.0.0-beta.20 (global)
Blitz version: 2.0.0-beta.20 (local)
Windows 11 | win32-x64 | Node: v16.14.2


 Package manager: pnpm

  System:
    OS: Windows 10 10.0.22621
    CPU: (20) x64 12th Gen Intel(R) Core(TM) i9-12900H
    Memory: 14.89 GB / 31.70 GB
  Binaries:
    Node: 16.14.2 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.19 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 9.2.0 - C:\Program Files\nodejs\npm.CMD
  npmPackages:
    @blitzjs/auth: 2.0.0-beta.20 => 2.0.0-beta.20
    @blitzjs/next: 2.0.0-beta.20 => 2.0.0-beta.20
    @blitzjs/rpc: 2.0.0-beta.20 => 2.0.0-beta.20
    @prisma/client: 4.6.0 => 4.6.0
    blitz: 2.0.0-beta.20 => 2.0.0-beta.20
    next: 12.2.5 => 12.2.5
    prisma: 4.6.0 => 4.6.0
    react: 18.2.0 => 18.2.0
    react-dom: 18.2.0 => 18.2.0
    typescript: ^4.8.4 => 4.9.4

Please include below any other applicable logs and screenshots that show your problem:

No response

Closes: https://github.com/blitz-js/blitz/issues/4021

What are the changes and their implications?

The input strings passed to blitz g are checked against an allow list of characters via regex. The helper throws if an unwanted character is found.

I think it would be enough to check in prisma/fields.ts. The main reason for added it there was so the tests in prisma/fields.test.ts can be used to test the regex. However, generators/model-generator.ts has the raw string (right?), so this would be the place it first. To keep the code simpler, we could remove it from generators/model-generator.ts again – let me know what you thing.

Also, please give the regex and everything a good review. I am new new to this :-).

Bug Checklist

• [x] Changeset added (run pnpm changeset in the root directory)
• [ ] Integration test added (see test docs if needed)

Feature Checklist

• [x] Changeset added (run pnpm changeset in the root directory)
• [ ] Integration test added (see test docs if needed)
• [ ] ~Documentation added/updated (submit PR to blitzjs.com repo main branch)~

What is the problem?

This is what I get after breaking thinks:

% blitz help
blitz:22: command not found: endAt:dateTime
% blitz g all post title:string author:string content:string
blitz:23: command not found: endAt:dateTime
% blitz help
blitz:24: command not found: endAt:dateTime

This is likely how I broke thinks…

I suspect the now() caused the issue.

blitz generate all date startAt:dateTime:default=now() endAt:dateTime title:string locationName:string locationUrl:string description:string id:uuid --dry-run 

How not to fix this…

• npm uninstall -g blitz, then reinstall does not help
• force-cleaning the npm cache does not help
• removing node_modues, then reinstalling all does not help

How to fix it:

I had to remove files in a npm temp folder, which "cached" broken code.

// 
$ echo TMPDIR
/var/folders/_2/w9vhc5hx1fg2vfmnypv3wvmm0000gp/T/
    
% cd $TMPDIR
% cd node-jiti
% ls
  blitz-auth-build.config.ts.42bb7c8e.js
  blitz-build.config.ts.531e0b43.js
  blitz-next-build.config.ts.b5eaaddf.js
  blitz-rpc-build.config.ts.f41b01c7.js
  codemod-build.config.ts.8d2cf2eb.js
  generator-build.config.ts.515f44ba.js
  pkg-template-build.config.ts.40d86f9a.js
    
$ cat pkg-template-build.config.ts.40d86f9a.js

"use strict"; Object.defineProperty(exports, "__esModule", { value: true }); exports.default = void 0;

const config = {
  entries: ["./src/index-browser", "./src/index-server"],
  externals: ["index-browser.cjs", "index-browser.mjs", "react"],
  declaration: true,
  rollup: {
    emitCJS: true,
    esbuild: {
      target: ["es2015"] } } };var _default =



config; exports.default = _default; /* v7-eb5970095fe3c5ea */

$ cat /private/var/folders/_2/w9vhc5hx1fg2vfmnypv3wvmm0000gp/T/node-jiti/generator-build.config.ts.515f44ba.js

"use strict";Object.defineProperty(exports, "__esModule", { value: true });exports.default = void 0;

const config = {
  entries: ["./src/index"],
  externals: ["react"],
  declaration: true,
  rollup: {
    emitCJS: true,
    esbuild: {
      target: ["es2015"] } } };var _default =



config;exports.default = _default; /* v7-5f8f751e7d033013 */

Other blitz files hold the same content. Once I removed them all, blitz started working again.

A quick fix could be to make sure only allow-listed characters (A-Za-z-_:=, but no () etc) are processed by the generator. I peeked at https://github.com/blitz-js/blitz/blob/main/packages/blitz/src/cli/commands/generate.ts but could not see where to do this…

Paste all your error logs here:

See above.

Paste all relevant code snippets here:

See above.

What are detailed steps to reproduce this?

See above.

Run blitz -v and paste the output here:

% blit
z --version
Blitz version: 2.0.0-beta.20 (global)
Blitz version: 2.0.0-beta.20 (local)
macOS Ventura | darwin-arm64 | Node: v18.8.0


 Package manager: npm

  System:
    OS: macOS 13.0.1
    CPU: (8) arm64 Apple M1
    Memory: 83.39 MB / 16.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 18.8.0 - ~/.nvm/versions/node/v18.8.0/bin/node
    Yarn: Not Found
    npm: 8.18.0 - ~/.nvm/versions/node/v18.8.0/bin/npm
  npmPackages:
    @blitzjs/auth: 2.0.0-beta.20 => 2.0.0-beta.20
    @blitzjs/next: 2.0.0-beta.20 => 2.0.0-beta.20
    @blitzjs/rpc: 2.0.0-beta.20 => 2.0.0-beta.20
    @prisma/client: 4.6.0 => 4.6.0
    blitz: 2.0.0-beta.20 => 2.0.0-beta.20
    next: 12.2.5 => 12.2.5
    prisma: 4.6.0 => 4.6.0
    react: 18.2.0 => 18.2.0
    react-dom: 18.2.0 => 18.2.0
    typescript: ^4.8.4 => 4.9.4

Please include below any other applicable logs and screenshots that show your problem:

No response

What are the changes and their implications?

The other three auth templates have the <Layout> right in the component. This brings the reset-password file(s) in line. It also gets rid of the empty wrapper-<div>.

Feature Checklist

I had trouble getting all tests running due to ELIFECYCLE errors. In case this is broken, feel free to just close the ticket.

• [x] Changeset added (run pnpm changeset in the root directory)
• [x] ~~Integration test added (see test docs if needed)~~
• [x] ~~Documentation added/updated (submit PR to blitzjs.com repo main branch)~~

What is the problem?

Hi,

I am trying to use setQueryData to change some of the data from useInifiniteQuery hook before the request to backend is complete. It seems, that it doesn't do anything actually. I think there is also a few problems with typing. I am using it right? This function seems bit unmaintained so what do you guys use for infinite query?

Paste all your error logs here:

No error.

Paste all relevant code snippets here:

// typescript throws error here, even tho it should be possible to return just the old data
setQueryData(oldData => oldData)

// old data is in fact undefined
setQueryData((oldData) => {
   console.log({ oldData }) // oldData === undefined in most of the cases
})

// it's typed to use like this but that doesn't work
setQueryData({
      contacts: [{ ...contactFormValues, id: faker.datatype.uuid() }],
      ...contactPages[0]
 }, {refetch: false})

// kinda make sense to use it like this, but also doesn't work
const [firstPage, ...restPages] = contactPages;
setQueryData([
      {
        ...firstPage,
        contacts: [
          { ...contactFormValues, id: faker.datatype.uuid() },
          ...firstPage.contacts
        ],
      },
      ...restPages
], {refetch: false})

What are detailed steps to reproduce this?

1. pull https://github.com/Daidalos117/blitzjs-infinity/
2. go to /contacts and try to add new contact
3. open app/contacts/components/ContactsList.tsx in editor
4. look into the onOnContactSave fnc

Run blitz -v and paste the output here:

blitz -v
Blitz version: 2.0.0-beta.4 (global)
Blitz version: 2.0.0-beta.20 (local)
macOS Monterey | darwin-arm64 | Node: v16.17.1


 Package manager: npm

  System:
    OS: macOS 12.6
    CPU: (8) arm64 Apple M1 Pro
    Memory: 568.14 MB / 16.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 16.17.1 - /usr/local/bin/node
    Yarn: 1.22.17 - /opt/homebrew/bin/yarn
    npm: 8.5.5 - /opt/homebrew/bin/npm
  npmPackages:
    @blitzjs/auth: 2.0.0-beta.20 => 2.0.0-beta.20 
    @blitzjs/next: 2.0.0-beta.20 => 2.0.0-beta.20 
    @blitzjs/rpc: 2.0.0-beta.20 => 2.0.0-beta.20 
    @prisma/client: 4.0.0 => 4.0.0 
    blitz: 2.0.0-beta.20 => 2.0.0-beta.20 
    next: 12.2.5 => 12.2.5 
    prisma: 4.0.0 => 4.0.0 
    react: 18.2.0 => 18.2.0 
    react-dom: 18.2.0 => 18.2.0 
    typescript: ^4.5.3 => 4.9.4 

Please include below any other applicable logs and screenshots that show your problem:

No error.