- 09 11月, 2020 1 次提交
-
-
由 Jesse Jafa 提交于
Resolves https://github.com/vercel/next.js/issues/18941
-
- 08 11月, 2020 1 次提交
-
-
由 Davidson Nascimento 提交于
-
- 07 11月, 2020 3 次提交
-
-
由 Ante Sepic 提交于
Now that all Contentful spaces support GraphQL, we are looking into switching the example from using a JS library to a simple fetch with GraphQL. @stefanjudis
☝ ️ -
由 Steven 提交于
Fixes #18908
-
由 Bruno Crosier 提交于
Co-authored-by: NLuis Alvarez <luis@vercel.com>
-
- 06 11月, 2020 4 次提交
-
-
由 Prottay Rudra 提交于
- new chakra-ui rc version doesn't work without 'farmer-motion', installed farmer motion - updated 'chakra-ui' library from '^1.0.0-rc.3' to '^1.0.0-rc.8'
-
由 Steven 提交于
Fixes #18794
-
由 Matthew Lilley 提交于
This PR fixes issues in two apollo examples where cached queries are lost, and cached data is merged incorrectly.
-
由 Vitor Dino 提交于
hey there
👋 stumbled on the [`using-preact` example](https://github.com/vercel/next.js/tree/canary/examples/using-preact) first when i tried to port my project, just saw that the [config wasn’t that trivial](https://github.com/vercel/next.js/issues/13969#issuecomment-641540051), and it would fit better on a [plugin](https://github.com/preactjs/next-plugin-preact).. I did this migration first on my project (it worked super well) and realized that people also would dislike having to maintain that kind of code, and would stumble faster on the plugin if it was already on the official example✨
-
- 05 11月, 2020 1 次提交
-
-
由 Steven 提交于
This revises the docs to add headings and also links to layout examples. Fixes #18554
-
- 04 11月, 2020 2 次提交
-
-
由 Matsumoto Toshi 提交于
Co-authored-by: Nkodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
由 Steven 提交于
-
- 03 11月, 2020 1 次提交
-
-
由 Aral Roca Gomez 提交于
Co-authored-by: NJoe Haddad <joe.haddad@zeit.co>
-
- 02 11月, 2020 1 次提交
-
-
由 Carmelo Scandaliato 提交于
Co-authored-by: Nkodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
- 31 10月, 2020 2 次提交
-
-
由 Daniel Treviño 提交于
Co-authored-by: Nkodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
由 ospira 提交于
* small tweaks for those testing on an existing site with missing author or featured image on posts When migrating WordPress or using an exisitng site, sometimes you have published posts wth missing data. The graphql plugin will properly resolve these to null, but some of existing code accessing tries to access the node property on these null values. I've made these properties optional in the pages and also tweaked some of the components along similar lines. * Lint fix Co-authored-by: NLuis Alvarez <luis@vercel.com> Co-authored-by: Nkodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
- 30 10月, 2020 2 次提交
-
-
由 Yudai Oriver K 提交于
Fixes #18523 ## description The i18n-routing Vercel deploy button URLs was: https://vercel.com/import/project?template=https://github.com/vercel/next.js/tree/canary/examples/amp So, I fixed the URLs for examples/i18n-routing: https://vercel.com/import/project?template=https://github.com/vercel/next.js/tree/canary/examples/i18n-routing
-
由 Yuji Matsumoto 提交于
- Update Next.js version to 10.0.0 - Update the other dependencies - Modify `next.config.js` to prevent circular `__self` and `__source`in dev env (ref: https://github.com/developit/nextjs-preact-demo/issues/25)
-
- 29 10月, 2020 2 次提交
- 28 10月, 2020 2 次提交
-
-
由 Sebastian Troć 提交于
-
由 Quinn Turner 提交于
Order moduleFileExtensions from most used to least used extensions. Sources: https://jestjs.io/docs/en/configuration#modulefileextensions-arraystring and facebook/jest#7616
-
- 27 10月, 2020 1 次提交
-
-
由 JJ Kasper 提交于
This is a follow-up to https://github.com/vercel/next.js/pull/18067 adding an example for i18n routing x-ref: https://github.com/vercel/next.js/pull/17370
-
- 24 10月, 2020 1 次提交
-
-
由 Steven 提交于
Co-authored-by: NLee Robinson <me@leerob.io> Co-authored-by: NTim Neutkens <timneutkens@me.com>
-
- 21 10月, 2020 1 次提交
-
-
由 Tuan Nguyen 提交于
This closes [#18023](https://github.com/vercel/next.js/issues/18023). I was following the example mentioned in the issue (https://github.com/vercel/next.js/tree/canary/examples/with-firebase-authentication) and for some reason `xa` was always false, failing fetching food. Through `console.log` I saw that `ya` contained a token value and using `ya` worked.
-
- 19 10月, 2020 3 次提交
-
-
由 Justin W Hall 提交于
Co-authored-by: NRémi de Juvigny <remi@hey.com> Co-authored-by: NTim Neutkens <tim@timneutkens.nl> Co-authored-by: Nkodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
由 Ash Connell 提交于
-
由 Or Yoffe 提交于
The current dependencies of the example "with-react-native-web" are outdated. In this PR I updated them and tested that they run and work. Newest current react and react-dom versions: 16.13.1 Newest current react-native-web and babel-plugin-react-native-web versions: 0.13.14 Mainly for the people starting with this example to have the new versions since the current versions are very far from each other. Please merge
🙏
-
- 17 10月, 2020 1 次提交
-
-
由 Ash Connell 提交于
This PR fixes 2 issues with the mongodb example: ### 1. Fallable Caching Strategy Calling `connectToDatabase()` multiple times before it's cached results in multiple connections being created. The latest one created was becoming the "cached" one and the others dissappear into the background. This is now fixed by using **promise sharing** so that only one connection can ever be created. ### 2. Problematic Hot Reload During development you can monitor your database connections and see that it continues to create more and more connections over time. Some users have reported their [databases reaching maximum connection limits](https://github.com/vercel/next.js/discussions/12229). This is resolved by using `global` to store the cached connection. It's not ideal but it is necessary.
-
- 15 10月, 2020 2 次提交
-
-
由 kamei 提交于
-
由 Davidson Nascimento 提交于
-
- 13 10月, 2020 1 次提交
-
-
由 Henrik Wenz 提交于
## Change To opt-in to using the new layers mode by default. ## Motivation - Reduces CSS filesize - Prevents users from using the already deprecated old layers mode - Removes the following console warnings: ```log risk - There are upcoming breaking changes: purgeLayersByDefault risk - We highly recommend opting-in to these changes now to simplify upgrading Tailwind in the future. risk - https://tailwindcss.com/docs/upcoming-changes ``` [more info](https://tailwindcss.com/docs/upcoming-changes)
-
- 09 10月, 2020 1 次提交
-
-
由 Jens Meindertsma 提交于
When using the `with-msw` example I noticed it increased my bundle size in production, even through MSW is meant to be used in development only. **Build size before implementing MSW** ``` Page Size First Load JS ┌ λ / 479 B 58.9 kB ├ /_app 0 B 58.4 kB └ ○ /404 3.44 kB 61.9 kB + First Load JS shared by all 58.4 kB ├ chunks/f6078781a05fe1bcb0902d23dbbb2662c8d200b3.b1b405.js 10.3 kB ├ chunks/framework.cb05d5.js 39.9 kB ├ chunks/main.a140d5.js 7.28 kB ├ chunks/pages/_app.b90a57.js 277 B └ chunks/webpack.e06743.js 751 B λ (Server) server-side renders at runtime (uses getInitialProps or getServerSideProps) ○ (Static) automatically rendered as static HTML (uses no initial props) ● (SSG) automatically generated as static HTML + JSON (uses getStaticProps) (ISR) incremental static regeneration (uses revalidate in getStaticProps) ``` **Build size after implementing MSW according to the `with-msw` example** ``` Page Size First Load JS ┌ λ / 479 B 71.6 kB ├ /_app 0 B 71.1 kB └ ○ /404 3.44 kB 74.6 kB + First Load JS shared by all 71.1 kB ├ chunks/f6078781a05fe1bcb0902d23dbbb2662c8d200b3.b1b405.js 10.3 kB ├ chunks/framework.cb05d5.js 39.9 kB ├ chunks/main.a140d5.js 7.28 kB ├ chunks/pages/_app.c58a6f.js 13 kB └ chunks/webpack.e06743.js 751 B λ (Server) server-side renders at runtime (uses getInitialProps or getServerSideProps) ○ (Static) automatically rendered as static HTML (uses no initial props) ● (SSG) automatically generated as static HTML + JSON (uses getStaticProps) (ISR) incremental static regeneration (uses revalidate in getStaticProps) ``` There was a 12.7 kB large increase in the `_app` First Load JS which increased the pages' First Load JS size. I tracked the problem down to the following code: ```js if (process.env.NEXT_PUBLIC_API_MOCKING === 'enabled') { require('../mocks') } ``` Removing this reduces the `_app` First Load JS to what it was previously. The `NEXT_PUBLIC_API_MOCKING` environment variable is defined in the `.env.development` file, as this means that Next.js will only activate MSW during development/testing, which is what MSW is intended for. After discussing with @kettanaito, the author of MSW, I did some investigation. This dynamic require statement is intended to allow tree-shaking of the MSW package for production. Unfortunately this did not seem to be working. To fix this, I changed the code to the following: ```js if (process.env.NODE_ENV !== 'production') { require('../mocks') } ``` This means I could remove the `NEXT_PUBLIC_API_MOCKING` environment variable from `.env.development`, as it is no longer used. It is important to note that this still achieves the same functionality as before: MSW runs in development / testing, and not in production. If MSW must be enabled in production for some reason, the following code can be used to run MSW regardless of the environment: ```js if (true) { require('../mocks') } ``` If possible, I'd love to hear from the Next.js maintainers regarding the tree-shaking process when using environment variables. Lastly, I made the necessary changes to have the example work in production mode as well, because there is no real backend. Of course there is a comment explaining what should be changed in a real world app.
-
- 08 10月, 2020 1 次提交
-
-
由 Henrik Wenz 提交于
# Issue The cache updates are performed in a wrong way, resulting in a duplicate collection: **Error:** ```log webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:88 Warning: Encountered two children with the same key, `6f3f7265-0d97-4708-a3ea-7dee76dc0a0a`. Keys should be unique so that components maintain their identity across updates. Non-unique keys may cause children to be duplicated and/or omitted — the behavior is unsupported and could change in a future version. ``` **Video:** ![broken](https://user-images.githubusercontent.com/1265681/95336501-0c170180-08b1-11eb-9273-6ac9e37ceb41.gif) # Fix **Video:** ![fixed](https://user-images.githubusercontent.com/1265681/95336538-15a06980-08b1-11eb-8d5e-6acc07e16138.gif)
-
- 06 10月, 2020 1 次提交
-
-
由 Tantan Fu 提交于
-
- 05 10月, 2020 1 次提交
-
-
由 Rafael Zerbini 提交于
Fixes #16431 * Added `.babelrc` with `next/babel` to remove the need of the React import on the `with-storybook` example.
-
- 03 10月, 2020 1 次提交
-
-
由 Riccardo Di Maio 提交于
-
- 02 10月, 2020 1 次提交
-
-
由 Dylan Jhaveri 提交于
-
- 30 9月, 2020 2 次提交
-
-
由 Philihp Busby 提交于
If this component is missing, an error will be printed to the console ``` Expected Document Component Head was not rendered. Make sure you render them in your custom `_document` See more info here https://err.sh/next.js/missing-document-component ``` Additionally, any components which use CSS modules will fail with an error. This is documented in https://nextjs.org/docs/advanced-features/custom-document
-
由 Amandeep Singh 提交于
-