What version of Next.js are you using?

10.0.6-canary.9

What version of Node.js are you using?

14.15.4

What browser are you using?

Firefox 84

What operating system are you using?

Ubuntu 20.04

How are you deploying your application?

Vercel

Describe the Bug

Recently (i think 10.0.6-canary.8) the behavior for shallow routing was changed to not scroll-to-top anymore

A bit of context, we introduced swr two weeks ago to our codebase. Everything is working fine, but we started to get some reports about some parts of the app being broken in slightly older browsers (Chrome 49, Firefox 59, Edge 18, etc…)

We found out that swr was causing a syntax error in these browsers because webpack by default picked the ESM build (rightly so) but because it's not transp

There is some text on the page, but it is hard coding in your index.js.
The better way is to make it customizable by parsing markdown or reading from the config file.

But, I think Gatsby is not as convenient as next.js in terms of reading data.... so do you consider changing the page framework? 😳

Atm now-deno uses the latest release but I think it would be good for users to (optionally?) pass a version number for the deno-lambda release to use.

(In the future this will match the deno version.)

Feature request

Is your feature request related to a problem? Please describe.

When you deploy the starter it doesn't have any products and prices because the Stripe account doesn't have any.

Describe the solution you'd like

Create a fixture json file to bootstrap some products & prices: https://stripe.com/docs/cli/fixtures

Description

Upon execution of /usr/local/bin/npx vercel -t ... Preview/Production URLs are currently exposed in the deploy logs. This may not always be desirable in public repos.

Vercel CLI 21.0.1
- Deploying colinwilson/static-exp

- Deploying colinwilson/static-exp

Inspect: https://vercel.com/colinwilson/static-exp/k9vv3xpaw [2s]

Inspect: https://vercel.com/colinwilson/s