- 05 1月, 2021 13 次提交
-
-
由 Tuan Nguyen 提交于
`getLoginSession` takes only one argument
-
由 Tim Neutkens 提交于
-
由 JJ Kasper 提交于
Adds the `pr` section from https://docs.microsoft.com/en-us/azure/devops/pipelines/repos/github?view=azure-devops&tabs=yaml#pr-triggers to filter paths that don't require test runs on PRs.
-
由 Jan Varho 提交于
Currently pages with `notFound: false` from `getServerSideProps` behave the same as `notFound: true`, i.e. just having the key is enough to result in a 404. This fixes the check in render.tsx and adds tests for it.
-
由 Lee Robinson 提交于
Adds an example using `lru-cache` to implement a simple rate limiter for API routes ([Serverless Functions](https://vercel.com/docs/serverless-functions/introduction)). **Demo: https://nextjs-rate-limit.vercel.app/**
-
由 Jesse Jafa 提交于
Closes https://github.com/vercel/next.js/issues/19481 The current text implies `query` is a string. IMO it would be better if it clarified that `query` is an object containing the query string's keys and values Edit: Relevant docs url: https://nextjs.org/docs/basic-features/data-fetching#getserversideprops-server-side-rendering
-
由 zoomdong 提交于
https://ant.design/docs/react/getting-started#Import-on-Demand At the document, We don't need to use `babel-import-plugin` to `Import on Demand`.
-
由 Manaia Junior 提交于
-
由 Justin Philpott 提交于
Hi, I'm submitting this PR for consideration as a new example app showing Styled JSX with SCSS working inside and outside storybook with example components. Only known issue: I noticed that when running this example with: `$ yarn next ./examples/with-storybook-styled-jsx-scss` I receive the following error: ``` error - ./pages/_app.js Error: [BABEL] .../next.js/examples/with-storybook-styled-jsx-scss/pages/_app.js: Cannot find module 'styled-jsx-plugin-sass' (While processing: ".../next.js/node_modules/next/babel.js") ``` However I notice that this same missing module error is triggered when running this existing example app "with-styled-jsx-scss". Any changes/tweaks needed? Thanks!
-
由 mongolyy 提交于
I made the following changes. - Addition of procedure for setting private_key - Addition of procedure for creating a database and setting database_url
-
由 Joe Haddad 提交于
This pull request correctly assigns boolean attributes for `<script />` to match the element as it is created by a server-side render. Prior to this pull request, we'd double-execute `<script>` tags with the `async`, `defer`, or `nomodule` property. --- Fixes #9070
-
由 matamatanot 提交于
As with `const width`, it should be declared just before it is used.
-
由 Kristoffer K 提交于
**What's the problem this PR addresses?** `@next/mdx` adds the webpack loader `@mdx-js/loader` without resolving it to an absolute path Depends on https://github.com/vercel/next.js/pull/17606 **How did you fix it?** `require.resolve` the webpack loader before adding it
-
- 04 1月, 2021 27 次提交
-
-
由 Joe Haddad 提交于
-
由 Kristoffer K 提交于
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
This file has been replaced by the bug-report issue template
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
-
由 Alexander Kachkaev 提交于
This PR is a small follow-up to #14705. It saves Next.js users from falling into a [pretty nasty trap](https://github.com/nodejs/node/issues/36620) in which I ended up last Friday. It took more than two days to investigate what was going on, so I hope I'm the last person who’s doing it
😅 Next.js-specific MWE: https://github.com/kachkaev/hanging-response-in-next-via-redirect-plus-compression (needs to be ran locally using Node 14.0.0+). > <img width="521" alt="Screenshot 2020-12-24 at 20 50 00" src="https://user-images.githubusercontent.com/608862/103105989-a9b8dc00-4629-11eb-9be3-5108755604bf.png"> To reproduce the bug I’m fixing: 1. Pick a large http body size (64 or 128 KB) 1. Check _Call res.end() after res.redirect() in /api/redirect_ 1. Navigate to a heavy page or an api handler via redirect 1. Observe that the http response is never finished. If you set `compress` to `false` in `next.config.js` or pick a small payload size (< `zlib.Z_DEFAULT_CHUNK` after compression), the bug will not be observed. This is explained by the use of `res.on("drain", ...)` [by the `compression` package](https://github.com/expressjs/compression/blob/3fea81d0eaed1eb872bf3e0405f20d9e175ab2cf/index.js#L193-L218). The package itself is not the reason for an issue though, it seems to be in the Node’s built-in `http` package. I’m happy to provide more info or GitHub CI to the MWE if needed. I was also thinking of adding some Next.js-specific testing, but could not come up with a compact and clear test plan. Happy to do this if there are any ideas. cc @botv (author of #14705) -
由 Tim Neutkens 提交于
Fixes #20487
-
由 Leo Lamprecht 提交于
Updates the env documentation to mention `.vercelignore` when using the Vercel CLI. Also clears up parts of the other paragraphs and updates the links as these topics now have dedicated pages in the Vercel docs.
-
由 JJ Kasper 提交于
Follow-up to https://github.com/vercel/next.js/pull/20628 this ensures `isReady` is not initially true when the query isn't present but the page is an automatically statically optimized dynamic route
-
由 Vitali Zaidman 提交于
-