- 15 7月, 2020 2 次提交
-
-
由 Joe Haddad 提交于
This PR corrects the data fetching behavior for optional root routes. --- Fixes #14923
-
由 Joe Haddad 提交于
-
- 14 7月, 2020 12 次提交
-
-
由 Lukas Polak 提交于
Use hooks with jss
-
由 Jesse Jafa 提交于
This should close https://github.com/vercel/next.js/issues/12964 but I'm leaving it up to one of the Tims (or if there are other maintainers) to close the issue as they see fit.
-
由 Jan Potoms 提交于
Co-authored-by: NJoe Haddad <joe.haddad@zeit.co>
-
由 Luis Alvarez D 提交于
Co-authored-by: NShu Uesugi <shu@chibicode.com> Co-authored-by: NJoe Haddad <joe.haddad@zeit.co>
-
由 JJ Kasper 提交于
Follow-up to https://github.com/vercel/next.js/pull/15041 this updates the documentation for custom-routes to mention `basePath` handling with them
-
由 abhik-b 提交于
UPDATE I ADDED: setUser() AFTER REMOVING cookie IN return STATEMENT OF logout ARROW FUNCTION There might be some cases where you do not want to redirect users after logout rather let them remain in that same page BUT let them know they have logged out by some UI changes . For that cases you might need the 'user' hook to update when users logs out . CURRENTLY the 'user' hook DOES NOT UPDATE AUTOMATICALLY when the user logs out . PAGE REFRESH NEEDED to update that. So i propose that we might add setUser() to update user so that user never returns true until user is set some value again
-
由 Darsh Patel 提交于
-
由 Joe Haddad 提交于
-
由 Jan Potoms 提交于
edge-case I introduced in https://github.com/vercel/next.js/pull/14827
-
由 Joe Haddad 提交于
We've added a Babel warning for unnamed default exports, and this PR addresses the remaining points in #13024. Fixes #13024
-
由 Tim Neutkens 提交于
-
由 Jan Potoms 提交于
Replace `url.parse` and `url.resolve` logic with whatwg `URL`, Bring in a customized `format` function to handle the node url objects that can be passed to router methods. This eliminates the need for `url` (and thus `native-url`) in core. Looks like it shaves off about 2.5Kb, according to the `size-limits` integration tests.
-
- 13 7月, 2020 8 次提交
-
-
由 Jan Potoms 提交于
Fixes https://github.com/vercel/next.js/issues/14757 Since https://github.com/vercel/next.js/pull/15041 has been sorted out, this can now be fully fixed There was also a bug in the dev server that causes redirect loops
-
由 Jan Potoms 提交于
It should be enough to encode the characters that `path-to-regexp` uses as path delimiters (`/#?`). Fixes https://github.com/vercel/next.js/issues/14691
-
由 Jason Miller 提交于
/cc @cristianbote
-
由 Anthony Morris 提交于
The TypeScript blog starter didn't have `.next` in the `.gitignore` file.
-
由 Tim Neutkens 提交于
Related to #14997
-
由 Jens Meindertsma 提交于
Co-authored-by: NJoe Haddad <timer150@gmail.com> Co-authored-by: Nkodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com> Co-authored-by: NJoe Haddad <joe.haddad@zeit.co>
-
由 JJ Kasper 提交于
This adds handling for custom-routes with `basePath` to automatically add the `basePath` for custom-routes `source` and `destination` unless `basePath: false` is set for the route. Closes: https://github.com/vercel/next.js/issues/14782
-
由 Ashik Paul 提交于
-
- 12 7月, 2020 3 次提交
-
-
由 Joe Haddad 提交于
Fixes #14888
-
由 Tim Neutkens 提交于
Found while working on figuring out this bug: https://twitter.com/timneutkens/status/1282129714627448832 I noticed that the node_modules got passed by the ignore still because when chokidar identifies a ignore pattern is a glob it treats the glob as-is instead of appending `/**` to the glob
-
由 Ashik Paul 提交于
-
- 11 7月, 2020 4 次提交
-
-
由 Cristian Bote 提交于
* (chore) Add with-goober as an example * (chore) Added better documentation * Updated package json Co-authored-by: NLuis Alvarez <luis@vercel.com>
-
由 George Arthur 提交于
This is to further give more insight on one of the ways to fix prerendering errors especially with dynamic pages.
-
由 Eric Goerens 提交于
-
由 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 7 次提交
-
-
由 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.
-