- 13 11月, 2020 13 次提交
-
-
由 Joe Haddad 提交于
-
由 Steven 提交于
- Fixes #19120 - Closes #18413 - Related to #19041
-
由 Joe Haddad 提交于
Co-authored-by: NGerald Monaco <gbmonaco@google.com>
-
由 Joe Haddad 提交于
-
由 Akuma Isaac Akuma 提交于
`url` object is an instance of `url.URL` which has no property called `query` and it's causing an error with Next image-optimizer as you can see with the error log below. ```log TypeError: Cannot destructure property 'url' of 'parsedUrl.query' as it is undefined. at imageOptimizer (/[redacted]/node_modules/next/next-server/server/image-optimizer.ts:51:11) at Object.fn (/[redacted]/node_modules/next/next-server/server/next-server.ts:617:11) at Router.execute (/[redacted]/node_modules/next/next-server/server/router.ts:200:40) at DevServer.run (/[redacted]/node_modules/next/next-server/server/next-server.ts:1017:41) at DevServer.run (/[redacted]/node_modules/next/server/next-dev-server.ts:406:18) at DevServer.handleRequest (/[redacted]/node_modules/next/next-server/server/next-server.ts:437:14) at /[redacted]/server/next-wrapper.ts:9:5 ```
-
由 LittleboyHarry 提交于
1. updates the `.gitignore` for this example to ignore the temporary output folders. ( similar to #15783 ) 2. change yarn run script to npm run script ( I don't like use yarn currently. )
-
由 Tuan Nguyen 提交于
-
由 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> ```
-
由 JJ Kasper 提交于
-
由 Anton Rieder 提交于
I believe this should read ["altogether"](https://www.merriam-webster.com/dictionary/altogether) not "all together".
-
- 12 11月, 2020 23 次提交
-
-
由 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.
-
由 Tim Neutkens 提交于
There are no breaking changes but we're seeing some reports of confusion because there's no section for 9 to 10, so this adds it.
-
由 Joe Haddad 提交于
-
由 Joe Haddad 提交于
-
由 Ludovico Fischer 提交于
-
由 Mihai Pocorschi 提交于
-
由 Joe Haddad 提交于
-
由 George 提交于
-
由 Joe Haddad 提交于
Fixes #18518
-
由 JJ Kasper 提交于
-
由 JJ Kasper 提交于
-
由 Yann Pringault 提交于
Co-authored-by: NLuis Alvarez D <luis@vercel.com>
-
由 jose-donato 提交于
Example for adding a service worker without any plugin or custom server
-
由 Lucas Varela 提交于
* Add info about SENTRY_URL on source map uploading * Update examples/with-sentry/README.md Co-authored-by: NLee Robinson <me@leerob.io> Co-authored-by: NLuis Alvarez D <luis@vercel.com>
-
由 Vyacheslav Konyshev 提交于
-
## Change - Update package versions - Replace @storybook/addons, @storybook/addon-actions to @storybook/addon-essentials - Replace examples of button, the action function is legacy: https://storybook.js.org/docs/react/essentials/actions#advanced--legacy-usage
-
由 Marco Valsecchi 提交于
Use useRouter over Router and add a workaround for the issue #11639
-
由 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
-
由 Daniel Stocks 提交于
Added `<Html>` and `<Head>` components in the custom `_document.js` for the with-fela example package This fixes an issue where fela `<style>` tags were not added and sent as part of the server-side rendered HTML payload, causing a FOUC.
-
由 Joe Haddad 提交于
-
由 Joe Haddad 提交于
This pull request completely replaces our old page loader with a brand new route loader. Our existing comprehensive test suite means I did not need to add a bunch of tests. I did add them where behavior was added or fixed. Summary of the changes: - Eagerly evaluates prefetched pages in browser idle time (speeds up transitions) - Router is **no longer frozen** indefinitely if the Build Manifest never arrives - Router is **no longer frozen** indefinitely if a page fails to bootstrap - New `withFuture` utility instead of ad-hoc deduping per resource - Prefetching is now delayed until browser idle time to not impact TTI - Browsers without `prefetch` now fall back to eager evaluation instead of using `preload` - We're now ready to serve non-static assets **with `no-store` without breaking prefetching** - **Application can now hydrate without fetching CSS assets—this is a huge performance win that was previously blocking hydration** --- The minor size increase here is unfortunate, but we have to incur it for correctness. --- Fixes #18389 Fixes #18642
-
由 JJ Kasper 提交于
-
- 11 11月, 2020 4 次提交
-
-
由 Steven 提交于
Fixes #18356
-
由 Kristoffer K 提交于
**What's the problem this PR addresses?** https://github.com/vercel/next.js/pull/18768 started to ncc `@babel/plugin-transform-runtime` which broke its Yarn PnP support since the version of `resolve` it uses can't be patched by Yarn. Fixes https://github.com/yarnpkg/berry/runs/1359235077?check_suite_focus=true#step:5:79 cc @guybedford **How did you fix it?** Resolve the absolute path to `@babel/runtime` so it doesn't have to go through `resolve` --- Fixes https://github.com/vercel/next.js/issues/19026
-
由 Daniel K 提交于
This confused me a lot, because in the case of `withBundleAnalyzer({})` it will ignore any previous config and basically override everything. Furthermore, it makes more sense to move the call with `enabled` option inside so it's aligned with other plugins approach.
-
由 JJ Kasper 提交于
Updates to the latest version of `chokidar` x-ref: https://github.com/vercel/next.js/issues/17416
-