- 11 7月, 2020 1 次提交
-
-
由 Steph Query 提交于
Sorry if I'm mixed up here. Was trying to install this and realized the folder is just `/with-emotion`. Guessing this was merged to overwrite the pre-v10 example project.
-
- 10 7月, 2020 4 次提交
-
-
由 JJ Kasper 提交于
This makes sure we don't add an undefined query value for auto-export pages for auto-export pages unnecessarily Fixes #15023
-
由 Cristian Dominguez 提交于
Fix #14902 I created a separated helper that wraps `fs.promises.mkdir` and sets `recursive` option to `true` by default. I'm not sure if this is the right approach (maybe it should just call `fs.promises.mkdir` from `create-app.ts`?), any thoughts?
-
由 Ricky Abell 提交于
Download instructions in examples/with-next-auth/README.md currently fail because they refer to next-auth instead of with-next-auth.
-
由 Tim Neutkens 提交于
-
- 09 7月, 2020 11 次提交
-
-
由 Cristian Dominguez 提交于
Co-authored-by: NCristian Dominguez <cristiand391@users.noreply.github.com>
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
Co-authored-by: NTobias Koppers <sokra@users.noreply.github.com>
-
由 Tim Neutkens 提交于
Co-authored-by: NZack Jackson <zackary.l.jackson@gmail.com>
-
由 Darsh Patel 提交于
Removed Option to enable `ReactProductionProfiling` from configuration and added a CLI switch for the same. Users can now do `next build --profile` to enable react production profiling. Also added a warning to notify users about the performance impact Fixes: #14688
-
由 Oskar 提交于
Co-authored-by: NTim Neutkens <tim@timneutkens.nl> Co-authored-by: Nkodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
由 JP Lew 提交于
There is a bug in the cms-wordpress example due to a Wordpress plugin dependency. After running `npm install`, then either `npm run dev` or `npm run build`, the following errors appear in the console: ```shell > cms-wordpress@1.0.0 dev /Users/jplew/Sites/projects/next.js/examples/cms-wordpress > next ready - started server on http://localhost:3000 info - Loaded env from /Users/jplew/Sites/projects/next.js/examples/cms-wordpress/.env.local event - compiled successfully event - build page: / wait - compiling... event - build page: /next/dist/pages/_error event - compiled successfully [ { message: 'Cannot query field "name" on type "NodeWithAuthorToUserConnectionEdge". Did you mean "node"?', extensions: { category: 'graphql' }, locations: [ [Object] ] }, { message: 'Cannot query field "firstName" on type "NodeWithAuthorToUserConnectionEdge".', extensions: { category: 'graphql' }, locations: [ [Object] ] }, { message: 'Cannot query field "lastName" on type "NodeWithAuthorToUserConnectionEdge".', extensions: { category: 'graphql' }, locations: [ [Object] ] }, { message: 'Cannot query field "avatar" on type "NodeWithAuthorToUserConnectionEdge".', extensions: { category: 'graphql' }, locations: [ [Object] ] } ] Error: Failed to fetch API at fetchAPI (webpack-internal:///./lib/api.js:31:11) ``` The reason for this is `wp-graphql` released version v0.10.0 ten days ago which introduced a number of breaking changes (https://github.com/wp-graphql/wp-graphql/releases/tag/v0.10.0). Specifically, this is the change that breaks the current example: > - One to One relationships are now nested. For example post.author and post.featuredImage now return an edge/node instead of the node directly. More info about this change can be found here: https://github.com/wp-graphql/wp-graphql/issues/347#issuecomment-639071772 After my changes, `npm run dev` and `npm run build` succeed without errors.
-
由 illuminist 提交于
https://github.com/vercel/next.js/issues/14969 It didn't specify on how to include the config with function config. This PR clarify the way to use the config with function.
-
-
由 JJ Kasper 提交于
-
由 JJ Kasper 提交于
This adds additional checks against the routeKeys used to build the named regexes for dynamic routes to ensure they follow PCRE rules for named capture groups x-ref: https://github.com/vercel/vercel/pull/4813
-
- 08 7月, 2020 11 次提交
-
-
由 Luis Alvarez D 提交于
Fixes #14792 Closes #14814 The project id is currently used by Sanity's image builder, which is used in a React component. @maybac It was faster for me to create a new PR but the credit goes to you, thank you!.
-
由 Darsh Patel 提交于
-
由 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 提交于
-