I'm currently playing around with query prefetching, and my query results include date objects. In this case, I receive a serialization error as this object is being handled by next.

Error: Error serializing `.dehydratedState.queries[0].state.data.items[0].createdAt` returned from `getServerSideProps` in "/projects".
Reason: `object` ("[object Date]") cannot be serialized as JSON. Please only return JSON serializable data types.

<!-- Thanks for submitting an issue! All bug reports and problem issues require a reduced test case. Create one by forking any one of the CodePen examples from the docs. See guidelines link above. --> If we enable lazy loading jquery plugin we face issue with the display structure, Request you to kindly help us with the solution
Test case: http://codepen.io/desandro/pen/osFxj

.oO( This probably belongs on the gotrue repo )

Bug report

Describe the bug

When a user receives an invitation email and accepts it, then later opens the same email and clicks the link a second time the user is shown a JSON error on the supabase website.

To Reproduce

1. Go to Authentication in the dashboard
2. Click on 'Invite' in the header
3. Send an invitation to an unregistered email address you have access to
4. (wait for the email)
5. Open the email and click "Accept the invite"
6. Wait for Supabase to redirect you to your app
7. Open the same email and click "Accept the invite" again

Expected behavior

The user should be redirected to the app for the app to present the error message.

NOTE: The error message should be clear that it was an expired invitation. If it sends the displayed JSON error then it is the same payload as if someone attempts to use the magic login a second time (404). Please also see this feature request regarding these callbacks: https://github.com/supabase/supabase/discussions/1566

<!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible please:

• Link issue via "Closes #[2329]
• Choose & follow the right checklist for the change that you're making: -->

Closes: #2329

What are the changes and their implications?

Bug Checklist

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

Feature Checklist

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

Ideally, this should be handled on the server side. Sample code below:

import nextCookie from 'next-cookies'

.
.
.

export async function getServerSideProps(context) {
  
    const { token } = nextCookie(context)
    
    if (!token) {
        return {
            redirect: {
                permanent: false,
              destination: "/"
            }
        }
    }
    
    const data = getDataFromToken(token)
    
    return {
        props: data
    }
}

This pull request was created automatically by the sync-triage-config workflow.

What is the problem?

For the first time setup from blitzjs , using below commands throws error

• blitz new myAppName
• cd myAppName
• blitz dev

Solution is after running prisma commands from here , its works fine

Issue is very small & easy to fix but might be problematic for new users

Paste all your error logs here:

![Uploading image.png…]()

Paste all relevant code snippets here:

What are detailed steps to reproduce this?

1. Use blitz documentation first time setup

Run blitz -v and paste the output here:

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

blitz: 0.34.3 (global)
blitz: 0.34.3 (local)

  Package manager: yarn 
  System:
    OS: macOS 10.15.6
    CPU: (8) x64 Intel(R) Core(TM) i5-8257U CPU @ 1.40GHz
    Memory: 22.75 MB / 8.00 GB
    Shell: 5.7.1 - /bin/zsh
  Binaries:
    Node: 14.16.1 - /Users/yogi/.nvm/versions/node/v14.16.1/bin/node
    Yarn: 1.21.1 - /usr/local/bin/yarn
    npm: 6.14.12 - /Users/yogi/.nvm/versions/node/v14.16.1/bin/npm
    Watchman: Not Found
  npmPackages:
    @prisma/client: ~2.20 => 2.20.1 
    blitz: 0.34.3 => 0.34.3 
    prisma: ~2.20 => 2.20.1 
    react: 0.0.0-experimental-6a589ad71 => 0.0.0-experimental-6a589ad71 
    react-dom: 0.0.0-experimental-6a589ad71 => 0.0.0-experimental-6a589ad71 
    typescript: ~4.2 => 4.2.4 

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

No response

Hi @niklasgrewe 👋 Sorry for taking so long with this PR 😅 This should fix it, though.

<!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible please:

• Link issue via "Closes #[issue_number]
• Choose & follow the right checklist for the change that you're making: -->

Closes: #2272

What are the changes and their implications?

Fixes #2272 by detecting the location of node_modules/blitz and emitting besides it.

Bug Checklist

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

Feature Checklist

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

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployments, click below or on the icon next to each commit.

docs – ./web

🔍 Inspect: https://vercel.com/supabase/docs/5HfY7h74jDz8pnSsjaLyAngm3txe
✅ Preview: In Progress

Someone is attempting to deploy a commit to the Supabase Team on Vercel.

A member of the Team first needs to authorize it.

add documentation for traefik

