- 07 8月, 2020 9 次提交
-
-
由 JJ Kasper 提交于
-
由 Sven Anderson 提交于
This example application guides you to build a next.js application and integrate lambda.store as data store. See readme for details.
-
由 Markoz Peña 提交于
## Which solves this PR Displaying a friendly error, when the user is only passing `statusOrUrl`(type number) and the second argument `url` is ignored. **Example** `res.redirect(307);` // Show friendly error Closes: https://github.com/vercel/next.js/issues/15594 x-ref: https://github.com/vercel/next.js/pull/15603
-
由 Tom Dohnal 提交于
This resolves https://github.com/vercel/next.js/issues/13659
-
由 Arsalan Khattak 提交于
Co-authored-by: NLuis Alvarez D. <luis@vercel.com>
-
由 Evil Rabbit 提交于
-
由 Raibima Putra 提交于
-
由 Eric Piacentini 提交于
Co-authored-by: NLuis Alvarez D <luis@vercel.com> Co-authored-by: NTim Neutkens <timneutkens@me.com> Co-authored-by: NJoe Haddad <timer150@gmail.com>
-
由 Jan Potoms 提交于
-
- 06 8月, 2020 19 次提交
-
-
由 Joe Haddad 提交于
-
由 Joe Haddad 提交于
Fixes #15928 --- This would cause us to print the message too early and open the browser to a server that wasn't started yet. This waits until we're listening, but before the app is ready fully.
-
由 Joe Haddad 提交于
-
由 Joe Haddad 提交于
Co-authored-by: NJJ Kasper <jj@jjsweb.site>
-
由 Aubrey 提交于
updated example for [active-class-name](https://github.com/vercel/next.js/tree/f00ad581a16a3023f4be88940d3330550544509b/examples/active-class-name) to also support a `[slug].js` page that matches on `as` instead of `href` (as `href` would be `/[slug]`) > This does not demo `[..slug].js` as this requires possible custom code for determining the slug path part for the active classname. i.e. page tree active nodes. A possible other example or another PR on this example. Has possible information for: * https://github.com/vercel/next.js/issues/7410
-
由 matamatanot 提交于
-
由 Luis Alvarez D 提交于
This is the same fix from https://github.com/vercel/next.js/pull/15729 - Adding it in a new PR as I can't update the current one. Closes #15729 Fixes #15676
-
由 Robin Tom 提交于
This PR adds example for #15073 > - [ ] `redirects` For [docs/api-reference/next.config.js/redirects.md](https://github.com/vercel/next.js/blob/canary/docs/api-reference/next.config.js/redirects.md)
-
由 Joe Haddad 提交于
-
由 Joris 提交于
Co-authored-by: NJoe Haddad <joe.haddad@zeit.co>
-
由 Joe Haddad 提交于
This PR reduces padding on all [iPhone models](https://developer.apple.com/library/archive/documentation/DeviceInformation/Reference/iOSDeviceCompatibility/Displays/Displays.html) to make the error easier to see when you have the debugger open. Before ![image](https://user-images.githubusercontent.com/616428/89454188-5a334b80-d72e-11ea-8e0b-ce392615d814.png) After ![image](https://user-images.githubusercontent.com/616428/89454129-40920400-d72e-11ea-903d-8a8178da2966.png) --- Fixes #14702 Closes #14767
-
由 JJ Kasper 提交于
Since we now use query parameters to pass dynamic route params while routing on Vercel, this makes sure we normalize the request URL before populating the `asPath` Fixes: https://github.com/vercel/next.js/issues/15879
-
由 Tim Neutkens 提交于
Adds handling for module not found errors exposed by webpack. This ensures you see the actual stack line and code instead of a short message where you don't know where to go. ### Previous <img width="794" alt="Screen Shot 2020-08-05 at 18 02 06" src="https://user-images.githubusercontent.com/6324199/89435935-d5542c00-d745-11ea-9ca7-c67f553364f9.png"> ### New <img width="769" alt="Screen Shot 2020-08-05 at 14 20 23" src="https://user-images.githubusercontent.com/6324199/89412212-f6595480-d726-11ea-81a3-398ab7036338.png"> Fixes #14711
-
由 Joe Haddad 提交于
-
由 Mikkel Laursen 提交于
-
由 Jan Potoms 提交于
-
由 Jan Potoms 提交于
Fixes https://github.com/vercel/next.js/issues/15639 Fixes https://github.com/vercel/next.js/issues/15820 To Do: - [x] Doesn't work with `basePath` yet
-
由 Alex Castle 提交于
This PR adds a second experimental post-processing step for the framework introduced by @prateekbh in #14746. The image post-processing step scans the rendered document for the first few images and uses a simple heuristic to determine if the images should be automatically preloaded. Analysis of quite a few production Next apps has shown that a lot of sites are taking a substantial hit to their [LCP](https://web.dev/lcp/) score because an image that's part of the "hero" element on the page is not preloaded and is getting downloaded with lower priority than the JavaScript bundles. This post-processor should automatically fix that for a lot of sites, without causing any real performance effects in cases where it fails to identify the hero image. This feature is behind an experimental flag, and will be subject to quite a bit of experimentation and tweaking before it's ready to be made a default setting.
-
由 Sigurður Gunnar Njálsson 提交于
Fixes https://github.com/vercel/next.js/issues/15906 This should solve https://github.com/vercel/next.js/issues/15906. It simply removes a block that states runtime configuration for serverless builds are not supported.
-
- 05 8月, 2020 12 次提交
-
-
由 Jack Clackett 提交于
-
由 Aleksander 提交于
-
由 Steven 提交于
Follow up to #15899 since it didn't solve the [concurrency limit](https://docs.github.com/en/actions/getting-started-with-github-actions/about-github-actions#usage-limits) issue. It seems that the job is queued prior to the `if` statement being evaluated so we must use a separate workflow to listen for push events and filter prior to the job being queued.
-
由 nirtamir2 提交于
-
由 Riccardo Di Maio 提交于
Co-authored-by: Nkodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
由 Rounak Agarwal 提交于
Co-authored-by: NTim Neutkens <tim@timneutkens.nl> Co-authored-by: Nkodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
由 Steven 提交于
Only run macOS tests on canary to avoid queued jobs due to [concurrency limit](https://docs.github.com/en/actions/getting-started-with-github-actions/about-github-actions#usage-limits). Follow up to #15366
-
由 Darsh Patel 提交于
removed the dotenv dependency in favor of Next.js environment support: #15225 The example seems to work with no other changes required ![Screenshot 2020-08-03 at 12 03 22 PM](https://user-images.githubusercontent.com/11258286/89152753-557d6480-d581-11ea-919c-4b89a6bec4b6.png)
-
由 Joseph Knowles 提交于
Fix with-firebase-authentication example: Update the cookie when ID token refreshes on client (#15628) I noticed a problem with the example - when you leave it logged in for more than an hour it breaks. The example API call starts to fail with `auth/id-token-expired`. Looking at the code I saw that we never update the id token after signing in, but firebase automatically updates it every hour, meaning our `verifyIdToken` fails after an hour. So I used the `onIdTokenChanged` function from firebase to update the cookie every time the id token changes. I'm open to suggestions on refactoring the code I've added.
-
由 Amith Mihiranga 提交于
Correct the error handling for fetch API to check if the status is ok or not FIxes #15808
-
由 Flavian Desverne 提交于
## Motivation As Graphcool is being shutdown, we replaced all the graphcool api endpoints with some handcrafted APIs using Prisma & Nexus, that can be found here https://github.com/prisma-labs/nextjs-graphql-api-examples. These GraphQL endpoints are now deployed to Vercel. ## Notes - I couldn't get the reason-relay example to run. Given that the relay endpoint works on the other relay example, I don't see any reason why it wouldn't work on that one - The `with-apollo` example is buggy when creating some posts, but nothing related to the switch of the api endpoint as it was already buggy before. I suspect the `concatPagination` strategy to be the cause of that bug, but I couldn't figure it out. Fixes #14780
-
由 Darsh Patel 提交于
-