- 19 Sep, 2018 2 commits
-
-
Tim Neutkens authored
-
Tim Neutkens authored
# Conflicts: # package.json
-
- 18 Sep, 2018 1 commit
-
-
Henrik Wenz authored
This way the warnings will work in test mode. (`process.env.NODE_ENV === „test“`)
-
- 17 Sep, 2018 5 commits
-
-
Tim Neutkens authored
-
Tim Neutkens authored
-
Tim Neutkens authored
Fixes an edge case where some library imports react-dom by itself, like react-spring.
-
Tim Neutkens authored
-
Tim Neutkens authored
-
- 16 Sep, 2018 8 commits
-
-
Stephen Sauceda authored
Adding an example of testing with Mocha #4767
-
Tim Neutkens authored
-
Tim Neutkens authored
-
Tim Neutkens authored
-
Tim Neutkens authored
-
Tim Neutkens authored
Follow-up of #5176 Closes #5173 as it led to inconsistencies in DX.
-
Tim Neutkens authored
First wave of changes. Just landing this first so that there is a base to build on.
-
René Keller authored
./css.js has been removed with [e093441b](https://github.com/zeit/next.js/commit/e093441bad588e98765a05df90f76f75283eda07#diff-b9cfc7f2cdf78a7f4b91a753d10865a2)
-
- 14 Sep, 2018 4 commits
-
-
Tim Neutkens authored
-
Henrik Wenz authored
Since we are now using webpacks `mode` flag we can get rid of: * `webpack.optimize.ModuleConcatenationPlugin` * `webpack.DefinePlugin` (`process.env.NODE_ENV`) https://webpack.js.org/concepts/mode/
-
maurodaprotis authored
* Add with-context-api example * Change next dependency to canary and fix CounterProvider import
-
Tim Neutkens authored
This saves 7KB as prop-types-exact is not needed in production.
-
- 12 Sep, 2018 7 commits
-
-
Rafael Almeida authored
There is no need to wrap every page with a component when you can use the custom document.
-
Marcelo Zapaia authored
in some cases access to the token doesn't work in client side. this access to the token once in getInitialProps method and pass it down using props
-
Henri authored
Added a clear example on how to use react-jss with injecting the styles on the server. cssinjs/jss#457
-
Tim Neutkens authored
* Remove handleBuildId as it’s being handled in the static files route * Remove dead code
-
Tim Neutkens authored
-
Lin Qiu authored
-
Tim Neutkens authored
-
- 11 Sep, 2018 2 commits
-
-
Tim Neutkens authored
-
Tim Neutkens authored
Solves inconsistent loading issues when one bundle is loaded faster than the other Fixes zeit/next-plugins#244 Fixes #4997 Fixes #4620
-
- 10 Sep, 2018 1 commit
-
-
Kyle Holmberg authored
Update next.config in with-webpack-bundle-analyzer example to avoid issue with Next.js in CI (#5135) See: https://spectrum.chat/thread/030243b0-7ebf-434c-8e02-5f54ea30f3b6 Build works now
💃
-
- 09 Sep, 2018 2 commits
-
-
Tim Neutkens authored
-
Tim Neutkens authored
* Add test for /_next/development route * Make sure useFileSystemPublicRoute: false only disables filesystem routing * Bring back comment * Add useFileSystemPublicRoutes tests
-
- 08 Sep, 2018 1 commit
-
-
Tim Neutkens authored
Fixes #5125 I'm not sure if this is a bug in babel-loader / babel-core or not. But this will at least temporary fix it till I hear back from @loganfsmyth
🙏
-
- 07 Sep, 2018 6 commits
-
-
Tim Neutkens authored
-
Tim Neutkens authored
Fixes #5114 Also adds a test for it.
-
Tim Neutkens authored
-
Evan Jacobs authored
you folks should really use semver ranges, but since greenkeeper is no longer running for this branch things have fallen behind in particular, there seems to be an incompatibility with multiple v2.x versions of this package in the same bundle as displayed here: https://github.com/styled-components/styled-components/issues/1972 When I force resolution to a particular h-n-r-s version, the issue goes away. This is true for both next 6 and next 7 canary. But really you folks should use semver carets instead of pinning.
-
Evan Jacobs authored
you folks should really use semver ranges, but since greenkeeper is no longer running for this branch things have fallen behind in particular, there seems to be an incompatibility with multiple v2.x versions of this package in the same bundle as displayed here: styled-components/styled-components#1972 When I force resolution to a particular h-n-r-s version, the issue goes away. This is true for both next 6 and next 7 canary.
-
Julia Qiu authored
Probably an oversight but currently env preset's `modules` option always evaluates to 'auto'. We probably want it to be set to false, especially in prod, to have Webpack handle modules natively.
-
- 06 Sep, 2018 1 commit
-
-
Tim Neutkens authored
-