- 29 8月, 2020 2 次提交
-
-
由 Daniel Eden 提交于
This change adds a new example, `with-mdx-remote`, which leverages [`next-mdx-remote`](https://github.com/hashicorp/next-mdx-remote) to use MDX files as content for a dynamic route. In addition to the basic functionality, the example adds a note about somewhat advanced usage that allows the use of conditionally-loaded custom MDX components. cc @jescalan
-
由 Sam Robbins 提交于
Allows people to more easily find how to style active links if they are wanting to
-
- 28 8月, 2020 4 次提交
-
-
由 Jan Potoms 提交于
This is not needed anymore since absolute urls are supported. Also added an extra test for `mailto:` urls
-
由 Rich Paret 提交于
* Include yarn instructions Yarn seems like it's encouraged elsewhere (such as in create-next-app docs), so adding this to clarify it's supported here. * Added to a similar case Co-authored-by: NLuis Alvarez D <luis@vercel.com>
-
由 Vic Vijayakumar 提交于
Updated `examples/with-tailwindcss` to the newest TailwindCSS, and opted in to future-facing breaking changes. Also created a jsconfig.json so that files can be imported without traversing up relative paths.
-
由 Long Ho 提交于
Changes: - Migrate to TypeScript. `react-intl` natively supports TypeScript now. - Upgrade corresponding `formatjs` packages. - Dynamically polyfill Intl API per locale since those polyfills are huge. - Migrate to recommended workflow per https://formatjs.io/docs/getting-started/application-workflow
-
- 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
-
- 26 8月, 2020 1 次提交
-
-
由 JJ Kasper 提交于
This adds tests to ensure preview mode pages aren't cached and made publicly available or written to the disk. Closes: https://github.com/vercel/next.js/issues/16020
-
- 25 8月, 2020 10 次提交
-
-
由 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.
-
由 Joe Haddad 提交于
-
由 Tim Neutkens 提交于
-
由 Jared Palmer 提交于
Changes the name of the environment variable to `NEXT_PUBLIC_GA_TRACKING_ID`
-
由 Hyeon Kim (김지현) 提交于
styled-components requires 'react-is' as a peerDependency ###### Reference - https://github.com/styled-components/styled-components/blob/b19d17f/packages/styled-components/package.json#L78
-
由 Christian Pena Valerio 提交于
Take care of the other links that aren't working while browsing github. Related to: #16505
-
由 Luis Alvarez D 提交于
Should be able to help with: https://github.com/vercel/next.js/discussions/16530
-
由 Ondřej Chrastina 提交于
Hello everyone! I would like to add the example using [Kentico Kontent](https://kontent.ai) as a data source for your example. I have tried to be consistent with the other examples and showcase the preview as well. I have tried to keep up with [Contribution guidelines](https://github.com/vercel/next.js/blob/canary/contributing.md#adding-examples). Thank you.
-
由 Tim Neutkens 提交于
When the webpack 5 beta is used disk caching will be automatically enabled to improve incremental build performance.
-
- 24 8月, 2020 9 次提交
-
-
由 Christian Pena Valerio 提交于
-
由 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
-
由 Luis Alvarez D 提交于
Fixes https://github.com/vercel/next.js/issues/16502 Check the issue for more details.
-
由 WeichienHung 提交于
Fix https://github.com/vercel/next.js/issues/16197 See my screenshot. Testing url is changed to http://localhost:3000/test and can find the source map. <img width="826" alt="圖片" src="https://user-images.githubusercontent.com/1462027/90737991-d74eeb00-e300-11ea-9675-f25aef6a4062.png">
-
由 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
👍 -
由 Luis Alvarez D 提交于
@Timer This example seems to not be needed anymore
-
- 23 8月, 2020 5 次提交
-
-
由 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
-
由 sharils 提交于
* Document req and res * lint fix Co-authored-by: NLuis Alvarez <luis@vercel.com> Co-authored-by: Nkodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
由 JJ Kasper 提交于
* Add version note to path aliases docs * Update docs/advanced-features/module-path-aliases.md Co-authored-by: NLuis Alvarez D <luis@vercel.com>
-
由 Diego Gennaro 提交于
* nextjs with unsplash initial commit * update demo link * remove isomorphic-unfetch * remove ssr on collection page * fix style issues * fix import/no-anonymous-default-export * usign fetch instead of request * remove credits * improve instructions * improve instructions * Updated readme steps and images * Updated readme * Updated gitignore Co-authored-by: NLuis Alvarez <luis@vercel.com>
-
- 22 8月, 2020 5 次提交
-
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
-
由 Joe Haddad 提交于
This pull request correctly tracks render cancelation behavior. Prior to this PR, we'd have an unhandled rejection that left the app in a bad state and no routeChangeError event was fired. --- Closes #16424 Fixes #16445
-
由 JJ Kasper 提交于
This makes sure to also check if a dynamic route matched after resolving a rewrite on the client to match behavior on the server. It also adds tests for this behavior to ensure it is working properly. Fixes: https://github.com/vercel/next.js/issues/16454
-
由 Joe Haddad 提交于
-