- 30 Nov, 2018 4 commits
-
-
Tim Neutkens authored
-
Tim Neutkens authored
Fixes #5778 Fixes #3650
-
Tim Neutkens authored
-
Tim Neutkens authored
-
- 29 Nov, 2018 5 commits
-
-
Steven Bell authored
-
Tim Neutkens authored
-
Tim Neutkens authored
-
Tim Neutkens authored
-
Tim Neutkens authored
* Fix polyfill for ie11 * Use esmodules only when using webpack
-
- 28 Nov, 2018 7 commits
-
-
Jan Mühlemann authored
* replace all i18next related examples with the recommended next-i18next module * update readme
-
garnerp authored
Added next/babel in .babelrc Upgraded babel-macros to babel-plugin-macros Upgraded preval.macro
-
Tim Neutkens authored
-
Tim Neutkens authored
* Make sure const/async is transpiled * Use babel common compilation instead
-
Ståle Pettersen authored
-
Tim Neutkens authored
-
Tim Neutkens authored
- Replaces taskr-babel with taskr-typescript for the `next` package - Makes sure Node 8+ is used, no unneeded transpilation - Compile Next.js client side files through babel the same way pages are - Compile Next.js client side files to esmodules, not commonjs, so that tree shaking works. - Move error-debug.js out of next-server as it's only used/require in development - Drop ansi-html as dependency from next-server - Make next/link esmodule (for tree-shaking) - Make next/router esmodule (for tree-shaking) - add typescript compilation to next-server - Remove last remains of Flow - Move hoist-non-react-statics to next, out of next-server - Move htmlescape to next, out of next-server - Remove runtime-corejs2 from next-server
-
- 27 Nov, 2018 4 commits
-
-
Tim Neutkens authored
-
-
Tim Neutkens authored
-
Anderson Leite authored
- Removed unused "render" and "appPort" var from tests - Fix typo on "occured" to "occurred"
-
- 26 Nov, 2018 1 commit
-
-
Tim Neutkens authored
Based on https://github.com/zeit/next.js/pull/5737#discussion_r236059295 This will cause a warning in chrome/safari after 3s
-
- 25 Nov, 2018 5 commits
-
-
Isaac Hinman authored
-
Voon Ming Hann authored
-
Ting-Hsiang Hsu authored
In this example, we can: - `QueryRenderer` SSR - caching the data - use the feature of `react-relay-network-modern` which is the powerful tool for `relay-modern` I copy the example `with-relay-modern`, but I just modified the code. Some detail are not modified. If you think this example is needed, I will fix those. Otherwise, close this **PR** to let me know this example is not needed.
-
Obed Marquez Parlapiano authored
- The with-firebase-auth example won't run unless a database with proper rules is created first. - Add a small error callback to addDbListener to help with debugging if someone's database connection doesn't work.
-
Anderson Leite authored
**What's this PR?** Based on the feedback on [this PR](https://github.com/zeit/next.js/pull/5722) @timneutkens asked me to create a test for `ssr: true` **What's it do?** - adds a test for setting `ssr: true` - /basic - adds a test for setting `ssr: true` - /production
-
- 24 Nov, 2018 2 commits
-
-
Tim Neutkens authored
-
Tim Neutkens authored
* Use <link rel=“prefetch”> for prefetching Fixes #5734 * Fix unit tests for router * Add test for prefetch * Rename test * Check all logs for message
-
- 23 Nov, 2018 1 commit
-
-
Hozefa authored
Since glamorous is [no longer maintained](https://github.com/paypal/glamorous#status-unmaintained) removing it from readme.
-
- 22 Nov, 2018 3 commits
-
-
Matt Jewell authored
(At least with my set up, mac osx, node 10.13.0, yarn 1.12.1) Couldn't get the server to start with `npm start`, this appears to fix that
-
Richard Park authored
* Upgrade terser-webpack-plugin * Upgrade webpack * Extract common terserPluginConfig
-
Vagisha Nidhi authored
This PR is related to the issue #5713 The PR helps to publish test results for reporting in Azure Pipelines. Azure Pipelines provides excellent reporting capabilities that can be leveraged by this PR. An example report is shown in the image below. 
-
- 21 Nov, 2018 5 commits
-
-
Tim Neutkens authored
-
Tim Neutkens authored
* Remove flow-typed * Remove flow types * Remove the last types * Bring back taskr dependency * Revert "Bring back taskr dependency" This reverts commit 38cb95d7274d63fe63c6ac3c95ca358a28c17895. * Bring back preset-flow as it’s used for tests * Revert "Revert "Bring back taskr dependency"" This reverts commit b4c933ef133f4039f544fb10bf31d5c95d3b27a2.
-
Darryl authored
I'm trying to contribute on resolving issues, hope this help. Fixes #5694
-
Curran Kelleher authored
I came across **Possible spelling mistakes** #5496 and noticed that the current wording could be improved both in terms of accuracy and succinctness.
-
Anderson Leite authored
-
- 20 Nov, 2018 3 commits
-
-
Adam Lane authored
-
Már Örlygsson authored
On the server `props.initialMobxState` received by the `constructor` is a fully functioning mobx store that was instantiated by `getInitialProps()` only a few ticks earlier. Thus, creating a new instance is unneccessary. In the browser, however, `props.initialMobxState` is a hydrated plain object and thus the store needs to be initialized.
-
Tim Neutkens authored
-