- 14 1月, 2019 6 次提交
-
-
由 Tim Neutkens 提交于
-
由 Alexander Nanberg 提交于
* Revert #6030 * Fix _app childContextTypes
-
由 Tim Neutkens 提交于
For some reason one test inconsistently failed.
-
由 Alexander Nanberg 提交于
Continuation of #5945
-
由 Tim Neutkens 提交于
* Remove next/asset Reasoning described in #5970 * Remove next/asset tests * Bring back asset-page
-
由 Peter Kellner 提交于
small spelling correction
-
- 12 1月, 2019 8 次提交
-
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
-
由 Connor Davis 提交于
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
-
由 tangye 提交于
original code in `/lib/router/router.js` ``` urlIsNew (pathname, query) { return this.pathname !== pathname || !shallowEquals(query, this.query) } ``` the urlIsNew compare `this.pathname` to an argument `pathname` the invokers: ``` // If asked to change the current URL we should reload the current page // (not location.reload() but reload getInitialProps and other Next.js stuffs) // We also need to set the method = replaceState always // as this should not go into the history (That's how browsers work) if (!this.urlIsNew(asPathname, asQuery)) { method = 'replaceState' } ``` the parameter here is `asPathname` destructured from `asPath` so here is a problem when we reuse a single page rendered in two asPaths pages/a.js ``` <> <Link href='/a'><a>goto a</a></Link> <Link href='/a' as='/b'><a>goto b</a></Link> </> ``` If we navigate to page /a, then click 'goto b', actually the history is replaced, not pushed. It is expected that history could be correctly pushed and popped as long as the browser url is changed. -
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
Because next-routes requires APIs outside of compilation we have to compile these Fixes https://github.com/fridays/next-routes/issues/274 Fixes #6017
-
- 11 1月, 2019 7 次提交
-
-
由 Alexander Nanberg 提交于
Fixes parts of #5716. I had some issues with the test suite but I'm fairly certain that I got it working correctly.
-
由 astenmies 提交于
-
由 Tim Neutkens 提交于
It’s an inconsistent result, users should use ctx instead. At a later time we’ll normalize the properties passed into _app.js its getInitialprops to be consistent with pages.
-
由 Isaac Hinman 提交于
Fixes #6026
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
-
- 10 1月, 2019 1 次提交
-
-
由 Jayden Seric 提交于
This PR fixes the buggy `Head.propTypes` here: https://github.com/zeit/next.js/blob/v8.0.0-canary.3/packages/next-server/lib/head.js#L107 Currently, `Head.propTypes` allows one child node like this: ```jsx import Head from 'next/head' // … <Head> <title>Title</title> </Head> ``` But more than one child node mistakenly causes a prop type error like this: ```jsx <Head> <title>Title</title> <meta name="description" content="Description." /> </Head> ``` ``` Warning: Failed prop type: Invalid prop `children` supplied to `Head`. ```
-
- 09 1月, 2019 4 次提交
-
-
由 Jayden Seric 提交于
Adds an example with [`graphql-react`](https://github.com/jaydenseric/graphql-react), using [`next-graphql-react`](https://github.com/jaydenseric/next-graphql-react). [`graphql-react`](https://github.com/jaydenseric/graphql-react) is a lightweight but powerful [GraphQL](https://graphql.org) client for React; the first [Relay](https://facebook.github.io/relay) and [Apollo](https://apollographql.com/docs/react) alternative with server side rendering.
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
* Remove unused argument * Replace pages-plugin with loader * Add loader-utils types * Remove logs * Bring back previous deposal behavior * Remove console.log * Remove webpack/utils as it’s no longer in use * Remove hot-self-accept-loader * Error Recovery tests * Make hotSelfAccept a noop default loader * Fix windows deleted/added * Remove logging * Remove unused variables * Remove log * Simplify entrypoint generation * Don’t return the function * Fix _app test * Remove code that’s always true * Move aliases to constants * Use alias * Join pages alias in reduce * Default pages differently * Loop over pages instead of manually defining * Move entry generation into common function * Update packages/next/build/webpack/loaders/next-client-pages-loader.ts Co-Authored-By: Ntimneutkens <tim@timneutkens.nl> * Update packages/next/build/webpack/loaders/next-client-pages-loader.ts -
由 Peter Kellner 提交于
The current TypeScript "with-typescript" looks like it was put there as a place holder. I'm fairly new to TypeScript but I'm sure the changes I've made here will be a huge improvement. Open to suggestions and to update as appropriate. Also, Tried to run yarn lint --fix to no avail. I can't figure out how to get it to find lint whether I'm running on my mac or PC. I tried lots of variations around npm i lint -g but had no success. (#6011)
-
- 07 1月, 2019 2 次提交
-
-
由 Zack Tanner 提交于
Enables SSR for styled-components babel-plugin to prevent HTML attribute mismatch warnings during rehydration.
-
由 Zack Tanner 提交于
-
- 06 1月, 2019 2 次提交
-
-
由 tylim 提交于
improve the example so that it can preserve unstated from server to client unstated
-
由 Luc 提交于
It looks like : ``` Pages sizes after gzip: ┌ / (196 B) ├ /_app (11.5 kB) ├ /_error (4.44 kB) ├ /blog (196 B) └ /blog/page (195 B) ``` (style inspired from now-cli : https://github.com/zeit/now-cli/blob/canary/src/util/output/builds.js) I'll add dynamic chunks in a separate PR. @timneutkens Do you want to keep `_app` and `_error` or filter them out ? I think it's a good idea to keep them, because `_app` can get pretty large and it would encourage code splitting in that case.
-
- 05 1月, 2019 4 次提交
-
-
由 Juan Olvera 提交于
I wrote a [script](https://github.com/j0lv3r4/dependency-version-updater) to update dependencies recursively in `package.json` files, e.g.: ``` $ node index.js --path="./examples" --dependencies="react=^16.7.0,react-dom=^16.7.0" ``` This PR contains the result against the examples folder.
-
由 Juan Olvera 提交于
I changed the version to the following files: - [x] - examples/with-next-css/package.json - [x] - examples/with-draft-js/package.json - [x] - examples/custom-server-polka/package.json - [x] - examples/with-cerebral/package.json - [x] - examples/with-zones/package.json - [x] - examples/with-universal-configuration-runtime/package.json - [x] - examples/with-apollo/package.json - [x] - examples/with-higher-order-component/package.json - [x] - examples/with-hashed-statics/package.json - [x] - examples/with-pkg/package.json - [x] - examples/with-jest/package.json - [x] - examples/with-glamorous/package.json - [x] - examples/with-custom-reverse-proxy/package.json - [ ] - examples/with-emotion/package.json - [x] - examples/with-styled-jsx-scss/package.json - [x] - examples/with-styled-jsx-plugins/package.json `with-emotion/package.json` already has the latest, so I guess it's other packabe. BUT I think we need to update this example with the latest version of `emotion` since it changed a little bit (for better).
-
由 Luc 提交于
-
由 Luc 提交于
This PR aims at replacing next-server/lib/event-emitter.js by mitt. Fix https://github.com/zeit/next.js/issues/4908 event-emitter.js is ~400 bytes gzipped vs mitt is 200 bytes
-
- 03 1月, 2019 3 次提交
-
-
由 iceRao 提交于
* add readme * 修改中文文档，如中英文空格 * Update README-zh-CN.md 当前翻译版本为 7.0.0-canary.8 * anchor bugfix
-
由 Dima 提交于
-
由 Kévin Dunglas 提交于
-
- 02 1月, 2019 3 次提交
-
-
由 Tim Neutkens 提交于
-
由 Niklas Wagner 提交于
-
由 Tim Neutkens 提交于
-