- 04 11月, 2020 15 次提交
-
-
由 Steven 提交于
-
由 Steven 提交于
-
由 Tom 提交于
-
由 Guy Bedford 提交于
This is a prerequisite to being able to ncc inline the Babel dependencies in next.js. The removal of preset-modules is based on replacing it with preset-env under `targets: { esmodules: true }`, as per the guidance from the package (https://www.npmjs.com/package/@babel/preset-modules): > Starting from @babel/preset-env 7.9.0, you can enable the bugfixes: true option to get the same behavior as using @babel/preset-modules, but with support for custom targets. If you need to target browsers with native modules support (like this preset does), you can use targets: { esmodules: true }. From the above, I'm pretty sure this is entirely a backwards compatible change, apart from the change to the runtime plugin list being visible. Perhaps @developit can confirm this as well.
-
由 Matsumoto Toshi 提交于
Co-authored-by: Nkodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
由 Steven 提交于
-
由 Steven 提交于
-
由 Steven 提交于
-
由 Steven 提交于
Disabling GH Comments per @Timer These are the same settings we use for the `vercel/vercel` repo.
-
由 Steven 提交于
-
由 Cowboy Ho 提交于
Co-authored-by: NTim Neutkens <timneutkens@me.com> Co-authored-by: NJoe Haddad <joe.haddad@zeit.co> Co-authored-by: NJJ Kasper <jj@jjsweb.site>
-
由 Joe Haddad 提交于
-
由 Steven 提交于
-
由 Joe Haddad 提交于
-
由 JJ Kasper 提交于
This ensures we don't render the page un-necessarily when a redirect is returned from `getStaticProps` or `getServerSideProps`. Possibly related: https://github.com/vercel/next.js/issues/18735 Closes: https://github.com/vercel/next.js/issues/18747
-
- 03 11月, 2020 18 次提交
-
-
由 Eric Burel 提交于
-
由 Aral Roca Gomez 提交于
Co-authored-by: NJoe Haddad <joe.haddad@zeit.co>
-
由 Lee Robinson 提交于
Updates https://nextjs.org/docs/migrating/from-gatsby to mention the new `next/image` component released in Next.js 10.
-
由 Joe Haddad 提交于
Next.js would try to "recover" if its CSS assets went missing (i.e. a deployment occured) **while the page was initially loading**. This handled a rare case where we'd try to let the Next.js complete hydrating even though a deployment occured. However, in practice, this never worked: if the `fetch()` failed, that means the original assets never downloaded themselves (because the `fetch()` should be coming from disk cache). Instead of letting Next.js get itself into a weird state, let's just stop hydration so that the page doesn't accidentally delete its styles. The handle-no-styles behavior is already tested in `test/integration/css/test/index.test.js`. There was never a branch for it using its cached styles, so nothing else needs updated. --- Fixes #17930
-
由 khades 提交于
Serverside Dynamically loaded CSS module file insertion adds css-files as usual static files with special data-n-p tag, that is used in page transition logic. That files get removed on page transition cause they are not explicitly required in scope of page. Mini-css-extract-plugin adds style tags at chunk insertion without any tags and leave them be, no matter how many page transitions were made. I removed data-n-p tag from dynamically loaded css module files and added new data-n-d tag for it. Fixes #16950
-
由 Joe Haddad 提交于
-
由 JJ Kasper 提交于
This ensures the `basePath` property works correctly when a multi-level value is defined (`/hello/world`) Fixes: https://github.com/vercel/next.js/issues/17889
-
由 Steven 提交于
- Update default `deviceSizes` - Add default `imageSizes` - Use `layout` value to determine which `srcset` to use Fixes #18420 Closes #18714
-
由 JJ Kasper 提交于
This makes sure we don't incorrectly strip locale characters from the path if it is not a locale prefix e.g. `/fr` should not be removed from `/frank`. Additional tests have been added to ensure this isn't stripped for this case. Fixes: https://github.com/vercel/next.js/issues/18332
-
由 JJ Kasper 提交于
When visiting a non-locale prefixed path (`/hello` instead of `/fr/hello`) we don't trigger locale redirects currently so if another locale is matched we need to ensure this is reset to the `defaultLocale` for rendering to prevent a mis-match on the client and the server. This also fixes hydration errors from occurring with `asPath` for `getServerSideProps` pages due to `normalizeLocalePath` expecting only a pathname and `asPath` containing `hash` and `query values also. Fixes: https://github.com/vercel/next.js/issues/18337 Fixes: https://github.com/vercel/next.js/issues/18510
-
由 JJ Kasper 提交于
This adds support for passing `statusCode` in a `redirect` from `getServerSideProps` or `getStaticProps` which matches the `redirect` shape allowed to be returned for `redirects` in `next.config.js` Closes: https://github.com/vercel/next.js/issues/18350
-
由 JJ Kasper 提交于
Closes: https://github.com/vercel/next.js/issues/18694
-
由 JJ Kasper 提交于
This ensures we don't detect the locale from the header when `localeDetection` is set to `false` Fixes: https://github.com/vercel/next.js/issues/18482
-
由 JJ Kasper 提交于
This corrects additional fallback pages being generated without the fallback flag causing `getStaticProps` to be called without params with i18n. The revalidation aspect of the issue has been corrected separately in https://github.com/vercel/next.js/pull/18569 Fixes: https://github.com/vercel/next.js/issues/18404
-
由 JJ Kasper 提交于
This ensures the `html` tag's `lang` attribute is updated on client-transition when the locale is changing Fixes: https://github.com/vercel/next.js/issues/18452
-
由 JJ Kasper 提交于
* Ensure preload works correctly with locale option * Fix conditional import * Update size-limit tests * DCE some code * Resolve merge error Co-authored-by: NTim Neutkens <timneutkens@me.com>
-
由 JJ Kasper 提交于
This updates the documentation with the new `redirect` and `notFound` return values adding `redirect` to the `getStaticProps` section and adding a new section describing the return values allowed for `getServerSideProps` Closes: https://github.com/vercel/next.js/pull/18626 Closes: https://github.com/vercel/next.js/issues/18691
-
由 Joe Haddad 提交于
Fixes #18643
-
- 02 11月, 2020 6 次提交
-
-
由 Joe Haddad 提交于
-
由 Carmelo Scandaliato 提交于
Co-authored-by: Nkodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
https://err.sh/nextjs由 Shun Kakinoki 提交于
Hi next.js team! Was trying out the canary and came across the error! The redirect to https://err.sh was to `https://github.com/vercel/nextjs`, not `https://github.com/vercel/next.js`
-
由 Steven 提交于
In PR #18147, we fixed the default loader to prevent upscaling images. This PR fixes the same bug for 3rd party loaders. --- Fixes #18648
-
由 Steven 提交于
Older versions of Safari (and other browsers) do not support webp format so we were incorrectly falling back to png. This PR fixes #18509 so that we fallback to the original image format if a modern format like webp was not explicitly provided in the Accept header. Tests were added to ensure that the Accept header for Safari, Firefox, and Chrome work properly.
-
由 Joe Haddad 提交于
-
- 01 11月, 2020 1 次提交
-
-
由 Joe Haddad 提交于
-