- 22 12月, 2020 6 次提交
-
-
由 Juny 提交于
Fixes: https://github.com/vercel/next.js/issues/16926 I do not know this is the right way. Please review it.
-
由 Joe Haddad 提交于
This PR fixes webpack 5 compatibility with older betas.
-
由 JJ Kasper 提交于
This ensures the pages-manifest only includes forward slashes and not backslashes when adding i18n page references, this also adds tests ensuring we don't regress on this in the i18n-support test suite. Fixes: https://github.com/vercel/next.js/issues/20330
-
由 Joe Haddad 提交于
-
由 Joe Haddad 提交于
There's currently two bugs with the font optimization, but we'd really like to ship a stable version. To unblock the stable release, we're **temporarily** reflagging this. It'll be unflagged on canary again!
-
由 Tim Neutkens 提交于
Adds profiling for terser and css-minimizer. Will move the old profiler to this new system as well.
-
- 18 12月, 2020 6 次提交
-
-
由 Matt Wood 提交于
When using `getServerSideProps` with Typescript, it looks like it's expecting `req` to be a plain `IncomingMessage` from `http`, but Next middleware (?) is adding `cookies`: ![image](https://user-images.githubusercontent.com/22530815/100816292-680e8a00-340b-11eb-8c40-19ec4f9ea356.png) Here's a reproduction showing the example: https://codesandbox.io/s/nextjs-server-side-props-cookies-vr547?file=/pages/index.tsx In the terminal, you can see that there is a value for cookies, but `IncomingMessage` doesn't include it by default. I still need to get more familiar with all the Next.js internals, but I imagine there are a few other places where this type could be used if cookies are being included. Any help would be appreciated.
-
由 Darsh Patel 提交于
Fixes: #20289 I noticed the following errors about missing icon files while working on the progressive-web-app example <img width="639" alt="Screenshot 2020-12-18 at 9 16 25 AM" src="https://user-images.githubusercontent.com/11258286/102572751-e3ae4d80-4112-11eb-896a-2facfb5e16d3.png"> I've added the missing icon files and updated the path :)
-
由 Vishnu Paduchuri 提交于
Build Fails due to Invalid Token error, adding SENTRY_URL fixed the issue.
-
由 Bogdan Chadkin 提交于
Co-authored-by: NTim Neutkens <timneutkens@me.com> Co-authored-by: Nkodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
由 Joe Haddad 提交于
-
由 Vitor Barbosa 提交于
This should fix source map config description text.
-
- 17 12月, 2020 6 次提交
-
-
由 Tim Neutkens 提交于
Makes https://www.npmjs.com/package/@zeit/next-source-maps a built-in feature so that it can be deprecated.
-
由 ykdojo 提交于
-
由 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 提交于
-