- 06 11月, 2018 1 次提交
-
-
由 Már Örlygsson 提交于
I spent far too much time fiddling with this example project before realizing it contained a bug in the store initialization logic and it was a bit more complex than it needed to be. * The custom server was not needed * The store-initialization did effectively the same thing twice for no reason * And wrapping MyApp component in a HOC was wholly unnecessary indirection My changes are split into four discrete commits for clarity.
-
- 05 11月, 2018 1 次提交
-
-
由 Rafael Cossovan 提交于
Tests using a case insensitive expression. Fixes assets output folder. Reduce `limit` so we can use `file-loader` on larger files.
-
- 03 11月, 2018 2 次提交
-
-
由 AJ Livingston 提交于
* added example for using typings-for-css-modules-loader * Update examples/with-typings-for-css-modules/README.md * Update examples/with-typings-for-css-modules/README.md * Update examples/with-typings-for-css-modules/next.config.js
-
由 Henrik Wenz 提交于
* Update examples/with-antd-mobile - Reduced noise - Simplify setup * Create more more complex example
-
- 01 11月, 2018 1 次提交
-
-
由 Giuseppe 提交于
* Remove pathname (#5428) Same as #5424 * fix typo (#5451) * Add with style-sheet example * Fix readme * Fix typo
-
- 30 10月, 2018 2 次提交
-
-
由 Anton Moiseev 提交于
- Looks like no other example provides a link to a hosted demo - There is the "Deploy to now" badge, so it can be deployed on demand when needed - The link is broken anyway - Probably any example hosted by an individual contributor sooner or later will be cleaned up, doesn't feel like a reliable way to provide a live demo
-
由 Anton Moiseev 提交于
* Replace _document.tsx example with _app.tsx * Fix title * Remove _app.tsx
-
- 29 10月, 2018 1 次提交
-
-
由 Janek Rahrt 提交于
* fix graphql dep * fix ssr auth bug * fix linting issues
-
- 24 10月, 2018 1 次提交
-
-
由 Quentin Sommer 提交于
Add an example how to use `@quentin-sommer/react-useragent` with next. I've been asked this https://github.com/quentin-sommer/react-useragent/issues/10 and plan to link this example as reference! See readme for details
-
- 23 10月, 2018 1 次提交
-
-
由 David Calhoun 提交于
Utilize ES modules, which are now the default export for `react-native-web`. _NOTE:_ [This example requires `next@^7.0.0`](https://bit.ly/2PaEhao).
-
- 21 10月, 2018 3 次提交
-
-
由 Christopher Lee 提交于
-
由 ultrox 提交于
package accept returns false if can't find language in offered list of languages, then later on bool is attempted to be split, and app crashes in prod & dev
-
由 Tim Neutkens 提交于
-
- 20 10月, 2018 4 次提交
-
-
由 Henrik Wenz 提交于
* Fix linter * Add test env * Fix lint errors
-
由 Anthony Cerbic 提交于
-
由 komkanit 提交于
-
由 zsx 提交于
-
- 19 10月, 2018 2 次提交
-
-
由 Seth Bergman 提交于
Fixes link to 404 page in sentry docs
-
由 Jerome Fitzgerald 提交于
Docker Multistage * Remove `devDependencies` from `./node_modules` in `builder` for faster copy on `base` init * Added `isomorphic-unfetch` to show it not being copied over to `base`. * `isomorphic-fetch` will still show from `next`
-
- 18 10月, 2018 1 次提交
-
-
由 Gerhard Preuss 提交于
I successfully deployed this example with `now` and `now --public` (I am on premium plan). Did this before deploy ```sh $ cp Dockerfile.multistage Dockerfile ```
-
- 17 10月, 2018 1 次提交
-
-
由 Zach Curtis 提交于
-
- 16 10月, 2018 2 次提交
-
-
由 Luc 提交于
-
由 Iurii Kucherov 提交于
Hello, Here is a small PR to fix some typos on the comments.
-
- 15 10月, 2018 1 次提交
-
-
由 Jan Czizikow 提交于
-
- 14 10月, 2018 1 次提交
-
-
由 Don Alvarez 提交于
The mobx-state-tree examples (with and without typescript) pre-dated the next _app class and needed to be updated to use _app for persisting state across client-side navigation transitions. Also removed unneeded custom server class to better keep with the "show one feature per example" style of the next examples folder
-
- 12 10月, 2018 1 次提交
-
-
由 zsx 提交于
-
- 11 10月, 2018 1 次提交
-
-
由 Rafael Almeida 提交于
Fixes #5352 . This updates the example updating react-i18next to v8.0.6, replacing the `translate` HOC to `withNamespaces` and `I18n` to `NamespacesConsumer`. There is one thing that I am not sure if is correct or not so I need some guidance. You gotta wrap the page with the `withI18next` HOC so it will extend the `getInitialProps` of the page with this: ``` Extended.getInitialProps = async (ctx) => { const composedInitialProps = ComposedComponent.getInitialProps ? await ComposedComponent.getInitialProps(ctx) : {} const i18nInitialProps = ctx.req ? i18n.getInitialProps(ctx.req, namespaces) : {} return { ...composedInitialProps, ...i18nInitialProps } } ``` The problem lies in `i18n.getInitialProps` that has this code: ``` i18n.getInitialProps = (req, namespaces) => { if (!namespaces) namespaces = i18n.options.defaultNS if (typeof namespaces === 'string') namespaces = [namespaces] req.i18n.toJSON = () => null // do not serialize i18next instance and send to client const initialI18nStore = {} req.i18n.languages.forEach((l) => { initialI18nStore[l] = {} namespaces.forEach((ns) => { initialI18nStore[l][ns] = (req.i18n.services.resourceStore.data[l] || {})[ns] || {} }) }) return { i18n: req.i18n, // use the instance on req - fixed language on request (avoid issues in race conditions with lngs of different users) initialI18nStore, initialLanguage: req.i18n.language } } ``` In my understanding, among other things, it gets the `i18n` object from the request (included by the `server.js`) and uses the data to create `initialI18nStore` and `initialLanguage`, and then return these two objects plus the `i18n` object itself. If you add the `i18n` object on the return, then there will be a crash on the client-side render of the page: ```TypeError: Cannot read property 'ready' of null``` I don't know why, but returning it breaks `NamespacesConsumer` component from `react-i18next` (the state becomes null). So I commented this line and the provider on `_app.js` is getting the `i18n` instance from the `i18n.js` file (the same as `server.js`). I don't know if this would be an issue so I would like help to debug this.
-
- 10 10月, 2018 2 次提交
-
-
由 Luc 提交于
* fix relative path in examples/.babelrc * remove examples/.babelrc * remove examples/.gitignore
-
由 Kenneth Luján Rosas 提交于
Regarding a question about having different global layouts via `_app.js` usage, it came up that we could use a static property in the page that needed a different one(Thanks @timneutkens ) Link to the Spectrum post: https://spectrum.chat/?t=af6ca794-5420-4780-abd8-96f085a19e09 This PR adds an example called `with-dynamic-app-layout`, that showcases that use case in the simplest way I could think of. Let me know if there's changes or improvements to be made.
🎉
-
- 09 10月, 2018 4 次提交
- 07 10月, 2018 2 次提交
-
-
由 Romello Goodman 提交于
Upgrading the styled-components and babel styled components packages!
-
由 Logan McAnsh 提交于
[polka](https://github.com/lukeed/polka/releases/tag/v0.5.0) changed their listen api to be more like express like
-
- 06 10月, 2018 1 次提交
-
-
由 Supakorn Thongtra 提交于
* <title> should not be used in _document.js's * fix style as it was
-
- 01 10月, 2018 1 次提交
-
-
由 Carlos 提交于
* Add analyze-bundles example * housekeeping: with-webpack-bundle-analyzer example * analyze-bundles example: revert the version of faker library * analyze-bundles add analyze:server and analyze:browser to scripts * with-webpack-bundle-analyzer example: fix typo
-
- 29 9月, 2018 1 次提交
-
-
由 Carlos 提交于
### Next js 7+ and Typescript 3+ Example No babel, tsc, pure typescript usage Made by [next-with-typescript plugin](https://github.com/echoulen/next-with-typescript)
-
- 28 9月, 2018 2 次提交
-
-
由 Mert Can 提交于
-
由 Yuri Yakovlev 提交于
-