- 16 5月, 2018 1 次提交
-
-
由 Tim Neutkens 提交于
When changing a page `/_app` can be seen as “updated”, but the router shouldn’t reload it, because there is an ongoing/going to be ongoing update.
-
- 15 5月, 2018 1 次提交
-
-
由 yhirano55 提交于
It's better that Counter behave not only `increment (add)` but also `decrement` or `reset`. * Add decrement, reset handlers and rename add handler in `components/counter.js` * Add increment, decrement, reset actions to `store.js` * Rename page component class name: Counter => Index in `pages/index.js` * Remove needless dispatch count event on getInitialProps in `pages/index.js` * Format JSX to be readable in `pages/_app.js` * Remove needless line from `components/examples.js` * Remove needless spaces in `lib/with-redux-store.js`
-
- 14 5月, 2018 14 次提交
-
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
-
由 yhirano55 提交于
-
由 yhirano55 提交于
* Add name, version, license to package.json
-
由 yhirano55 提交于
* Remove unnecessary dir key from next's argument * Add license section to package.json
-
由 yhirano55 提交于
* Update react, react-dom major version * Add license section to package.json * Use isomorphic-unfetch instead of isomorphic-fetch
-
由 Gaston Fartek 提交于
-
由 yhirano55 提交于
* Fixed class name in data-fetch example * Removed needless empty lines
-
由 yhirano55 提交于
* Added name, version, license keys.
-
由 yhirano55 提交于
I found build error, so I've updated babel-plugin-module-resolver
-
由 yhirano55 提交于
Use https instead of http for tachyons URL
-
- 13 5月, 2018 4 次提交
-
-
由 Petr Messner 提交于
The option `"decoratorsLegacy": true` seems mandatory, fails without it: > The new decorators proposal is not supported yet. You must pass the `"decoratorsLegacy": true` option to @babel/preset-stage-0
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
* Make sure props.url is immutable * Add test for immutable url * Match object instead of string
-
- 12 5月, 2018 2 次提交
-
-
由 Tim Neutkens 提交于
-
由 Karthik Muralidharan 提交于
Fixes the compilation error : ``` * ./clock in ./components/examples.js ModuleNotFoundError: Module not found: Error: [CaseSensit ivePathsPlugin] `/components/clock.js` does not matc h the corresponding path on disk `Clock.js`. ```
-
- 11 5月, 2018 7 次提交
-
-
由 Tomas Carnecky 提交于
Otherwise you may get a React warning about calling setState() on an unmounted component.
-
由 Tim Neutkens 提交于
-
由 Cédric Marcone 提交于
-
由 Kyle Kelley 提交于
-
由 Jason Leibowitz 提交于
* Add immutable redux example * Updated readme * Fix linting errors
-
由 Tim Neutkens 提交于
-
由 Pascal Birchler 提交于
-
- 09 5月, 2018 3 次提交
-
-
由 Andrew Razumovsky 提交于
* Fix flickering on page change via <Link /> * Remove process.browser check
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
-
- 08 5月, 2018 5 次提交
-
-
由 Volker Rose 提交于
This example gave me 404s on `pages/*.tsx` when using it with the latest nextjs (`5.1.0`) and `@zeit/next-typescript@0.0.11`. The latest next-typescript plugin version fixes it.
-
由 Tim Neutkens 提交于
-
由 Kirill Konshin 提交于
* Support _app approach for upgraded Redux Wrapper * Updated according to discussion * Package.json versions
-
由 Michael Hsu 提交于
* fix(with-pkg): update pkg config for next.js * update docs
-
由 Jorge Cuadra 提交于
-
- 07 5月, 2018 3 次提交
-
-
由 Tim Neutkens 提交于
* Simplify redux example * Simplify redux example even more * Remove empty space
-
由 Tim Neutkens 提交于
* Add new apollo example * Update readme * Update with-apollo to use _app.js * Move withData to _app * Make SSR work again * Remove withData * Use HOC to provide apolloClient * Spread pageprops
-
由 Drew Hays 提交于
When running some tests, I noticed that Akamai was still caching the response for render errors for some reason. Honestly, I would've thought that `no-store, must-revalidate` would be enough to prevent the CDN from caching it. That being said, MDN's documentation on [Cache-Control] has a section called ["Preventing Caching"] and recommends also using the `no-cache` directive. Given the definitions provided for `no-cache` and `no-store`, I can't tell much of a difference between these two. But I _do_ know that, for whatever reason, Akamai seems to respect the `no-cache` value for this header. [Cache-Control]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cache-Control ["Preventing Caching"]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cache-Control#Preventing_caching
-