- 08 7月, 2020 9 次提交
-
-
由 Darsh Patel 提交于
-
由 Christian Alfoni 提交于
-
由 Gianmarco 提交于
Hi, we received some issues on the `react-three-fiber` and `drei` repos, mentioning broken ssr because of some examples where we import three's examples - like to implement loaders or controls. This PR adds a next.config suggested by many that transpiles everything in three, drei and postprocessing. I also added some code from `drei` that shows how controls and effects can be easily added.
-
由 Ben Botvinick 提交于
-
由 Arsalan Khattak 提交于
-
由 Christian Alfoni 提交于
Fix key warning
-
由 Christian Alfoni 提交于
Fix key warning
-
由 Christian Alfoni 提交于
-
由 Christian Alfoni 提交于
-
- 07 7月, 2020 9 次提交
-
-
由 Tomasz Tunik 提交于
Preview of existing posts should always return the latest revision so DESC sorting was required. Otherwise, it would always return the oldest revision. Tested against latest Wordpress and GraphQL plugins on drafts, published, and edited but unpublished changes. The example works great!
-
由 Joe Haddad 提交于
-
由 Ty Mick 提交于
Co-authored-by: NJoe Haddad <timer150@gmail.com> Co-authored-by: NJoe Haddad <joe.haddad@zeit.co>
-
由 Jan Potoms 提交于
Discovered while working on https://github.com/vercel/next.js/pull/14848 when asPath is the same but href is different it should use `replaceState` instead of `pushState`, so that browser back/forward behavior is preserved. Currently it's comparing a path that includes basepath with one that excludes it, so `pushState` is always used. This makes sure the behavior is the same as when running next.js without a basepath
-
由 Ben Botvinick 提交于
Co-authored-by: NTim Neutkens <tim@timneutkens.nl>
-
由 Jan Potoms 提交于
Currently following links are broken when using `basePath`: ```jsx // pages/hello.js <Link href="#hashlink"> <a id="hashlink">Hash Link</a> </Link> ``` with `basePath: '/docs'`, this will navigate to `/docs/docs/hello#hashlink` instead of `/docs/hello#hashlink` I have a further optimization that builds on this branch that removes `url.parse` and `url.resolve` in favor for `new URL()` in router and link. Will PR when this gets merged.
-
由 Christian Alfoni 提交于
-
由 James Mosier 提交于
Fast Refresh doesn't appear to work with older version (16.8.x) versions of React. I was able to reproduce this via this issue https://github.com/vercel/next.js/issues/14895 I updated all examples I found of React `16.8.x` to `^16.13.1` so that future installs will auto bump to the latest minor version. Previously the pinned version was causing the lock of version.
-
由 Asher Foster 提交于
Co-authored-by: NJoe Haddad <timer150@gmail.com> Co-authored-by: NTim Neutkens <timneutkens@me.com>
-
- 06 7月, 2020 4 次提交
-
-
由 JJ Kasper 提交于
This updates the scroll position saving to occur as the scroll position changes instead of trying to do it when the navigation is changing since the `popState` event doesn't allow us to update the leaving history state once the `popState` has occurred. The order of events that was previously attempted to save scroll position on a `popState` event (back/forward navigation) 1. history.state is already updated with state from `popState` 2. we replace state with the currently rendered page adding scroll info 3. we replace state again with the `popState` event state overriding scroll info Using this approach the above event order is no longer in conflict since we don't attempt to populate the state with scroll position while it's leaving the state and instead do it while it is still the active state in history This approach resembles existing solutions: https://www.npmjs.com/package/scroll-behavior https://twitter.com/ryanflorence/status/1029121580855488512 Fixes: https://github.com/vercel/next.js/issues/13990 Fixes: #12530 x-ref: https://github.com/vercel/next.js/pull/14075
-
由 Tim Neutkens 提交于
Fixes #14452
-
由 Tim Neutkens 提交于
Fixes #14453
-
由 Tim Neutkens 提交于
-
- 05 7月, 2020 1 次提交
-
-
由 matamatanot 提交于
-
- 04 7月, 2020 1 次提交
-
-
由 Tom Dohnal 提交于
This resolves https://github.com/vercel/next.js/issues/12713 and https://github.com/vercel/next.js/issues/12722
-
- 03 7月, 2020 3 次提交
-
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
Co-authored-by: NJoe Haddad <timer@zeit.co> Co-authored-by: NJoe Haddad <joe.haddad@zeit.co>
-
由 Darsh Patel 提交于
Fixes: #13512 Defined and exported type for `metric` used in [reportWebVitals](https://nextjs.org/docs/advanced-features/measuring-performance) ``` export function reportWebVitals(metric) { if (metric.label === 'custom') { console.log(metric) // The metric object ({ id, name, startTime, value, label }) is logged to the console } } ``` One can now do ``` import { NextWebVitalsMetric } from 'next/app' export function reportWebVitals(metric: NextWebVitalsMetric ) { if (metric.label === 'custom') { console.log(metric) // The metric object ({ id, name, startTime, value, label }) is logged to the console } } ```
-
- 02 7月, 2020 5 次提交
-
-
由 JJ Kasper 提交于
Co-authored-by: Nkodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
由 Jan Potoms 提交于
Convert `Link` to a function component. Prefetch logic and memoized url formatting now meshes nicely with React hooks. Class methods were hoisted to module scope to preserve performance characteristics.
-
由 JJ Kasper 提交于
Since the no-op rewrite is a valid rewrite used to check pages/assets before adding a 404-rewrite this makes sure we don't show the rewriting to auto-export dynamic pages warning from it Closes: https://github.com/vercel/next.js/issues/14736
-
-
由 Tim Neutkens 提交于
-
- 01 7月, 2020 7 次提交
-
-
由 Tim Neutkens 提交于
Webpack 5 supports a single runtimechunk for the Node.js compilation, this solves sharing modules between entrypoints.
-
由 Tim Neutkens 提交于
Fixes #11711 Also cleaned up some extra code. This was already supported on the Vercel edge network.
-
由 Lindsey Simon 提交于
Fix CSS `display` on login link.
-
由 muslax 提交于
-
由 JJ Kasper 提交于
-
由 JJ Kasper 提交于
This makes sure to base64 encode the `.env*` file contents before passing them in the URL for the serverless-loader since `!` is a special character in this case which can cause webpack to fail to build Closes: https://github.com/vercel/next.js/issues/14749
-
由 Luis Alvarez D 提交于
Updated the example to use server only variables inside `getStaticProps`
-
- 30 6月, 2020 1 次提交
-
-
由 Joe Haddad 提交于
-