- 05 9月, 2020 2 次提交
-
-
由 Joe Haddad 提交于
-
由 JJ Kasper 提交于
This makes sure we only pass the as value's `pathname` instead of the full value so that we don't accidentally include `query` values while resolving the rewrites. This also adds tests to ensure the rewrites are resolved with the correct query values when only providing `href` and when manually mapping them with `href` and `as` Fixes: https://github.com/vercel/next.js/issues/16825
-
- 04 9月, 2020 3 次提交
-
-
由 JJ Kasper 提交于
-
由 JJ Kasper 提交于
This corrects detecting of invalid page config exports and adds additional test cases for non-invalid config import/exports Closes: https://github.com/vercel/next.js/issues/16775
-
由 Jan Potoms 提交于
Alternative to https://github.com/vercel/next.js/pull/16798
-
- 03 9月, 2020 4 次提交
-
-
由 JJ Kasper 提交于
This is a follow-up to https://github.com/vercel/next.js/pull/16744 which shows the build/activity indicator while the data is being re-fetched to let the user know the re-fetching is occurring Closes: https://github.com/vercel/next.js/issues/16790
-
由 Joe Haddad 提交于
-
由 JJ Kasper 提交于
This adds initial support for reloading the page when `getStaticProps`, `getStaticPaths`, or `getServerSideProps` were changed for a page by triggering a reload when the server output for a page has changed but the client output has not since these methods aren't included in the client output. Closes: https://github.com/vercel/next.js/issues/13949
-
由 JJ Kasper 提交于
This corrects/makes sure interpolating dynamic route values for `href` works correctly. This provides an alternative approach to building the `href` value with `next/link` so that you don't need to worry about encoding the params manually. Closes: https://github.com/vercel/next.js/issues/13473 Closes: https://github.com/vercel/next.js/issues/14959 Closes: https://github.com/vercel/next.js/issues/16771
-
- 02 9月, 2020 10 次提交
-
-
由 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.
-
由 Joe Haddad 提交于
-
由 Alex Castle 提交于
This is a small change to the image post-processor logic. When it's looking for images to preload, it will now ignore SVGs, as these are rarely the relevant images for LCP.
-
由 Joe Haddad 提交于
-
由 Joe Haddad 提交于
-
由 Joe Haddad 提交于
-
由 Joe Haddad 提交于
-
由 Arthur 提交于
* feat Export return type for GetStaticPaths * add Duplicate generic Co-authored-by: NLuis Alvarez D <luis@vercel.com>
-
由 Joe Haddad 提交于
-
- 01 9月, 2020 1 次提交
-
-
由 Joe Haddad 提交于
-
- 30 8月, 2020 1 次提交
-
-
由 TMQ 提交于
The [finally-polyfill](https://gist.github.com/developit/d970bac18430943e4b3392b029a2a96c) did not expose any values. ![image](https://user-images.githubusercontent.com/15967520/91409583-2f916a00-e878-11ea-86d0-189966ceb83c.png)
-
- 28 8月, 2020 1 次提交
-
-
由 Jan Potoms 提交于
This is not needed anymore since absolute urls are supported. Also added an extra test for `mailto:` urls
-
- 27 8月, 2020 4 次提交
-
-
由 Joe Haddad 提交于
-
由 Joe Haddad 提交于
-
由 Joe Haddad 提交于
-
由 Joe Haddad 提交于
This pull request replaces our client-side style transitions with `<style>` tags over async `<link rel=stylesheet>` tags. This should fix some edge cases users see with Chrome accidentally causing a FOUC. This also removes the need to perform an async operation before starting the render, which should remove any perceivable navigation delay. --- Fixes #16289
-
- 25 8月, 2020 5 次提交
-
-
由 Joe Haddad 提交于
-
由 Joe Haddad 提交于
This pull request reuses existing `<link rel=stylesheet>` tags if their `href` matches instead of recreating it. This is in effort to fix an edge case where the browser will FOUC on the tag swap. This behavior should be sufficiently covered by all the existing CSS cases, as misbehavior would result in the resulting CSS styles being incorrect.
-
由 Tim Neutkens 提交于
-
由 Jared Palmer 提交于
Changes the name of the environment variable to `NEXT_PUBLIC_GA_TRACKING_ID`
-
由 Tim Neutkens 提交于
When the webpack 5 beta is used disk caching will be automatically enabled to improve incremental build performance.
-
- 24 8月, 2020 5 次提交
-
-
由 Joe Haddad 提交于
-
由 khades 提交于
To prevent FOUC, discussed in #10557 i need to store information about css file dependencies for chunk. Right now current implementation just throws away everything but js. Can there be more than one css file in chunk? If no - code will be simplified. closes #10557
-
由 Luis Alvarez D 提交于
Fixes https://github.com/vercel/next.js/issues/16495 Terminal: ![image](https://user-images.githubusercontent.com/4278345/90984442-96421b00-e53a-11ea-9939-44b00cba87cf.png) Browser: ![image](https://user-images.githubusercontent.com/4278345/90984456-a9ed8180-e53a-11ea-86da-d9f28e9c2fdd.png) The link https://nextjs.link/codemod-ndc used for the warning links to a currently 404 docs page, that will be available in the next stable release. Tests not added as the warning has tests already.
-
由 JJ Kasper 提交于
If a custom `_document` is added but not all of the expected document components are rendered it can cause unintended errors as noticed in https://github.com/vercel/next.js/issues/10219 so this adds detecting when one of the expected document components isn't rendered and shows an error. Closes: https://github.com/vercel/next.js/issues/10219
-
由 Tim Neutkens 提交于
Handles: - Next.js version - next.config.js `env` key - `NEXT_PUBLIC_` prefixed environment variables - next.config.js keys that affect performance Ideally we don't invalidate the whole cache when `NEXT_PUBLIC_` / `env` key variables change, but this is just to initially make the caching reliable, this behavior is similar to the current webpack 4 behavior, so it can only be improved
👍
-
- 23 8月, 2020 2 次提交
-
-
由 JJ Kasper 提交于
This fixes invalid initial route params in development mode and serverless production mode. It also adds tests to ensure these values are correct in development, production, and serverless mode. x-ref: https://github.com/vercel/next.js/pull/16084 Fixes: https://github.com/vercel/next.js/issues/16481 Fixes: https://github.com/vercel/next.js/issues/16482
-
由 JJ Kasper 提交于
When navigating from a non-shallow page to a page that was navigated to shallowly in history it causes incorrect page data to be shown since an incorrect shallow navigation is done. We can only maintain shallow routing when the current page was navigated to shallowly and the page being navigated to in history was also navigated to shallowly. Additional tests to ensure this behavior is working has also been added. Closes: https://github.com/vercel/next.js/issues/7395 Closes: https://github.com/vercel/next.js/issues/14928 Fixes: https://github.com/vercel/next.js/issues/16028
-
- 22 8月, 2020 2 次提交
-
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
-