@flybayer yes I believe so, thanks for pointing me in the right direction. I should have some time this evening to put up a PR for this change.

Added @fernvilla contributions for code

<!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible please:

• Link issue via "Closes #[issue_number]
• Choose & follow the right checklist for the change that you're making: -->

Closes: #2339

What are the changes and their implications?

Bug Checklist

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

Feature Checklist

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

What is the problem?

When generating a new blitz using version 0.35.0-canary.6 you receive this error: TypeError: Cannot convert undefined or null to object

Paste all your error logs here:

N/A

Paste all relevant code snippets here:

N/A

What are detailed steps to reproduce this?

1. Update to latest canary version.
2. Attempt to generate a new blitz app.
3. Observer the error in the console.

Run blitz -v and paste the output here:

blitz: 0.35.0-canary.6 (global)

  Package manager: npm 
  System:
    OS: macOS 11.3.1
    CPU: (8) x64 Apple M1
    Memory: 39.34 MB / 16.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 14.17.0 - /usr/local/bin/node
    Yarn: 1.22.10 - /usr/local/bin/yarn
    npm: 7.13.0 - /usr/local/bin/npm
    Watchman: Not Found
  npmPackages:
    @prisma/client: Not Found
    blitz: Not Found
    prisma: Not Found
    react: Not Found
    react-dom: Not Found
    typescript: Not Found

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

This error is usually caused when you call a function that expects an Object as its argument, but pass undefined or null instead. Could it be due to the change in no longer having dev dependencies?

Presumably, since there are no longer any dev dependencies inside package.json, pkg.devDependencies (on line 116 of app-generator.ts) will always be undefined.

A console.log of pkg in line 105 returns:

I suggest to introduce new flag --upgrade-cask and --upgrade-cask-greedy according to https://github.com/Homebrew/homebrew-autoupdate/issues/58#issue-876767244. I think separation formulas from casks upgrades would be more convenient.

I suggest changing StartInterval to StartCalendarInterval.

According to documentation StartInterval skips execution if computer is in sleep mode:

StartInterval <integer>
     This optional key causes the job to be started every N seconds. If the system is asleep during the time of the next scheduled interval firing, that interval will be missed due to shortcomings in queue(3).  If
     the job is running during an interval firing, that interval firing will likewise be missed.

StartCalendarInterval will be done right after its awakening and in my opinion this behavior is more desirable.

StartCalendarInterval <dictionary of integers or array of dictionaries of integers>
     This optional key causes the job to be started every calendar interval as specified. Missing arguments are considered to be wildcard. The semantics are similar to crontab(5) in how firing dates are specified.
     Multiple dictionaries may be specified in an array to schedule multiple calendar intervals.

Unlike cron which skips job invocations when the computer is asleep, launchd will start the job the next time the computer wakes up.  If multiple intervals transpire before the computer is woken, those events
     will be coalesced into one event upon wake from sleep.

We use Firebase currently for the easy of handling multi platform notifications: is this planned ( I could not find mention of it ) and otherwise, is it something that could be considered as a future feature?

I think there could be an option here.

If you see the way magic.link works, they have both - log in and sign up pages.

If you input email that does not exist yet, you get an error:

Now, my app is like the following code

const schema = zod.object({
     id: zod.string().uuid(),
    comment: zod.string().optional(),
    value: zod.number().min(1).max(2).int(),
})

What is the problem?

Hi there.

Described the problem at the title, but I guess this is may be zod's problem. Just a report.

Thank you!

Paste all your error logs here:

partially formatted

(property) authorize: ResolverAuthorize
<{
    id: string;
    comment: string;
    value: 1 ;
} | {
    id: string;
    comment: undefined;
    value: 2;
}, Ctx>(roleOrRoles?: "xxx" | ... 7 more ... | undefined) => (input: {
    ...;
} | {
    ...;
}, ctx: Ctx) => ResultWithContext<...>

Type 'undefined' is not assignable to type 'string'.
Type '2' is not assignable to type '1'.

Paste all relevant code snippets here:

export const schema = zod
  .object({
    id: zod.string().uuid(),
    comment: zod.string(),
    value: zod.literal(1),
  })
  .or(
    zod.object({
      id: zod.string().uuid(),
      comment: zod.undefined(),
      value: zod.literal(2),
    })
  )

export type Schema = zod.infer<typeof schema>

export default resolver.pipe(
  resolver.zod(schema),
  resolver.authorize(), // here!
  async () => {},
)

What are detailed steps to reproduce this?

1. Make union schema via zod.union / zod.object().or() and so on.
2. throw this schema to resolver.zod()
3. An error occurred while resolver.authorize()

