- 09 11月, 2020 11 次提交
-
-
由 iczero 提交于
`node-sass` v5 introduced support for Node.js v15, which is not supported by v4. However, Next.js currently errors with ``` Error: Node Sass version 5.0.0 is incompatible with ^4.0.0. ``` when attempting to build with `node-sass` 5.0.0. This error comes from `sass-loader`. They have recently released version 10.0.5 which supports `node-sass` 5.0.0 (PR <https://github.com/webpack-contrib/sass-loader/pull/899>, release <https://github.com/webpack-contrib/sass-loader/releases/tag/v10.0.5>).
-
由 tolfino 提交于
This replaces the seen set with a newly instantiated map of refs per value in the array. This corrects the behavior that the refs map passed into isSerializable contains only values along the path to the current value: previously, because the refs map was shared among all values in the array, this would trigger on instances such as: ```js const x = []; isSerializableProps('/', 'test', { arr: [x, [x]] }); ``` ... where the reference is shared but there is no cycle formed, as the presence of elements is disjoint. Fixes #18228.
-
由 James George 提交于
Prevent `catch` assertions in tests.
-
由 Davidson Nascimento 提交于
- Changed script `start` to `dev` and improved it #18934 adding commando to transpile electron code; - Added some folders into `.gitignore`; - Updated react to avoid issues as #18916 Fixes #18934
-
由 JJ Kasper 提交于
This updates to use the `Build.SourceVersion` value from the [predefined variables](https://docs.microsoft.com/en-us/azure/devops/pipelines/build/variables?view=azure-devops&tabs=yaml) for the cache key instead of the pull request value since it isn't available after merging to canary. x-ref: https://github.com/vercel/next.js/pull/18931
-
由 Tadao Iseki 提交于
This allows to import the type `ImageProps` from `next/image` like `next/link`. https://github.com/vercel/next.js/blob/a6660729ea82fbcb26cfe7c89637b1af37255c9f/packages/next/client/link.tsx#L21 ## Usage ```tsx import Image, { ImageProps } from 'next/image' const CustomImage: React.FC<ImageProps> = (props) => ( <Image {...props} unsized /> ) ```
-
由 JJ Kasper 提交于
-
由 Michael McQuade 提交于
The other examples are using the typescript `import type` style, which gets stripped during the build, so I added it to the API Routes example too.
-
由 Jesse Jafa 提交于
Resolves https://github.com/vercel/next.js/issues/18941
-
由 Luis Alvarez D 提交于
Notes: - I use "blank page" to refer to that state where a new tab is waiting for the initial HTML. Lmk if there are better words to describe that. - I did not add an usage example because it's the same thing of `fallback: true` and `fallback: false`, but with a config change. It's also explained below them and mentions the similarity with `fallback: true` --- Fixes #18468
-
由 JJ Kasper 提交于
-
- 08 11月, 2020 4 次提交
-
-
由 JJ Kasper 提交于
This ensures dynamic routes are correctly generated for `next start` with i18n and adds tests to the i18n suite to ensure they are working correctly. Closes: https://github.com/vercel/next.js/issues/18397
-
由 Davidson Nascimento 提交于
-
由 Joe Haddad 提交于
-
由 Steven 提交于
This PR fixes two bugs causing HTML validators to complain. - Error: Bad value data:image/svg+xml;charset=utf-8, for attribute src on element img: Illegal character in scheme data: < is not allowed. - Fixed by using base64 for svg during `layout=intrinsic` to avoid angle brackets - Error: Element img is missing required attribute src. - Fixed by using base64 transparent gif for `loading=lazy` placeholder Fixes #18850
-
- 07 11月, 2020 10 次提交
-
-
由 Dinesh Balaji 提交于
When `create-next-app` is initialized a git repo, it now uses 'main' as the initial branch. The branch master does not actually exist initially. The branches don't get created only when they have at least one commit. Until the branch gets created, the branch only exists in .git/HEAD. So there is no master branch initialized in the repo. Closes: https://github.com/vercel/next.js/issues/17733 <img width="639" alt="Screenshot 2020-10-09 at 17 26 30" src="https://user-images.githubusercontent.com/4656109/95580229-9f3c6c80-0a54-11eb-967f-180eb9601c1a.png">
-
由 Joe Haddad 提交于
This PR adds additional security tests.
-
由 JJ Kasper 提交于
This makes sure to compile query values for rewrites/redirects as non-path items to prevent param like values e.g. `https://` from causing the destination to fail to compile. Fixes: https://github.com/vercel/next.js/issues/17440 x-ref: https://github.com/vercel/next.js/issues/18670
-
由 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
☝ ️ -
由 Joe Haddad 提交于
This pull request fixes `<Image />` not updating when new props are passed by removing external DOM mutations and relying on React to do it instead. As an added bonus, I've extracted the intersection observer from both the `<Image />` and `<Link />` component, as their instance can be shared! The increase in size is minor (+3B), and actually a decrease for apps using both `<Image />` and `<Link />`. --- Fixes #18698 Fixes #18369
-
由 Steven 提交于
Fixes #18908
-
由 JJ Kasper 提交于
-
由 Bruno Crosier 提交于
Co-authored-by: NLuis Alvarez <luis@vercel.com>
-
由 JJ Kasper 提交于
This makes sure we don't use es6 syntax when compiling the `web-vitals` package with `ncc` since that breaks IE11 compatibility x-ref: https://github.com/vercel/ncc/pull/614
-
由 Joe Haddad 提交于
While we were fixing how Next.js handled CSS, we added a complex prefetch, preload, fetch sequence to acquire the CSS asset. This unnecessarily overcomplicated what could've been only a `fetch()` from the very start! --- Fixes #16932
-
- 06 11月, 2020 15 次提交
-
-
由 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'
-
由 Joe Haddad 提交于
Fixes #17066
-
由 JJ Kasper 提交于
-
由 JJ Kasper 提交于
This corrects this test failing from an arrow function being used in ie11 which isn't supported natively ``` ● Production Usage › Dynamic import › default behavior › should not remove css styles for same css file between page transitions JavascriptError: Error executing JavaScript at Object.throwDecodedError (../node_modules/selenium-webdriver/lib/error.js:550:15) at parseHttpResponse (../node_modules/selenium-webdriver/lib/http.js:565:13) at Executor.execute (../node_modules/selenium-webdriver/lib/http.js:491:26) ```
-
由 Luis Alvarez D 提交于
Note that the indentation of the code samples and notes is important so it uses the same indentation of the items in the list. Fixes https://github.com/vercel/next.js/issues/18869
-
由 Guy Bedford 提交于
This upgrades to ncc@0.25.0 and fixes the previous bugs including: * ncc not referenced correctly in build * Babel type errors * node-fetch, etag, chalk and raw-body dependencies not building with ncc - these have been "un-ncc'd" for now. As they are relatively small dependencies, this doesn't seem too much of an issue and we can follow up in the tracking ncc issue at https://github.com/vercel/ncc/issues/612. * `yarn dev` issues Took a lot of bisecting, but the overall diff isn't too bad here in the end.
-
由 Joe Haddad 提交于
* Ensure we prefetch on hover * double because of hovering prefetch * rerun workflow * disable flaky test
-
由 Steven 提交于
Fixes #18827 so that lazy loading does not break IE 11.
-
由 Guy Bedford 提交于
This fixes the current regression with an ncc revert for now. I will continue to follow up with the ncc upgrade in https://github.com/vercel/next.js/pull/18860.
-
由 JJ Kasper 提交于
* Fix chromedriver set-up to test electron separately * Update workflow * Update compiled
-
由 Joe Haddad 提交于
-
由 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✨ -
由 JJ Kasper 提交于
-