- 19 1月, 2019 5 次提交
-
-
由 Jason Aslakson 提交于
* Additional config options for hot reloader web socket connection * Apply suggestions from code review Accepting suggested code changes Co-Authored-By: Njaslakson <jason.aslakson@americastestkitchen.com> * updated README with websocket proxy options * Fix test / cleanup port setting * Always set proxy_path
-
由 Gary Meehan 提交于
This PR adds a basic example using [next-seo](https://www.npmjs.com/package/next-seo).
-
由 Gary Meehan 提交于
Updates to the latest version of Storybook.
-
由 Tim Neutkens 提交于
There's still a few Typescript helpers in use, but regenerator is added by Babel after this change, as it was already in the bundle it'll drop bundle sizes by quite a bit, eg _app.js becomes half the size.
-
由 James Mulholland 提交于
RE: https://github.com/zeit/next.js/issues/4587, this pull request improves the with-segment example. Previously, only SSR page loads were tracked. This pull request adds manual page view logging via `Router.events.on('routeChangeComplete')` in `Page.js`. There is also a minor bug fix on the textarea to remove a console error.
-
- 18 1月, 2019 6 次提交
-
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
-
由 Connor Davis 提交于
`react-is` isn't used in production, so we shouldn't bundle it. Note: most of those plugins are using the `dev` variable, but in case someone runs `NODE_ENV=development next build`, they would need a copy of `react-is` because the conditional use of `react-is` checks `NODE_ENV` — not whether or not HMR is being used (what what the `dev` variable is based on).
-
由 Saro Vindigni 提交于
-
由 Peter Kellner 提交于
Updated with-context-api to include an about page and also events that pass data to context provider (#6082) …aces (home and about pages). This makes it the example more clear and why someone might want to use _app.js in the first place. Also, added a button on the about page that allows for passing and arbitrary value from the about page to the context provider. I disagree with the naming convention of calling the class CounterProvider. It includes both a Provider and Consumer so it should have some name that covers both. Maybe it should be called CounterContext but I did not change that. I've seen other examples of the same naming conversion so figure I'm the odd duck here (still think it's wrong no matter how many people do it).
-
由 Tejas Kumar 提交于
I just added a paragraph and some links to the serverless section.
-
- 17 1月, 2019 2 次提交
-
-
由 Jerome Fitzgerald 提交于
Adds a Bullet Point under "Production deployment" for the Table of Contens / Link Section. Wanted to add this as a comment in #6070. Great work as always!
-
由 Tim Neutkens 提交于
I need feedback on if this is clear enough for users.
-
- 16 1月, 2019 3 次提交
-
-
由 Giuseppe 提交于
Introduces full support for Babel 7 including JSX Fragments shorthand. Switched to visiting the `Program` path and then start a traversal manually to solve conflicts with other Babel plugins.
-
由 fabb 提交于
-
由 Telegin Evgeniy 提交于
Resolves #5630
-
- 15 1月, 2019 1 次提交
-
-
由 Tim Neutkens 提交于
Fixes https://github.com/zeit/now-builders/issues/168 For some reason with a certain mix of deps `...` is not supported in webpack's parsing. By default it is supported as all our tests passed before and we have deployed Next.js apps on v2 already.
-
- 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 1 次提交
-
-
由 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.
-