- 10 12月, 2020 2 次提交
-
-
由 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 7 次提交
-
-
由 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
-
由 Allen Hai 提交于
This PR removes the `next.config.js` file with an `env` key and instead modifies the setup script to create a `.env.local` file with the provided credentials. I also made some changes to the Deploy Button to ask for the environment variables when creating a new project.
-
由 Nicolás Figueroa 提交于
## Problems with the other implementation - pixel not working first time load page (this generate fake information to facebook analytics data) - package react-facebook-pixel error when try use events in code blocks or other pages with the current implementation - sometimes pixel mark twice pageview (this generate warning in facebook panel) - standar or custom events not working ## Solutions - Initialize pixel when entering each page (_document) - Now, we can use custom and standar events (utils/fpixel.js) - correct way to implement pixel according to facebook and guide facebook to implement in SPA - this solution is complemented with example "with-google-analytics" In my opinion, the other development has problems, but I preferred created a new example because the way to implement the base code is different. It seems that the other example is based on set the events from the Facebook control panel then this method limits an advanced implementation.
-
- 03 12月, 2020 3 次提交
-
-
由 Carmelo Scandaliato 提交于
The example stopped working when the GraphQL service [Graphcool](https://www.graph.cool/) shut down in July. I have replaced it with an [Hasura](https://hasura.io/) endpoint. Fixes #19093
-
由 Michael McQuade 提交于
Remove extra word "the"
-
由 Lee Robinson 提交于
We've received some feedback that the current note about calling API routes inside gSP/gSSP is confusing. This updates the wording to make it clear you can still use `fetch` in your application, and also to not say you "import" an API route. You import the _logic_ inside the route.
-
- 02 12月, 2020 10 次提交
-
-
由 JJ Kasper 提交于
This updates to the latest version of the `@ampproject/toolbox-optimizer` which contains updates for dependencies to remove the warnings on install from `npm` x-ref: https://github.com/vercel/next.js/pull/18994 Closes: https://github.com/vercel/next.js/issues/17416
-
由 JJ Kasper 提交于
-
由 Jeff Escalante 提交于
* make the error message more clear if webpack config comes back undefined * Update check and add test * bump * Update build-output test Co-authored-by: NJJ Kasper <jj@jjsweb.site>
-
由 JJ Kasper 提交于
-
由 Janicklas Ralph 提交于
-
由 Janicklas Ralph 提交于
Co-authored-by: NJJ Kasper <jj@jjsweb.site>
-
由 Vyacheslav Matyukhin 提交于
dotenv currently doesn't support inline comments (see https://github.com/motdotla/dotenv/issues/484), so it's misleading to use inline comments in documentation examples.
-
由 Pradip Caulagi 提交于
Build directory is `dist` and not `build`. The typo also makes gitignore not work correctly.
-
由 Luis Alvarez D 提交于
Updated one of the deployment steps to make sure the deployment of the home app is not done without pushing the blog URL first!
-
由 Steven 提交于
The [default loader](https://github.com/vercel/next.js/blob/17b91e7c76711308707bc8ab3308376af98170e6/packages/next/client/image.tsx#L488) and [imgix loader](https://docs.imgix.com/apis/rendering/format/q) use a quality of 75 if none is specified on the Image component. This PR does something similar for the cloudinary loader by utilizing `q_auto`, but it should yield even better results. > This setting can significantly reduce the file size without any degradation noticeable to the human eye, and without the need for you to individually analyze every image. https://cloudinary.com/documentation/image_optimization#use_q_auto_automatic_quality_and_encoding ### Example - [Before](https://res.cloudinary.com/demo/image/upload/woman.jpg) - 583KB - [After](https://res.cloudinary.com/demo/image/upload/q_auto/woman.jpg) - 46KB
-
- 01 12月, 2020 1 次提交
-
-
由 Vishnu Paduchuri 提交于
-
- 30 11月, 2020 3 次提交
-
-
由 Dennis Morello 提交于
This PR closes #19649.
-
由 Tim Neutkens 提交于
-
由 Wesley Tian 提交于
Either use `avoid` or `prevent` as verb, but not both.
-
- 28 11月, 2020 1 次提交
-
-
由 Mark Steggles 提交于
-
- 27 11月, 2020 1 次提交
-
-
- 26 11月, 2020 1 次提交
-
-
由 Guy Bedford 提交于
This reverts #18921 and ensures that the Babel runtime is only inlined as an absolute path when using PnP as before, but then including the correction this resolution as implemented by @merceyz only in the PnP cases, while keeping the diff to a minimum.
-