- 17 12月, 2020 4 次提交
-
-
由 Leo Toneff 提交于
This PR is an implementation of RFC #13276 (more specifically @banerjeesouvik's [suggestion](https://github.com/vercel/next.js/discussions/13276#discussioncomment-17874)) which solves #3322 by adding an extra parameter to the router events that'll allow you to see whether or not the route is shallow. This is a recreation of PR #13243.
-
由 JJ Kasper 提交于
-
由 Joe Haddad 提交于
-
由 JJ Kasper 提交于
This keeps track of required server files in a manifest file
-
- 16 12月, 2020 3 次提交
-
-
由 Tim Neutkens 提交于
Solves the following warning: > (node:1484) [DEP_WEBPACK_MAIN_TEMPLATE_REQUIRE_FN] DeprecationWarning: MainTemplate.requireFn is deprecated (use "__webpack_require__")
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
Co-authored-by: Nkodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
- 15 12月, 2020 1 次提交
-
-
由 Tuan Nguyen 提交于
-
- 14 12月, 2020 4 次提交
-
-
由 Dmitry Belyaev 提交于
Mention onClick property for next/link wrapping custom components
-
由 Joi Glifberg 提交于
Add note about import required to be explicit and dynamic required to be top-level module.
-
由 Erik August Johnson 提交于
Adds brief summary in Getting Started to explain the `pages/api` functionality. The intention here is reduce confusion to new users of Next.js as to what `pages/api` is and how it works.
-
由 Craig Johnson 提交于
Grammar correction.
-
- 13 12月, 2020 3 次提交
-
-
由 bram-l 提交于
Fixes #17813
-
由 JJ Kasper 提交于
-
由 Tim Neutkens 提交于
Solves some of the cache warnings when using webpack 5
-
- 12 12月, 2020 2 次提交
-
-
由 JJ Kasper 提交于
This makes sure the `locale` doesn't cause the wrong `href` to be resolved, this also ensures route specificity is correct when loading dynamic routes in production mode. Fixes: https://github.com/vercel/next.js/issues/19747
-
由 Hidetaka Okamoto 提交于
* docs: add example of Ionic with TypeScript * docs: fix example code typo * fix: support ionicons * docs: fix example code by ESLint and prettier * docs: example remove invalid config * Renamed example to with-ionic-typescript * Updated .gitignore * Updated readme * Updated package.json Co-authored-by: NHidetaka Okamoto <info@wp-kyoto.net> Co-authored-by: NLuis Alvarez <luis@vercel.com>
-
- 11 12月, 2020 3 次提交
-
-
由 Bruno Antunes 提交于
Currently if sizes is not defined, Next.js is setting sizes as: ``` (max-width: 640px) 640px, (max-width: 750px) 750px, (max-width: 828px) 828px, (max-width: 1080px) 1080px, (max-width: 1200px) 1200px, (max-width: 1920px) 1920px, (max-width: 2048px) 2048px, 3840px' ``` This pull request will make sizes be `100vw` by default, which will allow us to download "smaller" images than what's currently happening. In a demo app I have, the difference is between downloading 488KB vs 1.4MB (in images)
-
由 Joe Haddad 提交于
-
由 Joe Haddad 提交于
Fixes #18056
-
- 10 12月, 2020 4 次提交
-
-
-
-
由 JJ Kasper 提交于
Closes: https://github.com/vercel/next.js/issues/20044
-
由 Aral Roca Gomez 提交于
I applied the changes of the [migration guide of next-translate from 0.x of 1.0](https://github.com/vinissimus/next-translate/blob/1.0.0/docs/migration-guide-1.0.0.md)
-
- 09 12月, 2020 2 次提交
-
-
由 Lachlan Campbell 提交于
Fixes #19923. Before: <img width="564" alt="Screen Shot 2020-12-08 at 3 07 11 PM" src="https://user-images.githubusercontent.com/5074763/101535738-1adc6c00-3967-11eb-8c80-c7f2e75f8de5.png"> After: <img width="574" alt="Screen Shot 2020-12-08 at 3 07 18 PM" src="https://user-images.githubusercontent.com/5074763/101535742-1b750280-3967-11eb-828b-1ecac08c6511.png">
-
由 Joe Haddad 提交于
-
- 08 12月, 2020 8 次提交
-
-
由 Richard Lee 提交于
As seen in https://github.com/mhart/alpine-node, the `base` image tag has been renamed to `slim`.
-
由 Tim Neutkens 提交于
Adds an err.sh link to the production build missing message. Also clears up `valid` as `production`. Also fixes an edge case where an unhelpful error would be thrown because we checked for `.next` instead of `.next/BUILD_ID` Added the out directory location as the list line during export to make sure people know where the files are output. Fixes #19778 Fixes #19788
-
由 JJ Kasper 提交于
Noticed Azure tests have started failing after https://github.com/vercel/next.js/pull/19758 due to the middleware taking longer than the allotted threshold which adds unexpected logs to stderr. This attempts to resolve these test failures by increasing the allotted time for the middleware when running on Azure. x-ref: https://dev.azure.com/nextjs/next.js/_build/results?buildId=22617&view=logs&jobId=5ee44de4-e310-59d9-0ba5-4a271a649fb0&j=5ee44de4-e310-59d9-0ba5-4a271a649fb0&t=af3fb693-3771-5a1a-ec97-2ba4cc77f25c x-ref: https://dev.azure.com/nextjs/next.js/_build/results?buildId=22619&view=logs&jobId=5ee44de4-e310-59d9-0ba5-4a271a649fb0&j=5ee44de4-e310-59d9-0ba5-4a271a649fb0&t=af3fb693-3771-5a1a-ec97-2ba4cc77f25c
-
由 Sung Hah Hwang 提交于
typos
-
由 Nicolás Figueroa 提交于
(@lfades), I forgot remove package react-facebook-pixel that is not necessary now and update readme doc.
-
由 Tim Neutkens 提交于
Fixes #19939
-
由 Joe Haddad 提交于
-
由 JJ Kasper 提交于
This ensures locales aren't applied for the trailing slash redirect un-necessarily Fixes: https://github.com/vercel/next.js/issues/19784
-
- 07 12月, 2020 1 次提交
-
-
由 Daniel Kempner 提交于
## Why Some users prefer to use a custom server implementation that handles body parsing. If they do this, they have no way to opt out of all body parsing in API Routes. Requests with bodies die if next's `bodyParser` is not disabled. Requests just hang forever. Instead of adding [this config](https://nextjs.org/docs/api-routes/api-middlewares#custom-config) to every API Route, we do a simple check to avoid parsing the body twice. Fixes #8315 Fixes #7960
-
- 04 12月, 2020 5 次提交
-
-
由 JJ Kasper 提交于
-
由 Pepijn Senders 提交于
Nitpicky change, but the version string contained a double `|`, implying that there might be an empty value between `process.env.__NEXT_VERSION` and the environment variables.
-
由 JJ Kasper 提交于
This makes sure to note how custom-routes need to be prefixed when `locale: false` is used for routes to be matched correctly. Closes: https://github.com/vercel/next.js/issues/19703
-
由 JJ Kasper 提交于
This ensures i81n custom routes are resolving correctly, it also corrects redirects for default locales when `locale: false` is not used, and this also simplifies the resolving for custom routes with i18n in `next-server` adding types for the i18n config. This also adds additional tests to prevent regression and starts leveraging a shared `NextConfig` type to allow us to share types for config values. Fixes: https://github.com/vercel/next.js/issues/19521 Fixes: https://github.com/vercel/next.js/issues/19403 Fixes: https://github.com/vercel/next.js/issues/19302 Fixes: https://github.com/vercel/next.js/issues/19227
-
由 Prateek Bhatnagar 提交于
- Making font optimizations as default - Re-enabling tests - Fixes #19159
-