- 11 9月, 2020 1 次提交
-
-
由 Sakito Mukai 提交于
There was a security update for node-fetch. > This is an important security release. It is strongly recommended to update as soon as possible. https://github.com/node-fetch/node-fetch/blob/master/docs/CHANGELOG.md#v261
-
- 10 9月, 2020 1 次提交
-
-
由 Joe Haddad 提交于
Fixes #10142 Fixes #11629
-
- 02 9月, 2020 1 次提交
-
-
由 JJ Kasper 提交于
Since the error overlay could be dismissed before this is resolved we need to make sure the component is still mounted before updating the state.
-
- 01 9月, 2020 1 次提交
-
-
由 Joe Haddad 提交于
-
- 22 8月, 2020 1 次提交
-
-
由 Joe Haddad 提交于
Fixes #16259 Caused by #16022 Follow up issue: #16450 This PR skips polyfilling Node modules in webpack 4 which are ignored by the `browsers` key.
-
- 21 8月, 2020 1 次提交
-
-
由 Prateek Bhatnagar 提交于
- Upgrades cssnano to 1.2.0 - Only removes whitespaces from downloaded font declarations - Disables Font optimization for AMP pages
-
- 20 8月, 2020 1 次提交
-
-
由 Tim Neutkens 提交于
-
- 19 8月, 2020 1 次提交
-
-
由 Joe Haddad 提交于
This PR replaces `prop-types-exact` (only used in this location) with manual property checking. Right now, malformed properties sent to `<Link>` are silently handled and only emit a warning in the console. This leads to confusing/unexpected errors because we try to read a value that is undefined. To fix this, we'll now throw a proper error when `<Link>` is misused. **This still isn't optimal, however, because we don't have a component stack trace we can give the user**. We're not going to be able to give the user actionable instructions until React 16.14 at a minimum. --- Fixes #13951 Fixes #16107 Closes #13962
-
- 17 8月, 2020 1 次提交
-
-
由 Sergey Rubanov 提交于
Co-authored-by: NTim Neutkens <timneutkens@me.com> Co-authored-by: Nkodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
- 14 8月, 2020 2 次提交
-
-
由 Kristoffer K 提交于
**What's the problem this PR addresses?** https://github.com/vercel/next.js/pull/16048 stopped bundling `caniuse-lite` but didn't declare it as a dependency https://github.com/yarnpkg/berry/runs/972037981?check_suite_focus=true#step:5:75 **How did you fix it?** Add `caniuse-lite` as a dependency --- cc @Timer As mentioned in https://github.com/vercel/next.js/issues/14157#issuecomment-667328984 I looked into adding a PnP e2e test but the use of the `gist` protocol stopped me from getting it to work since v2 doesn't support that yet. Would it be possible to change this to one of the supported protocols (https://yarnpkg.com/features/protocols)? https://github.com/vercel/next.js/blob/636672755004c756eefcddb5d4ccabbc1855e75a/packages/next/package.json#L208
-
由 Joe Haddad 提交于
-
- 11 8月, 2020 1 次提交
-
-
由 Sebastian Benz 提交于
See [release notes](https://github.com/ampproject/amp-toolbox/releases/tag/v2.6.0). **Highlight:** [hero images can now be server-side rendered](https://github.com/ampproject/amp-toolbox/tree/main/packages/optimizer#preloadheroimage) by annotating then with `data-hero`. This will greatly improves LCP when using large images in the first viewport. ``` <amp-img data-hero src="/hero.jpg" layout="responsive" width="640" height="480"></amp-img> ``` Also fixes #15979
-
- 10 8月, 2020 4 次提交
-
-
由 Joe Haddad 提交于
-
由 Tim Neutkens 提交于
Largely based on the code @threepointone wrote for react-codemod. Co-Authored-By: NSunil Pai <threepointone@gmail.com> Co-authored-by: NSunil Pai <threepointone@gmail.com>
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
This adds the following Node.js core polyfills only when the import is used: - `path` - `stream` - `vm` - `crypto` - `buffer` Fixes #15948 We'll have a separate issue about adding warnings for the usage of these modules in the browser, some polyfills like crypto are quite heavy and generally not needed for most applications (included accidentally through node_modules).
-
- 08 8月, 2020 1 次提交
-
-
由 Prateek Bhatnagar 提交于
Bug fix - Do not remove spaces as it might mangle font names
-
- 06 8月, 2020 3 次提交
-
-
由 Joe Haddad 提交于
-
由 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
-
由 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 1 次提交
-
-
由 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 3 次提交
-
-
由 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 提交于
-
- 03 8月, 2020 1 次提交
-
-
由 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
-
- 28 7月, 2020 5 次提交
-
-
由 Tim Neutkens 提交于
-
由 Rafael Almeida 提交于
* Add release hook * Remove release.js exported config * Add skip flag to release CLI * Use full flag name * Upgrade release * Update yarn.lock Co-authored-by: NTim Neutkens <timneutkens@me.com>
-
由 Prateek Bhatnagar 提交于
Co-authored-by: Natcastle <atcastle@gmail.com>
-
由 Tim Neutkens 提交于
-
由 Sebastian Benz 提交于
-
- 27 7月, 2020 1 次提交
-
-
由 Joe Haddad 提交于
-
- 26 7月, 2020 1 次提交
-
-
由 Jan Potoms 提交于
jest retries seem to be masking test failures, like the `auto-export` one (and maybe others). I turned it off for now. The `auto-export` test fails when retries are turned off. the output of this test failure was a bit unhelpful so I also improved it. Many tests have anonymous page functions.
-
- 25 7月, 2020 2 次提交
-
-
由 Joe Haddad 提交于
-
由 Tim Neutkens 提交于
Forces all Next.js users to have this patch installed: https://twitter.com/timneutkens/status/1282129714627448832 Huge thanks to @paulmillr and @sokra
🙏
-
- 20 7月, 2020 1 次提交
-
-
由 Bogdan Chadkin 提交于
Co-authored-by: NJoe Haddad <joe.haddad@zeit.co>
-
- 19 7月, 2020 1 次提交
-
-
由 Joe Haddad 提交于
-
- 17 7月, 2020 1 次提交
-
-
由 Tim Neutkens 提交于
Co-authored-by: Nkodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com> Co-authored-by: NJoe Haddad <joe.haddad@zeit.co>
-
- 16 7月, 2020 2 次提交
-
-
由 Joe Haddad 提交于
This replaces the `url-polyfill` package with the `core-js` version which handles more edge cases in legacy browsers. Closes #11702 Fixes #15194
-
由 Tim Neutkens 提交于
Co-authored-by: NJoe Haddad <joe.haddad@zeit.co>
-
- 15 7月, 2020 1 次提交
-
-
由 Joe Haddad 提交于
-