- 18 11月, 2020 9 次提交
-
-
由 Joe Haddad 提交于
-
由 Vitor Dino 提交于
-
由 Luis Alvarez D 提交于
Co-authored-by: Nkodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
由 Ondřej Chrastina 提交于
-
由 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
-
- 17 11月, 2020 5 次提交
-
-
由 Tim Neutkens 提交于
-
由 Lee Robinson 提交于
Building off the "Migrating to Next.js" section started, this doc provides information on using `rewrites`, `redirects`, and micro-frontends to incrementally adopt Next.js in your codebase.
-
由 GH Lee 提交于
ref. https://github.com/vercel/next.js/pull/14519, https://github.com/vercel/next.js/pull/15062 Add limitation for Anonymous arrow functions.
-
由 Paul van Dyk 提交于
fixes the event argument inside the function call - argument is `e` but `event` was used instead
-
由 Luis Alvarez D 提交于
~Updated the `with-zones` example and docs to use `@vercel/next` instead of `@now/next` and also updated the readme instructions with better steps.~ ~Related to https://github.com/vercel/next.js/issues/12317 - Looks like there may be an issue with the example but it continues to work as expected to me, moving away from `@now/next` may help.~ Fixes https://github.com/vercel/next.js/issues/12317 Closes https://github.com/vercel/next.js/issues/12317 Moved the example to use [Vercel Monorepos](https://vercel.com/blog/monorepos). Locally it switches to `next dev` instead of `vercel dev`.
-
- 16 11月, 2020 5 次提交
-
-
由 Abdullah Mzaien 提交于
Upgraded charkra ui and peer dep and fixed the icon to follow the new api
-
由 Amr Saber 提交于
Update the mentioned redirection status message.
-
由 Yordis Prieto 提交于
The intention is to show people the correlation between things, in this case, understand the usage of the same key from the props and the rehydration. Hopefully, this change will bring value as it has done with some Juniors already.
-
由 Joe Haddad 提交于
-
由 JJ Kasper 提交于
Co-authored-by: NJoe Haddad <joe.haddad@zeit.co>
-
- 14 11月, 2020 12 次提交
-
-
由 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
-
由 Steven 提交于
This page is useful for testing out layouts so we moved that section to the top.
-
由 Steven 提交于
This will make it clear which properties are not allowed
-
由 Steven 提交于
This unifies the docs to always use `<Image>` instead of `<img>` so we can set readers up for success.
-
由 Tony Spiro 提交于
-
由 xeust 提交于
Add an example for using Next.js with Deta Base on Vercel.
-
由 Joe Haddad 提交于
-
由 Steven 提交于
Fixes #18557
-
- 13 11月, 2020 9 次提交
-
-
由 Balázs Orbán 提交于
likelyhood -> likelihood
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
-
由 Joe Haddad 提交于
-
由 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 ```
-