- 20 2月, 2019 6 次提交
-
-
由 Joe Haddad 提交于
-
由 Connor Davis 提交于
-
由 wtgtybhertgeghgtwtg 提交于
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 提交于
Upgrades `standard` to major version 12
-
由 JJ Kasper 提交于
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 提交于
* Update readme with ZEIT Now deployment guide link * Update links to ZEIT Now deployment guide * Fix missing word
-
- 19 2月, 2019 2 次提交
-
-
由 Joe Haddad 提交于
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 提交于
-
- 18 2月, 2019 7 次提交
-
-
由 Kenneth Luján Rosas 提交于
* 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 提交于
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 提交于
Per consensus in a mixed-application scenario, we'll use the `amp` query parameter convention.
-
由 Timon Borter 提交于
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
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 提交于
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.
-
- 17 2月, 2019 6 次提交
-
-
由 Ahmed Tarek 提交于
-
由 Tim Neutkens 提交于
-
由 Joshua Scott 提交于
-
由 Joe Haddad 提交于
Success: ![image](https://user-images.githubusercontent.com/616428/52907314-5e636480-322d-11e9-9420-b348663a3a7a.png) Error: ![image](https://user-images.githubusercontent.com/616428/52907318-6c18ea00-322d-11e9-848d-e615d6af747d.png) Warnings: ![image](https://user-images.githubusercontent.com/616428/52907353-2d376400-322e-11e9-9778-370f36912491.png) --- We can still make build error output friendlier, but this is a good start.
-
由 Tim Neutkens 提交于
-
由 Joe Haddad 提交于
* Remove usage of WebpackBar and Friendly Errors * Add new clearConsole helper * Add new simplified output for development mode * Add an explicit bootstrapping mode * Add missing returns * Use existing output style * Adjust first output to say Waiting on * Only print URL if present
-
- 16 2月, 2019 4 次提交
-
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
-
由 JJ Kasper 提交于
After discussion, I added falling back to fetch based pinging when the WebSocket fails to connect. I also added an example of how to proxy the onDemandEntries WebSocket when using a custom server. Fixes: #6296
-
由 Connor Davis 提交于
Closes: #6244 This will block the following keys: ``` NODE_.+ __.+ ``` There doesn't seem to be a way to simulate a failed build or else I'd add tests for it.
-
- 15 2月, 2019 3 次提交
-
-
由 Timon Borter 提交于
-
由 Felix Mosheev 提交于
-
由 Joe Haddad 提交于
-
- 14 2月, 2019 3 次提交
-
-
由 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
-
由 Joe Haddad 提交于
-
由 Jonathan Reed 提交于
# Description * Fixes incorrect assertion of configuration file in the `with-hashed-statics` README as well as adds link to line for updating
-
- 13 2月, 2019 6 次提交
-
-
由 Gary Meehan 提交于
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
# Conflicts: # lerna.json # packages/next-server/package.json # packages/next/package.json
-
由 Truong Hoang Dung 提交于
Add options to customize webpack config section.
-
由 Joe Haddad 提交于
* Set default `Error` status code to 404 This is an appropriate default behavior because: 1. When the server encounters an error, the `err` property is set. 2. When the client-side application crashes, the `err` property is set. This means the "only" way to render the `/_error` page without an error is when a page is not found (special condition). Fixes #6243 Closes #5437 * Add new integration test for client side 404 * single quotes * Remove unused variable * Standard needs to go away * Whoops * Check for null status code in res and err * Only check response for valid statusCode
-
- 12 2月, 2019 3 次提交
-
-
由 Connor Davis 提交于
-
由 Connor Davis 提交于
-
由 Joe Haddad 提交于
* Add `module` as server fallback main field * Test that a module only package can be imported
-