- 16 11月, 2020 4 次提交
-
-
由 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 17 次提交
-
-
由 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 ```
-
由 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 7 次提交
-
-
由 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 提交于
-