- 21 Feb, 2019 7 commits
-
-
Tim Neutkens authored
-
Tim Neutkens authored
-
Joe Haddad authored
-
HelloRusk authored
I renewed Rust installation Link.
-
Vincent Grafé authored
I spotted a few typos in the server files, that might confuse new/unexperienced users. I hope I did catch them all!
-
Robert Sköld authored
-
Tim Neutkens authored
-
- 20 Feb, 2019 15 commits
-
-
Ariel Fuggini authored
Fixes https://github.com/zeit/next.js/issues/6201 Fixes #5912
-
Joe Haddad authored
* Pass along props to html * Check for html props to be passed * Switch ordering of html tag props * Remove children from this.props
-
Joe Haddad authored
* Make console output well behaved * Fix bad rebase
-
Jess Telford authored
-
Isaac Hinman authored
-
Connor Davis authored
-
Tim Neutkens authored
-
Joe Haddad authored
This introduces a new `<Html>` tag for a custom `Document` so that we can correctly toggle the `amp` flag (among other things in the future ... maybe). This is already "tested" through every other test & the AMP validator -- but let me know if we want explicit tests.
-
Jess Telford authored
-
Jess Telford authored
-
Andrew Gerard authored
* assign deep defaults for custom config * allow for new object type defaults * fix linting
-
HelloRusk authored
-
Tim Neutkens authored
-
Joe Haddad authored
-
Connor Davis authored
-
- 19 Feb, 2019 6 commits
-
-
wtgtybhertgeghgtwtg authored
Currently, `getBaseWebpackConfig` is marked async, but it doesn't await anything or otherwise return a Promise. Please correct me if I am wrong, but it looks like it can be made synchronous.
-
Connor Davis authored
Upgrades `standard` to major version 12
-
JJ Kasper authored
After talking with @timneutkens it was decided it'd be more streamlined to replace the onDemandEntries WebSocket with an alternative. Using the EventSource connection gives us these benefits over the WebSocket one: - less code needed - no extra server running - no extra config for onDemandEntries
-
Timothy authored
* Update readme with ZEIT Now deployment guide link * Update links to ZEIT Now deployment guide * Fix missing word
-
Joe Haddad authored
Relevant commit: https://github.com/zeit/next.js/commit/f913aabe163aebfbe57a2c407be5e7108559cc3a ~~I needed to upgrade Standard to work with JSX fragment syntax.~~ This caused too much noise so I just stopped using Fragments.
-
Joe Haddad authored
-
- 18 Feb, 2019 3 commits
-
-
Kenneth Luján Rosas authored
* fix(launch-editor): resolve filename including current working directory * refactor: handle when fileName is already absolute * feat: use Next.js dir instead of process.cwd()
-
Jess Telford authored
If this is an acceptable pattern, I'm happy to open a PR to add these links to all the other examples also
👍 -
Joe Haddad authored
Per consensus in a mixed-application scenario, we'll use the `amp` query parameter convention.
-
- 17 Feb, 2019 8 commits
-
-
Timon Borter authored
-
Tim Neutkens authored
-
Tim Neutkens authored
Arguments that held the same name as one of the default commands were filtered out, causing issues. For example `next build build` would get rid of the second `build` parameter. Fixes #6263
-
Tim Neutkens authored
Fixes #5347 The main issue is that we were waiting only 1 level of dynamic imports, so the dynamic imports nested inside other dynamic import files were not awaited. This would cause either a flash of loading states or you wouldn't see the loading state (because of preload) but it would then show a hydration warning in development. Thanks to @arthens for providing the reproduction that I modelled the tests after.
-
Ahmed Tarek authored
-
Tim Neutkens authored
-
Joshua Scott authored
-
Joe Haddad authored
Success:  Error:  Warnings:  --- We can still make build error output friendlier, but this is a good start.
-
- 16 Feb, 2019 1 commit
-
-
Tim Neutkens authored
-