- 13 2月, 2019 1 次提交
-
-
由 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 7 次提交
-
-
由 Connor Davis 提交于
-
由 Connor Davis 提交于
-
由 Joe Haddad 提交于
* Add `module` as server fallback main field * Test that a module only package can be imported
-
由 Juan Olvera 提交于
* convert export default anonymous functions into named functions * change examples to function declaration and split export in classes * change NextHead name to Head and rename component
-
由 Connor Davis 提交于
-
由 Spencer Elliott 提交于
`initialProps.styles` is a React node, but not guaranteed to be an array, so we can use a fragment to concatenate additional styles. See https://github.com/DefinitelyTyped/DefinitelyTyped/issues/32932#issuecomment-462372319
-
由 Jason Miller 提交于
-
- 11 2月, 2019 11 次提交
-
-
由 Juan Olvera 提交于
* extract request login from auth * add clarification that the monorepo is for deploy in Now only and fix typo * Refactor HOC - add authorization to HOC - add displayName to HOC - remove unnecessary `run`s in local routing
-
由 Fredrik Höglund 提交于
* Updated examples for build-time env configuration for v8 * Add comment to build time config example with how to include entire .env
-
由 Resi Respati 提交于
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
-
由 Resi Respati 提交于
As per discussion in #6165, I removed the `passHref` in `Link` as they're unnecessary.
-
由 Giuseppe 提交于
Changelog https://github.com/zeit/styled-jsx/releases/tag/v3.2.1
-
由 Fredrik Höglund 提交于
-
由 Akram 提交于
-
- 10 2月, 2019 5 次提交
-
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
* Bring in terser-webpack-plugin * Ignore terser from linting
-
由 Kris Luminar 提交于
-
- 08 2月, 2019 4 次提交
-
-
由 Tim Neutkens 提交于
-
由 Connor Davis 提交于
Introduce env to next.config.js for build-time configuration
-
由 Connor Davis 提交于
-
由 Alexander Nanberg 提交于
AFAIK this dependency isn't being used anywhere so it should be safe to remove it.
-
- 04 2月, 2019 1 次提交
-
-
由 Henri 提交于
This updates the react-jss example to work with the v10 alpha
-
- 03 2月, 2019 5 次提交
-
-
由 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.
-
由 Konstantin Grushetsky 提交于
-
-
`Router.events.off` should be called instead of `Router.events.on` in `componentWillInmount`.
-
由 Giuseppe 提交于
Fixes #5860
-
- 01 2月, 2019 4 次提交
-
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
-
由 Sultan Tarimo 提交于
Closes #6152. - Only dynamically load /_error.js when an exception occurs. - Fix websocket “/_error.js” ping oddity.
-
由 Resi Respati 提交于
I've just thought of a way to improve the initial props page by adding an example for a list/detail page structure. To do that, I've created a separate `/detail` page, and a mock API which calls data from the array we made on the previous PR. A ListDetail component is created as an example for displaying detail. Page structure is also cleaned up. Should I go ahead and add an example on how to style with styled-jsx + its TS declarations? I might decide to do it within this week anyway.
-
- 31 1月, 2019 1 次提交
-
-
由 Petr Messner 提交于
Update examples with-relay-modern and with-relay-modern-server-express to react-relay 2.0.0 - react-relay has started to use new Context API instead of Legacy Context API - add `parseInt` because graphql 14.0.0 introduced stricter scalar value coercion Closes #6157
-
- 30 1月, 2019 1 次提交
-
-
由 Timon Borter 提交于
This reverts the changes made in [this pr](https://github.com/zeit/next.js/pull/6109). `redux-saga: "1.0.0"` changed the way it handles it's queues. Because of that we're still having trouble to implement the synchronous side-effects flow in `next-redux-saga`. See [this discussion](https://github.com/bbortt/next-redux-saga/pull/1) for more information. Therefore I would feel more comfortable not to mislead users by giving them a non-working example in the main branch.
-