- 07 Aug, 2020 5 commits
-
-
Tim Neutkens authored
-
Tim Neutkens authored
-
Kazuhito Hokamura authored
In the Sentry example, sourcemaps is not enabled in server error. I solved this problem by using `RewriteFrames`. On the client side, the sourcemaps path is `~/_next`, but on the server side it needs to be `~/.next` (distDir), so I rewrite it using the `iteratee`. ref. https://docs.sentry.io/platforms/node/sourcemaps/#updating-sentry-sdk-configuration-to-support-source-maps ----- ## before <img width="983" alt="ss2" src="https://user-images.githubusercontent.com/39471/88479997-29188580-cf8e-11ea-8d16-10ccfa6fc1a4.png"> ## after <img width="989" alt="ss1" src="https://user-images.githubusercontent.com/39471/88479995-26b62b80-cf8e-11ea-8b1f-7784b32b9e6d.png">
-
JJ Kasper authored
-
Sven Anderson authored
This example application guides you to build a next.js application and integrate lambda.store as data store. See readme for details.
-
- 06 Aug, 2020 13 commits
-
-
🐝 Markoz Peña authored## 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 authored
This resolves https://github.com/vercel/next.js/issues/13659
-
Arsalan Khattak authored
Co-authored-by:Luis Alvarez D. <luis@vercel.com>
-
Evil Rabbit authored
-
Raibima Putra authored
-
Eric Piacentini authored
Co-authored-by:
Luis Alvarez D <luis@vercel.com> Co-authored-by:
Tim Neutkens <timneutkens@me.com> Co-authored-by:
Joe Haddad <timer150@gmail.com>
-
Jan Potoms authored
-
Joe Haddad authored
-
Joe Haddad authored
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 authored
-
Joe Haddad authored
Co-authored-by:JJ Kasper <jj@jjsweb.site>
-
Aubrey authored
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 authored
-
- 05 Aug, 2020 22 commits
-
-
Luis Alvarez D authored
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 authored
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 authored
-
Joris authored
Co-authored-by:Joe Haddad <joe.haddad@zeit.co>
-
Joe Haddad authored
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  After  --- Fixes #14702 Closes #14767
-
JJ Kasper authored
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 authored
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 authored
-
Mikkel Laursen authored
-
Jan Potoms authored
-
Jan Potoms authored
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 authored
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 authored
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.
-
Jack Clackett authored
-
Aleksander authored
-
Steven authored
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 authored
-
Riccardo Di Maio authored
Co-authored-by:kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
Rounak Agarwal authored
Co-authored-by:
Tim Neutkens <tim@timneutkens.nl> Co-authored-by:
kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
Steven authored
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 authored
removed the dotenv dependency in favor of Next.js environment support: #15225 The example seems to work with no other changes required 
-
Joseph Knowles authored
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.
-