- 17 10月, 2020 8 次提交
-
-
由 Joe Haddad 提交于
-
由 Joe Haddad 提交于
-
由 Yamagishi Kazutoshi 提交于
![Screenshot on VS Code](https://user-images.githubusercontent.com/12539/96300300-43fc1280-1030-11eb-89ae-dba8beeca583.png) The only attribute that must be used with Image Component is src, but all attributes are required and TypeScript will warn you.
-
由 Yamagishi Kazutoshi 提交于
Unify the confusing `config.images.sizes` ([Image Optimizer](https://github.com/vercel/next.js/discussions/17141)) and `config.images.breakpoints` ([Image Component](https://github.com/vercel/next.js/discussions/16832)).
-
由 Yamagishi Kazutoshi 提交于
Image Optimizer only accepts the name of the width parameter as a `w`. ref https://github.com/vercel/next.js/blob/v9.5.6-canary.3/packages/next/next-server/server/image-optimizer.ts#L71
-
由 JJ Kasper 提交于
-
由 Tim Neutkens 提交于
Co-authored-by: NSteven <steven@ceriously.com>
-
由 Tim Neutkens 提交于
-
- 16 10月, 2020 8 次提交
-
-
由 Tim Neutkens 提交于
-
由 Steven 提交于
Co-authored-by: NJJ Kasper <jj@jjsweb.site>
-
由 JJ Kasper 提交于
This makes sure the correct `initialRevalidateSeconds` field is populated in the `prerender-manifest` for non-dynamic SSG pages since they will be inserted into the `initialPageRevalidationMap` under their locale prefixed variant with `i18n` enabled x-ref: https://github.com/vercel/next.js/pull/17370
-
由 Joe Haddad 提交于
This PR adjust the Web Vitals reporting to be called *after* rendering occurs. It used to work like this, but React's render method is no longer synchronous—so we have to do it in an effect. Existing tests should cover this code path, and IMO it's unfeasible to test that it's invoked _after_ hydration. Also removed the `&& ST` condition which is not relevant to Web Vitals.
-
由 JJ Kasper 提交于
* Ensure i18n support with AMP * Fix type error * Update size-limit
-
由 JJ Kasper 提交于
-
由 JJ Kasper 提交于
-
由 JJ Kasper 提交于
This adds the i18n config items to the routes-manifest so that they can accessed in the builder. This doesn't increment the routes-manifest version as existing value shapes haven't been modified and an additional non-breaking value is being added x-ref: https://github.com/vercel/next.js/pull/17370
-
- 15 10月, 2020 4 次提交
-
-
由 Tim Neutkens 提交于
-
由 Slawek Kolodziej 提交于
Co-authored-by: NTim Neutkens <tim@timneutkens.nl> Co-authored-by: Nkodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
由 JJ Kasper 提交于
This adds the `locale` prop for `next/link` to allow transitioning between locales client-side and also allows passing the locale to `router.push/replace` via the transition options similar to `shallow` e.g. `router.push('/another', '/another, { locale: 'nl' })` x-ref: https://github.com/vercel/next.js/pull/17370
-
由 JJ Kasper 提交于
This updates to set the `NEXT_LOCALE` cookie to the default locale when the user prefers a different locale from the default in their `accept-language` header but visits the default locale path e.g. `/en-US` with a `accept-language` preferred header of `nl` will set the `NEXT_LOCALE=en-US` header and then redirect to `/` x-ref: https://github.com/vercel/next.js/pull/17370
-
- 14 10月, 2020 6 次提交
-
-
由 Tim Neutkens 提交于
-
由 Tommaso De Rossi 提交于
Co-authored-by: NLuis Alvarez D <luis@vercel.com> Co-authored-by: NTim Neutkens <tim@timneutkens.nl>
-
由 Simone Corsi 提交于
-
由 Alex Castle 提交于
Co-authored-by: NTim Neutkens <timneutkens@me.com> Co-authored-by: NTim Neutkens <tim@timneutkens.nl>
-
由 JJ Kasper 提交于
Co-authored-by: Nkodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
由 Jan Potoms 提交于
Co-authored-by: NJJ Kasper <jj@jjsweb.site> Co-authored-by: Nkodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
- 13 10月, 2020 1 次提交
-
-
由 Prateek Bhatnagar 提交于
Co-authored-by: NTim Neutkens <tim@timneutkens.nl> Co-authored-by: NTim Neutkens <timneutkens@me.com>
-
- 12 10月, 2020 2 次提交
-
-
由 JJ Kasper 提交于
While working on https://github.com/vercel/next.js/pull/17755 noticed a couple of cases that needed fixing and broke them out to this PR to make that one easier to review. One fix is for `ssgCacheKey` where it wasn't having the `locale` prefix stripped correctly due to the locales no longer being populated under the server instances `renderOpts` and the second fix is for the `asPath` not being set to `/` when the `locale` is the only part in the URL e.g. `/en` became an empty string `""` x-ref: https://github.com/vercel/next.js/pull/17370
-
由 JJ Kasper 提交于
Follow-up to https://github.com/vercel/next.js/pull/17370 this makes sure the locale detection is case-insensitive.
-
- 10 10月, 2020 3 次提交
-
-
由 JJ Kasper 提交于
Follow-up to https://github.com/vercel/next.js/pull/17370 this adds mapping of locales to domains and handles default locales for specific domains also allowing specifying which locales can be visited for each domain. This PR also updates to output all statically generated pages under the locale prefix to make it easier to locate/lookup and to not redirect to the default locale prefixed path when no `accept-language` header is provided.
-
由 JJ Kasper 提交于
-
由 JJ Kasper 提交于
-
- 09 10月, 2020 3 次提交
-
-
由 JJ Kasper 提交于
Follow-up PR to #17370 this adds generating auto-export, non-dynamic SSG, and fallback pages with all locales. Dynamic SSG pages still control which locales the pages are generated with using `getStaticPaths`. To further control which locales non-dynamic SSG pages will be prerendered with a follow-up PR adding handling for 404 behavior from `getStaticProps` will be needed. x-ref: https://github.com/vercel/next.js/issues/17110
-
由 JJ Kasper 提交于
-
由 JJ Kasper 提交于
This is a follow-up to https://github.com/vercel/next.js/pull/16973 which adds handling for the breaking change in the latest version of css-loader that causes unresolved file references in `url` or `import` to cause the build to fail. This fixes it by adding our own resolve checking and when it fails disabling the `css-loader`'s handling of it. Fixes: https://github.com/vercel/next.js/issues/17701
-
- 08 10月, 2020 4 次提交
-
-
由 JJ Kasper 提交于
Follow-up PR to https://github.com/vercel/next.js/pull/17370 when the path is not prefixed with a locale and the default locale is the detected locale it doesn't redirect to locale prefixed variant. If the default locale path is visited and the default locale is visited this also redirects to the root removing the un-necessary locale in the URL. This also exposes the `defaultLocale` on the router since the RFC mentions `Setting a defaultLocale is required in every i18n library so it'd be useful for Next.js to provide it to the application.` although doesn't explicitly spec where we want to expose it. If we want to expose it differently this can be updated.
-
由 JJ Kasper 提交于
This adds the initial changes outlined in the [i18n routing RFC](https://github.com/vercel/next.js/discussions/17078). This currently treats the locale prefix on routes similar to how the basePath is treated in that the config doesn't require any changes to your pages directory and is automatically stripped/added based on the detected locale that should be used. Currently redirecting occurs on the `/` route if a locale is detected regardless of if an optional catch-all route would match the `/` route or not we may want to investigate whether we want to disable this redirection automatically if an `/index.js` file isn't present at root of the pages directory. TODO: - [x] ensure locale detection/populating works in serverless mode correctly - [x] add tests for locale handling in different modes, fallback/getStaticProps/getServerSideProps To be continued in fall-up PRs - [ ] add tests for revalidate, auto-export, basePath + i18n - [ ] add mapping of domains with locales - [ ] investigate detecting locale against non-index routes and populating the locale in a cookie x-ref: https://github.com/vercel/next.js/issues/17110
-
由 JJ Kasper 提交于
-
由 JJ Kasper 提交于
-
- 06 10月, 2020 1 次提交
-
-
由 Joe Haddad 提交于
-