- 27 10月, 2020 16 次提交
-
-
由 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
-
由 Sam Robbins 提交于
Might be easier for some users to see a whole app set up with it
-
由 JJ Kasper 提交于
Follow-up to https://github.com/vercel/next.js/pull/18067 this adds the manifest item for the new docs
-
由 Joe Haddad 提交于
-
由 JJ Kasper 提交于
This is a follow-up to https://github.com/vercel/next.js/pull/17755 which adds support for returning `notFound` to `getServerSideProps` also
-
由 Tasuku Uno 提交于
* Fix test without expect for redirects from getStaticProps/getServerSideProps * Fix browser back issue of redirects from getServerSideProps / getStaticProps
-
由 Joe Haddad 提交于
-
由 JJ Kasper 提交于
This removes the `unstable_` prefix to prepare for stabilizing the feature
-
由 Joe Haddad 提交于
-
由 Steven 提交于
-
由 Steven 提交于
This separates the `next.config.js` property `images.sizes` into to properties: `images.deviceSizes` and `images.iconSizes`. The purpose is for images that are not intended to take up the majority of the viewport. Related to #18122
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
-
由 Steven 提交于
Add missing links in the documentation
-
- 26 10月, 2020 2 次提交
-
-
由 JJ Kasper 提交于
This adds checks to ensure that less than 50 domain and size items are configured and no sizes are less than 0 or greater than 10,000 x-ref: https://github.com/vercel/next.js/issues/18122Co-authored-by: NSteven <steven@ceriously.com>
-
由 Steven 提交于
There was a bug when the user defines a width on the Image component, but a larger size image is requested. This is because the browser uses the `srcset` to decide which image size to request and we had the srcset basically hardcoded. This PR fixes the behavior so that the `srcset` will never be larger than the `width` defined on the component. It also fixes a bug where the preload srcset did not match the img srcset. - Related to #18147 - Related to #18122
-
- 25 10月, 2020 6 次提交
-
-
由 JJ Kasper 提交于
* Add next/image default loader errors * Add domains check * Apply suggestions from PR * Update test
-
由 Steven 提交于
We currently always accept requests to the new `/_next/image` endpoint, even when it should not be used. Instead, we should check to see if the default loader is used as a signal to enable this API. Other loaders (such as cloudinary) will not go through the Next.js API so there is no need to expose this, instead we 404. - Analogous to https://github.com/vercel/vercel/pull/5321 - Related to #18122
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
-
由 JJ Kasper 提交于
This ensures a custom `/404` page with `getStaticProps` works correctly when leveraging the new `unstable_notFound` support in `getStaticProps` Closes: https://github.com/vercel/next.js/issues/18196 x-ref: https://github.com/vercel/next.js/pull/17755
-
由 Giuseppe 提交于
* Adds React 17 as a peer dependency
-
- 24 10月, 2020 4 次提交
-
-
由 Tim Neutkens 提交于
Solves on of the issues in https://github.com/vercel/next.js/issues/18122
-
由 Steven 提交于
Co-authored-by: NLee Robinson <me@leerob.io> Co-authored-by: NTim Neutkens <timneutkens@me.com>
-
由 Steven 提交于
For many users refactoring from `<img>` to `<Image>`, we can often support their properties as-is. The exception was width/height. This PR allows the `<Image>` component to accept strings for `width` and `height` just like `<img>`. Related to #18122
-
由 Steven 提交于
Previously, vector images like svg were being converted to webp and resized. However, vector images already handle any size so we can bypass the same we do for animated images. Related to #18122
-
- 23 10月, 2020 10 次提交
-
-
由 JJ Kasper 提交于
* Add initial i18n documentation * Apply suggestions from code review Co-authored-by: NTim Neutkens <tim@timneutkens.nl> * Apply suggestions from code review Co-authored-by: NLee Robinson <me@leerob.io> * Apply more suggestions * rephrase a bit more * Update doc Co-authored-by: NTim Neutkens <tim@timneutkens.nl> Co-authored-by: NLee Robinson <me@leerob.io> Co-authored-by: NTim Neutkens <timneutkens@me.com>
-
由 Steven 提交于
-
由 Steven 提交于
Add missing `w` param for [old browsers](https://developer.mozilla.org/en-US/docs/Web/API/HTMLImageElement/srcset#Browser_compatibility) like IE that dont support `srcset` (@styfle)
-
由 dependabot[bot] 提交于
Bumps [node-sass](https://github.com/sass/node-sass) from 4.12.0 to 4.13.1. - [Release notes](https://github.com/sass/node-sass/releases) - [Changelog](https://github.com/sass/node-sass/blob/master/CHANGELOG.md) - [Commits](https://github.com/sass/node-sass/compare/v4.12.0...v4.13.1) Signed-off-by: Ndependabot[bot] <support@github.com> Co-authored-by: Ndependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
-
由 dependabot[bot] 提交于
Bumps [tree-kill](https://github.com/pkrumins/node-tree-kill) from 1.2.1 to 1.2.2. - [Release notes](https://github.com/pkrumins/node-tree-kill/releases) - [Commits](https://github.com/pkrumins/node-tree-kill/compare/v1.2.1...v1.2.2) Signed-off-by: Ndependabot[bot] <support@github.com> Co-authored-by: Ndependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Nkodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
由 Yamagishi Kazutoshi 提交于
If give the `priority` and `quality` attributes to an Image Component, the `quality` attribute will not be given to the preload and a warning will be displayed to the devtool. ![screenshot on devtool](https://user-images.githubusercontent.com/12539/96960307-0837e000-153d-11eb-8c01-e15afd40e04f.png)
-
由 JJ Kasper 提交于
* Update redirect query encoding * Add additional tests
-
由 Steven 提交于
The `w` parameter in the Image Optimization API is the requested size of the image and should only be resized if the source image is larger than the requested size. This PR fixes the behavior to prevent accidental upscaling, for example icon images.
-
由 Steven 提交于
This PR updates the `<Image>` component to follow the same property naming as native `<img>`. https://developer.mozilla.org/en-US/docs/Web/HTML/Element/Img#attr-loading This currently allows two values,`loading=lazy` and `loading=eager`, but there might be new values added in a future spec. cc @atcastle
-
由 JJ Kasper 提交于
-
- 22 10月, 2020 2 次提交
-
-
由 JJ Kasper 提交于
Co-authored-by: Nkodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
由 Tim Neutkens 提交于
Co-authored-by: NSteven <steven@ceriously.com>
-