Run blitz -v and paste the output here:

You are using beta software - if you have any problems, please open an issue here:
      https://github.com/blitz-js/blitz/issues/new/choose

macOS Big Sur | darwin-x64 | Node: v14.16.1

blitz: 0.34.1 (local)

  Package manager: yarn 
  System:
    OS: macOS 11.2.1
    CPU: (8) x64 Intel(R) Core(TM) i7-1068NG7 CPU @ 2.30GHz
    Memory: 128.62 MB / 32.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 14.16.1 - /var/folders/0h/r111qyg93qx4l1qbn96yjqhm0000gn/T/yarn--1620980841473-0.47879523957614545/node
    Yarn: 1.22.4 - /var/folders/0h/r111qyg93qx4l1qbn96yjqhm0000gn/T/yarn--1620980841473-0.47879523957614545/yarn
    npm: 6.14.12 - ~/.nodebrew/current/bin/npm
    Watchman: Not Found
  npmPackages:
    @prisma/client: 2.20.1 => 2.20.1 
    blitz: 0.34.1 => 0.34.1 
    prisma: 2.20.1 => 2.20.1 
    react: 0.0.0-experimental-3310209d0 => 0.0.0-experimental-3310209d0 
    react-dom: 0.0.0-experimental-3310209d0 => 0.0.0-experimental-3310209d0 
    typescript: 4.1.3 => 4.1.3 


✨  Done in 1.16s.

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

No response

What is the problem?

This error has occurred when I tried to import 'app/web-pages/queries/getWebPages' module

I tried moving "app/web-pages" to "app/aaapages", but that didn't work. I tried moving "app/web-pages" to "app/web-page", and it worked fine.

It seems to happen in 'app/(. +)pages' path.

Paste all your error logs here:

error - ./app/pages/web-pages/index.tsx:4:0
Module not found: Can't resolve 'app/web-pages/queries/getWebPages'
  2 | import { Head, Link, usePaginatedQuery, useRouter, BlitzPage, Routes } from "blitz"
  3 | import Layout from "app/core/layouts/Layout"
> 4 | import getWebPages from "app/web-pages/queries/getWebPages"
  5 | 
  6 | const ITEMS_PER_PAGE = 100
  7 | 

Paste all relevant code snippets here:

N/A

What are detailed steps to reproduce this?

1. Run blitz generate all WebPage command and it will generate the following files:

app/pages/web-pages/[webPageId]/edit.tsx
app/pages/web-pages/[webPageId].tsx
app/pages/web-pages/index.tsx
app/pages/web-pages/new.tsx
app/web-pages/components/WebPageForm.tsx
app/web-pages/queries/getWebPage.ts
app/web-pages/queries/getWebPages.ts
app/web-pages/mutations/createWebPage.ts
app/web-pages/mutations/deleteWebPage.ts
app/web-pages/mutations/updateWebPage.ts

2. Run blitz dev

3. Open http://localhost:3000/web-pages

Run blitz -v and paste the output here:

macOS Big Sur | darwin-arm64 | Node: v15.12.0

blitz: 0.34.3 (global)
blitz: 0.34.3 (local)

  Package manager: yarn 
  System:
    OS: macOS 11.2.3
    CPU: (8) arm64 Apple M1
    Memory: 70.95 MB / 8.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 15.12.0 - ~/.anyenv/envs/nodenv/versions/15.12.0/bin/node
    Yarn: 1.22.10 - ~/.anyenv/envs/nodenv/versions/15.12.0/bin/yarn
    npm: 7.6.3 - ~/.anyenv/envs/nodenv/versions/15.12.0/bin/npm
    Watchman: Not Found
  npmPackages:
    @prisma/client: ~2.20 => 2.20.1 
    blitz: 0.34.3 => 0.34.3 
    prisma: ~2.20 => 2.20.1 
    react: 0.0.0-experimental-6a589ad71 => 0.0.0-experimental-6a589ad71 
    react-dom: 0.0.0-experimental-6a589ad71 => 0.0.0-experimental-6a589ad71 
    typescript: ~4.2 => 4.2.4 

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

No response

Hey, obviously you will have a more informed opinion about this than me but i feel it would be awesome if official API in integrated into this mainly for 2 reasons.

• I saw the API docs and with due respect to them the response data format seems all over the place. A better abstraction over it will be of huge benefit to the community
• Speed has been a main issue with Notion. Implementing a cloudflare worker talking to official API + caching built in is exactly the kind of building block needed to use Notion as a headless CMS and build amazing things on top.

Just my 2 cents.