- 06 8月, 2020 9 次提交
-
-
由 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 提交于
-
由 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 提交于
-
由 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.
-
- 05 8月, 2020 5 次提交
-
-
由 Joe Haddad 提交于
-
由 Joe Haddad 提交于
Next.js plugins like `@next/mdx` inject additional webpack loaders to compile files, but they omit the necessary loader for Fast Refresh to work. Instead of making these files deopt out of Fast Refresh, we can automatically detect and inject the loader in these cases. Fixes #13574
-
由 Joe Haddad 提交于
-
由 Jan Potoms 提交于
-
由 jiangtao 提交于
fixed issue with runtime-config returning undefined when building or in a development environment (#15777) fix https://github.com/vercel/next.js/issues/7713#issuecomment-643632270
-
- 04 8月, 2020 8 次提交
-
-
由 Joe Haddad 提交于
By popular request, this pull request adds support for returning `fallback: 'blocking'` from `getStaticPaths`. This new mode will cause unknown paths to be rendered on-demand ("SSR") without the static (placeholder) fallback. This feature is **currently experimental and should not be used in production yet**. It's currently flagged behind `unstable_`: ``` fallback: 'unstable_blocking' ``` TODO: - [x] Next.js tests - [ ] Add Vercel support - [ ] Vercel tests --- Fixes #15637
-
由 Tim Neutkens 提交于
-
由 Darsh Patel 提交于
The icon is just something I thought might look good, can certainly be changed. I've currently added incremental static generation support Edit: Updated screenshot after 8037981 ![Screenshot 2020-08-04 at 1 51 14 PM](https://user-images.githubusercontent.com/11258286/89270960-afe9f400-d659-11ea-8f18-197dc53b8beb.png) Fixes: #14204
-
由 Jonathan G 提交于
Co-authored-by: NTim Neutkens <timneutkens@me.com> Co-authored-by: NJJ Kasper <jj@jjsweb.site>
-
由 Prateek Bhatnagar 提交于
- Fixes the serverless build for font optimizations
-
由 Kristóf Poduszló 提交于
Add missing nomodule polyfills and suggest using features only up to ES2019 for browser compatibility (#15772) These changes aim to resolve most of the concerns raised in #15756. It adds missing polyfills for legacy browsers up until ES2019: - Number.{parseFloat,parseInt} - ~Math.{acosh,asinh,atanh,cbrt,clz32,cosh,expm1,fround,hypot,imul,log10p,log1p,log2,sign,sinh,tanh,trunc}~ _[Removed as these are [not widely used](https://github.com/vercel/next.js/pull/15772#discussion_r463957931)]_ - While these may seem to weigh a lot, they barely add 1 kB to the resulting bundle: <img width="492" alt="gzip: 32 kB vs. 30.9 kB, Brotli: 28.8 kB vs. 27.8 kB" src="https://user-images.githubusercontent.com/14854048/89100961-1376e600-d3fc-11ea-90fd-3e6632b70220.png"> - ~Object.fromEntries~ _[Removed as [it's rarely used in user code](https://github.com/vercel/next.js/pull/15772#discussion_r463984612)]_ Also, the following features are now supported with build-time transforms: - ~`globalThis` (gets transformed into `window` in browser environments)~ _[Removed as it [could break existing applications](https://github.com/vercel/next.js/pull/15772#discussion_r463956269)]_ - `export * as ns from 'module'` The suggested TypeScript library version has been set to ES2018, so the features below become unavailable in type-checked files (they're not evenly supported by module-compatible browsers, either): - Object.fromEntries - String.prototype.matchAll - String.prototype.replaceAll - Promise.any + AggregateError - WeakRef As for the `import.meta` support, [webpack v5 seems to fix that](https://github.com/webpack/webpack/pull/11075), so it should eventually become an issue of the past. --- Fixes #15756
-
由 Joe Haddad 提交于
-
由 Joe Haddad 提交于
-
- 03 8月, 2020 6 次提交
-
-
由 Tim Neutkens 提交于
Same as #15483 but couldn't push to it --- Closes #15483 Fixes #15828
-
由 Jan Potoms 提交于
In terms of url rewriting, `trailingSlash` supports everything `exportTrailingSlash` does. We can just share all other code paths and deprecate `exportTrailingSlash`. This PR shows a deprecation warning when `exportTrailingSlash` is used. Also fixes https://github.com/vercel/next.js/issues/15774 We can update the tests now or later. (I kept them the same to prove it's non-breaking) To do: - [x] Do we want to keep this? => nope https://github.com/vercel/next.js/blob/841d4efc517a379d8947f491e3c6a1c4784bbccf/packages/next/next-server/lib/router/router.ts#L329 - [x] I kept `exportTrailingSlash` here. Do we want to rename that as well? => nope https://github.com/vercel/next.js/blob/2d9d649d492b77adeddea0242ab6b7fe73d18079/packages/next/build/index.ts#L959
-
由 Tim Neutkens 提交于
- Use latest terser version (still 1 warning in the stable version which is an open PR) - Add emitOnErrors instead of noEmitOnErrors - Added trace-deprecations for Next.js core development
-
由 Tim Neutkens 提交于
- Using `namedChunks` where possible, this will also allow for faster access to the chunks as we no longer have to look them up like we did before using `find` - Using the new asset hooks introduced in the latest webpack beta - Using the new externals function signature
-
由 Joe Haddad 提交于
-
由 JJ Kasper 提交于
Adds additional test cases for cascading env values and corrects behavior Fixes: https://github.com/vercel/next.js/issues/15744
-
- 02 8月, 2020 1 次提交
-
-
由 Jan Potoms 提交于
-
- 01 8月, 2020 3 次提交
-
-
-
由 Joe Haddad 提交于
-
由 Jan Potoms 提交于
Irrelevant since https://github.com/vercel/next.js/pull/15379
-
- 31 7月, 2020 2 次提交
-
-
由 Rafau 提交于
I think this is necessary for IE11. via [Webpack docs](https://webpack.js.org/migrate/5/#turn-off-es2015-syntax-in-runtime-code-if-necessary) > By default, webpack's runtime code uses ES2015 syntax to build smaller bundles. If your build targets environments that don't support this syntax (like IE11), you'll need to set output.ecmaVersion: 5 to revert to ES5 syntax. Thank you
-
由 Jan Potoms 提交于
Caught this while reviewing router code for https://github.com/vercel/next.js/pull/15710
-
- 30 7月, 2020 6 次提交
-
-
由 Joe Haddad 提交于
Fixes #15668
-
由 Arsalan Khattak 提交于
-
由 JJ Kasper 提交于
`pageProps` should always be defined to ensure everything is working as expected although to prevent a breaking change this adds an additional check before attempting to access `pageProps` before hydration. It also adds tests to prevent regressing on this Closes: https://github.com/vercel/next.js/issues/15647
-
由 Joe Haddad 提交于
-
由 Joe Haddad 提交于
-
由 Joe Haddad 提交于
-