- 19 3月, 2019 1 次提交
-
-
由 Joe Haddad 提交于
-
- 14 3月, 2019 2 次提交
-
-
由 JJ Kasper 提交于
* Add err.sh link for threw undefined * Update wording Co-Authored-By: Nijjk <22380829+ijjk@users.noreply.github.com>
-
由 JJ Kasper 提交于
* Show a better error when someone throws undefined * Update error wording Co-Authored-By: Nijjk <22380829+ijjk@users.noreply.github.com> * Update error wording in test Co-Authored-By: Nijjk <22380829+ijjk@users.noreply.github.com> * Update test and add check for statusCode before updating error
-
- 12 3月, 2019 1 次提交
-
-
由 JJ Kasper 提交于
Fixes: #6497
-
- 20 2月, 2019 1 次提交
-
-
由 Connor Davis 提交于
Upgrades `standard` to major version 12
-
- 14 2月, 2019 1 次提交
-
-
由 Tim Neutkens 提交于
* Add initial AMP implementation * Implement experimental feature flag * Implement feedback from sbenz * Add next/amp and `useAmp` hook * Use /:path*/amp instead * Add canonical * Add amphtml tag * Add ampEnabled for rel=“amphtml” * Remove extra type
-
- 03 2月, 2019 1 次提交
-
-
由 Tim Neutkens 提交于
Followup to removing the /_error in the initial markup we can now compile it using on-demand-entries only when it's needed.
-
- 26 1月, 2019 1 次提交
-
-
由 Tim Neutkens 提交于
This reverts commit 9112f63e.
-
- 23 1月, 2019 1 次提交
-
-
由 Tim Neutkens 提交于
* Move phases back to next/constants * Fix typescript error
-
- 19 12月, 2018 1 次提交
-
-
由 Tim Neutkens 提交于
This brings us one step closer to outputting serverless functions as renderToHTML now renders the passed components, which allows us to bundle the renderToHTML function together with statically imported components in webpack.
-
- 17 12月, 2018 1 次提交
-
-
由 Brian Beck 提交于
As I detailed in [this thread on Spectrum](https://spectrum.chat/?t=3df7b1fb-7331-4ca4-af35-d9a8b1cacb2c), the dev experience would be a lot nicer if the server started listening as soon as possible, before the slow initialization steps. That way, instead of manually polling the dev URL until the server's up (this can take a long time!), I can open it right away and the responses will be delivered when the dev server is done initializing. This makes a few changes to the dev server: * Move `HotReloader` creation to `prepare`. Ideally, more things (from the non-dev `Server`) would be moved to a later point as well, because creating `next({ ... })` is quite slow. * In `run`, wait for a promise to resolve before doing anything. This promise automatically gets resolved whenever `prepare` finishes successfully. And the `next dev` and `next start` scripts: * Since we want to log that the server is ready/listening before the intensive build process kicks off, we return the app instance from `startServer` and the scripts call `app.prepare()`. This should all be backwards compatible, including with all existing custom server recommendations that essentially say `app.prepare().then(listen)`. But now, we could make an even better recommendation: start listening right away, then call `app.prepare()` in the `listen` callback. Users would be free to make that change and get better DX. Try it and I doubt you'll want to go back to the old way. :)
-
- 10 12月, 2018 1 次提交
-
-
由 Tim Neutkens 提交于
-
- 03 11月, 2018 1 次提交
-
-
由 Tim Neutkens 提交于
It's no longer needed inside the `render()` function since we have a separate devServer
-
- 03 10月, 2018 1 次提交
-
-
由 Tim Neutkens 提交于
-
- 02 10月, 2018 1 次提交
-
-
由 Tim Neutkens 提交于
-
- 01 10月, 2018 2 次提交
-
-
由 Tim Neutkens 提交于
As prepare is only needed to boot up the hot reloader + exportPathMap routes in development, it's not longer a requirement in the production server.
-
由 Tim Neutkens 提交于
- Implements Lerna - Moves all source code into `packages/next` - Keeps integration tests in the root directory
-
- 29 9月, 2018 1 次提交
-
-
由 Tim Neutkens 提交于
-
- 28 9月, 2018 2 次提交
-
-
由 Tim Neutkens 提交于
Remove `if(this.hotReloader)` as it's always guaranteed to be there. https://github.com/zeit/next.js/pull/5317#discussion_r221233064
-
由 Tim Neutkens 提交于
* Initial dev server * Remove obsolete check * Move hotReloader to dev-server * Use parent renderErrorToHTML to remove dep on render.js * Remove dev option from server itself
-