- 21 11月, 2020 1 次提交
-
-
由 JJ Kasper 提交于
This updates the export progress to make sure we log out the final progress update when less pages than number of progress updates (segments). This also adds tests to ensure we are logging the progress out as expected. Fixes: https://github.com/vercel/next.js/issues/19122 Closes: https://github.com/vercel/next.js/pull/19123
-
- 20 11月, 2020 4 次提交
-
-
由 JJ Kasper 提交于
This ensures navigations to non-configured locales causes the 404 page to be shown, it also adds tests to ensure direct visits for non-configured locales 404s correctly. Fixes: https://github.com/vercel/next.js/issues/19214
-
由 JJ Kasper 提交于
This makes sure we're using `next.js` in the err.sh links instead of `nextjs` since that leads to a 404
-
由 JJ Kasper 提交于
This fixes the case where we were returning page data when rendering `/_error` in `serverless` mode with `next start` Closes: https://github.com/vercel/next.js/issues/19068
-
由 Sylvain Bannier 提交于
-
- 19 11月, 2020 1 次提交
-
-
由 Joe Haddad 提交于
This PR removes the modern mode experiment because: - It does not yield meaningful bundle size wins when compared to other initiatives we've taken - It's not compatible with webpack 5 (which we're upgrading to) - It's currently broken and causes most apps to malfunction - There's no champion currently owning the experiment We can re-introduce this in the future when we'd like to make it a default for all Next.js apps. Note: **Next.js still supports Differential Loading (`nomodule`) and does it by default.** This PR strictly removes the experimental modern _syntax_, and does not disable our existing modern/legacy polyfilling. --- Fixes #19200 Fixes #18960 Fixes #14707 Fixes #14465
-
- 18 11月, 2020 6 次提交
-
-
由 Joe Haddad 提交于
-
由 Joe Haddad 提交于
-
由 JJ Kasper 提交于
This ensures redirects are handled properly with i18n + `trailingSlash: true`, additional tests have also been added to ensure this is covered Fixes: https://github.com/vercel/next.js/issues/19069
-
由 JJ Kasper 提交于
-
由 JJ Kasper 提交于
This makes sure SSG data is correctly prefetched for the default locale and other locales on the same page. Tests for this behavior have been added for catch-all and normal pages. Closes: https://github.com/vercel/next.js/issues/19048
-
由 Joe Haddad 提交于
This fixes compatibility with React 17 and `styled-jsx`. Fixes #19242
-
- 16 11月, 2020 2 次提交
-
-
由 Joe Haddad 提交于
-
由 JJ Kasper 提交于
Co-authored-by: NJoe Haddad <joe.haddad@zeit.co>
-
- 14 11月, 2020 7 次提交
-
-
由 JJ Kasper 提交于
-
由 Joe Haddad 提交于
We accidentally regressed back in 9.5 and dropped support for inline CSS comments. PostCSS always parses these as pass-through (and not a syntax error), which can cause problems when minifying. Browsers do a similar thing and ignore the comments. To ensure we generate valid CSS, this adds support for stripping the CSS comments from the build. --- Fixes #15589 Closes #17130
-
由 JJ Kasper 提交于
This allows SSG pages that return `notFound` to be revalidated. Closes: https://github.com/vercel/next.js/issues/18651
-
由 Joe Haddad 提交于
-
由 JJ Kasper 提交于
This mirrors the `basePath: false` behavior for custom-routes with `locale: false` to allow users to configure the locales manually (`locale: false`) or have the locales be handled automatically for custom-routes. Fixes: https://github.com/vercel/next.js/issues/18927 Fixes: https://github.com/vercel/next.js/issues/18795
-
由 Joe Haddad 提交于
-
由 Steven 提交于
Fixes #18557
-
- 13 11月, 2020 10 次提交
-
-
由 Joe Haddad 提交于
-
由 Joe Haddad 提交于
-
由 Steven 提交于
- Fixes #19120 - Closes #18413 - Related to #19041
-
由 Joe Haddad 提交于
Co-authored-by: NGerald Monaco <gbmonaco@google.com>
-
由 Joe Haddad 提交于
-
由 Joe Haddad 提交于
Fixes #18720 This removes image preloading. It doesn't work correctly on any browser other than Chrome (with Chrome's real engine). On all other browsers, it triggers 2x the bytes to be downloaded. The tradeoff isn't worth it here IMO. Chrome itself should be smart enough to bump an `<img />` tag's priority over other preloads that are script type during the preparse phase. We can reintroduce this when we don't hurt non-Chrome users.
-
由 Steven 提交于
Fixes #18415 by using the default config as fallback. Users who wish to use their `next.config.js` values will still need the workaround from https://github.com/vercel/next.js/issues/18415#issuecomment-718180659
-
由 JJ Kasper 提交于
This ensures root optional-catch-all index routes with i18n are output to the correct location and are also loaded from the `prerender-manifest` correctly. Fixes: https://github.com/vercel/next.js/issues/19095
-
由 Matsumoto Toshi 提交于
## Description Fixes #18338 - Fixed an issue with `trailingSlash: true` adding a slash to the end of an external link. After ``` <h1 class="Home_title__3DjR7">Welcome to <a href="https://nextjs.org">Without slash</a></h1> <h1 class="Home_title__3DjR7">Welcome to <a href="https://nextjs.org">With slash?</a></h1> ``` Before ``` <h1 class="Home_title__3DjR7">Welcome to <a href="https://nextjs.org">Without slash</a></h1> <h1 class="Home_title__3DjR7">Welcome to <a href="https://nextjs.org/">With slash?</a></h1> ```
-
由 Anton Rieder 提交于
I believe this should read ["altogether"](https://www.merriam-webster.com/dictionary/altogether) not "all together".
-
- 12 11月, 2020 9 次提交
-
-
由 Josh Flayhart 提交于
In working with @devknoll on https://github.com/vercel/next.js/pull/17770 we thought it would be a good idea to update to the latest minor version from 1.2.20 -> 1.4.9 based on some bug fixes in these minor releases. I would like to separate this out to simplify the growing changeset in https://github.com/vercel/next.js/pull/17770, where we need to use `node-html-parser` to parse HTML for custom react components. The linked changeset above will take some time and there are some [useful bug fixes](https://github.com/taoqf/node-html-parser/commits/master) and features in this minor release we could benefit from anyway. Namely: - add nextSibling, nextElementSibling - missing node tag - `<style>` tag is not parsed correctly Also I think it's a good idea to separate this out for testing.
-
由 Joe Haddad 提交于
-
由 Joe Haddad 提交于
-
由 Joe Haddad 提交于
-
由 Joe Haddad 提交于
Fixes #18518
-
由 JJ Kasper 提交于
-
由 JJ Kasper 提交于
-
由 JJ Kasper 提交于
This ensures the mixed `notFound`/`redirect` error is shown correctly and adds an err.sh for the error. Closes: https://github.com/vercel/next.js/issues/18727
-
由 JJ Kasper 提交于
This fixes a few things related to optional catch-all routes and i18n. The first thing is it ensures the correct data route is generated on the client so that the locale isn't duplicated for an optional catch-all route, the next is it ensures the browser history is updated correctly when only a locale change is occurring, and then it also ensures we handle the locales and normalizing for fallback optional catch-all pages correctly. Tests have been added to ensure these cases are covered properly and we don't regress on them, these changes were also tested on Vercel [here](https://next-js-bug-i18n-root-params-nybg44l0b.vercel.app/) Fixes: https://github.com/vercel/next.js/issues/18633 Fixes: https://github.com/vercel/next.js/issues/19059
-