- 09 Nov, 2018 2 commits
-
-
Tim Neutkens authored
-
Jerónimo Carrizo authored
In order to trying to resolve the bug [#5480](https://github.com/zeit/next.js/issues/5480), I create this PR which update the webpack version.
-
- 08 Nov, 2018 2 commits
-
-
Jamie Barton authored
Instead of bundling `postcss-cli` we can now make use of `@zeit/with-css`. This also means we can get rid of the `<style>` import and concurrent build step for css.
🎉 -
Tim Neutkens authored
- use `enhanceApp` so that styled-components used in _app.js are server rendered - call parent getInitialProps, fixes #5629 - return `styles`, making the render() method obsolete. cc @mxstbr @probablyup
-
- 07 Nov, 2018 9 commits
-
-
Tim Neutkens authored
-
Tim Neutkens authored
-
Giuseppe authored
because of this https://twitter.com/rem/status/1059563246007566336
-
Tim Neutkens authored
-
Tim Neutkens authored
-
Tim Neutkens authored
-
Tim Neutkens authored
-
Tim Neutkens authored
-
Davide Curletti authored
The customer-server-typescript example has a bug where the `yarn start` command has the incorrect path to the server entry point file.
-
- 06 Nov, 2018 1 commit
-
-
Már Örlygsson authored
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 Nov, 2018 5 commits
-
-
Pieter De Decker authored
-
Tim Neutkens authored
-
Tim Neutkens authored
Takes advantage of caching between builds for Terser, also makes writing caches for babel-loader faster by disabling compression. Results for zeit.co (350 pages): Without cache: [4:16:22 PM] Compiled server in 1m [4:16:57 PM] Compiled client in 2m
✨ Done in 125.83s. With cache: [4:19:38 PM] Compiled client in 17s [4:19:50 PM] Compiled server in 29s✨ Done in 31.79s. Note: these results are from my multi-core Macbook Pro 2017, exact specs: MacBook Pro (13-inch, 2017, Four Thunderbolt 3 Ports) - 3,3 GHz Intel Core i5 - 16 GB 2133 MHz LPDDR3 - Intel Iris Plus Graphics 650 1536 MB The `without cache` build runs uglify in parallel, so without cache is likely to take longer on environments where you have only 1 core available. The `with cache` build however runs in a single thread, so the results should be similar. -
Tim Neutkens authored
-
Tim Neutkens authored
-
- 04 Nov, 2018 15 commits
-
-
Tim Neutkens authored
-
Tim Neutkens authored
-
Tim Neutkens authored
-
Tim Neutkens authored
-
Tim Neutkens authored
-
Tim Neutkens authored
-
Tim Neutkens authored
-
Tim Neutkens authored
-
Rafael Cossovan authored
Tests using a case insensitive expression. Fixes assets output folder. Reduce `limit` so we can use `file-loader` on larger files.
-
Tim Neutkens authored
-
Tim Neutkens authored
-
Tim Neutkens authored
-
Tim Neutkens authored
-
Tim Neutkens authored
Fixes #4887 Fixes #3612 Also removes http-errors dependency from next-server, leaving a smaller install size
-
Tim Neutkens authored
Drops an additional 6MB from the next-server node_modules size as there's no lodash
-
- 03 Nov, 2018 6 commits
-
-
Tim Neutkens authored
-
Tim Neutkens authored
-
Tim Neutkens authored
* Move __NEXT_DATA__ into a application/json script tag As outlined by @dav-is here https://github.com/zeit/next.js/pull/4943 * Set __NEXT_DATA__ for backwards compatability
-
Radovan Šmitala authored
Based on this PR https://github.com/zeit/next.js/pull/5520 there should be `engines` definition in package.json as first warn. Why i choose Node 8 as minimum? @timneutkens said (https://github.com/zeit/next.js/pull/5520/files#r228330327) that next.js should work on version 7.5 but automated tests in TravisCI are with versions 8 and 10. Version 7 was development branch. I think only production ready should be recommended.
-
Tim Neutkens authored
Clears the way a bit for #4943, also makes _document.js less complex, and will allow us to move `__NEXT_DATA__` to a `application/json` script tag. Also this causes a slightly smaller bundle size
😌 -
Tim Neutkens authored
It's no longer needed inside the `render()` function since we have a separate devServer
-