- 03 Dec, 2018 7 commits
-
-
Tim Neutkens authored
-
Tim Neutkens authored
-
Jess Telford authored
Example deployment on now v2: https://nextjswith-mdxexample-r8b1vzjbn.now.sh
-
Tim Neutkens authored
Same as https://github.com/zeit/ncc/pull/80
-
Matthew Lilley authored
* Fix for locale.split is not a function. Following from https://github.com/zeit/next.js/pull/5488 - Renamed languages to supportedLanguages - Firstly, accept languages based on supportedLanguages - And finally, accept a single language, if it returns false, the default of 'en' is used. I looked at the navigator library, which is used by 'accept', this should be a more solid solution, since we can now know that `const locale` is always a string. // Before (Sometimes returns an array as `const local`) const locale = accept.language(languages) || 'en' // After (Always returns a string) const locale = accept.language(accept.languages(supportedLanguages)) || 'en'; * Update server.js Update variable name.
-
Tim Neutkens authored
Fixes #3705 Fixes #4656 - No longer automatically dedupe certain tags. Only the ones we know are *never* going to be duplicate like charSet, title etc. - Fix `key=""` behavior, making sure that if a unique key is provided tags are deduped based on that. For example: ```jsx <meta property='fb:pages' content='one'> <meta property='fb:pages' content='two'> ``` Would currently cause ```jsx <meta property='fb:pages' content='two'> ``` ### After this change: ```jsx <meta property='fb:pages' content='one'> <meta property='fb:pages' content='two'> ``` Then if you use next/head multiple times / want to be able to override: ```jsx <meta property='fb:pages' content='one' key="not-unique-key"> <meta property='fb:pages' content='two' key="not-unique-key"> ``` Would cause: ```jsx <meta property='fb:pages' content='two'> ``` As `key` gets deduped correctly after this PR, similar to how React itself works.
-
Tim Neutkens authored
-
- 02 Dec, 2018 1 commit
-
-
Tim Neutkens authored
Slowly moving files over
💯
-
- 01 Dec, 2018 1 commit
-
-
Luc authored
-
- 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 2 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
-