- 20 11月, 2018 1 次提交
-
-
由 Anderson Leite 提交于
-
- 19 11月, 2018 6 次提交
-
-
由 Tim Neutkens 提交于
-
由 Giuseppe 提交于
-
由 Sean Connolly 提交于
-
由 paulogdm 提交于
Fixes #5680
-
由 Anderson Leite 提交于
Extracting the logic that defines if a page is blocked to utils. If that refactor make sense, I will create a next PR to cover both of the functions inside utils with tests.
-
由 Alexander Kachkaev 提交于
-
- 18 11月, 2018 2 次提交
-
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
* Add node_modules bundling under the —lambdas flag for next build * Run minifier when lambdas mode is enabled * Add lambdas option to next.config.js * Add test for lambdas option
-
- 16 11月, 2018 1 次提交
-
-
由 Luc 提交于
-
- 15 11月, 2018 1 次提交
-
-
由 Luc 提交于
-
- 14 11月, 2018 5 次提交
-
-
由 Anderson Leite 提交于
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
Fixes #5671
-
由 Tim Neutkens 提交于
-
由 Adam Lane 提交于
This alternative implementation of https://github.com/zeit/next.js/pull/5150 follows @timneutkens suggestion of using props. Fixes #5150 Fixes #3630
-
- 13 11月, 2018 2 次提交
-
-
由 Adam Lane 提交于
-
由 Luc 提交于
It looks like this : ![capture d ecran 2018-11-13 a 00 47 12](https://user-images.githubusercontent.com/6616955/48361936-7cc13d80-e6dd-11e8-8aa8-c5a73beae966.png) I'm not sure about the License part, can you check @timneutkens ?
-
- 12 11月, 2018 3 次提交
-
-
由 Tim Neutkens 提交于
* Trim buildId returned from generateBuildId * Pass dir to function
-
由 Anderson Leite 提交于
The current contributing.md instructions are outdated since the project uses yarn. The problem: Without installing yarn we have the following error/output: `lerna ERR! yarn run prepublish exited ENOENT in 'next-server'` Adding new instructions on how to install and run the project.
-
由 luffyZhou 提交于
Current with-ant-design-less example has some problems. - Upgrade next7, console found a 404 error. ![](https://user-gold-cdn.xitu.io/2018/11/11/167015fb80017e79?w=2606&h=1000&f=jpeg&s=124801) > After upgrade next7, .next folder didn't find /static/style.css and there is /static/css/style.chunk.css. - The /_next/static/style.css link don't need be placed in the <Head> tag. The style.chunk.css file will be add in the head tag automatically after build. - The project with more pages include _app.js, _document.js...the antd-custom.less will not work well. > The solution is use `modifyVars` of `lessLoaderOptions`. It work well in my project~
-
- 10 11月, 2018 1 次提交
-
-
由 Adam Lane 提交于
-
- 09 11月, 2018 3 次提交
-
-
由 Callum Locke 提交于
-
由 Tim Neutkens 提交于
-
由 Jerónimo Carrizo 提交于
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 11月, 2018 6 次提交
-
-
由 Jamie Barton 提交于
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 提交于
- 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
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
-
由 Giuseppe 提交于
because of this https://twitter.com/rem/status/1059563246007566336
-
由 Tim Neutkens 提交于
-
- 07 11月, 2018 5 次提交
-
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
-
由 Davide Curletti 提交于
The customer-server-typescript example has a bug where the `yarn start` command has the incorrect path to the server entry point file.
-
- 06 11月, 2018 4 次提交
-
-
由 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.
-
由 Pieter De Decker 提交于
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
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.
-