status stringclasses 1
value | repo_name stringclasses 13
values | repo_url stringclasses 13
values | issue_id int64 1 104k | updated_files stringlengths 11 1.76k | title stringlengths 4 369 | body stringlengths 0 254k ⌀ | issue_url stringlengths 38 55 | pull_url stringlengths 38 53 | before_fix_sha stringlengths 40 40 | after_fix_sha stringlengths 40 40 | report_datetime timestamp[ns, tz=UTC] | language stringclasses 5
values | commit_datetime timestamp[us, tz=UTC] |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
closed | vercel/next.js | https://github.com/vercel/next.js | 18,337 | ["packages/next/build/webpack/loaders/next-serverless-loader.ts", "packages/next/client/index.tsx", "packages/next/next-server/server/next-server.ts", "test/integration/i18n-support/pages/_app.js", "test/integration/i18n-support/pages/another.js", "test/integration/i18n-support/pages/gsp/fallback/[slug].js", "test/inte... | Wrong defaultLocale on non-index pages on client-side and detected language redirect doesn't work. | # Bug report
## Describe the bug
On non-index pages `defaultLocale` overrided was with detected language, only happend on client-side. At the same time `defaultLocale` was correct on the server-side. Also on non-index pages detected language redirect doesn't work.
## To Reproduce
Check out the [repository](... | https://github.com/vercel/next.js/issues/18337 | https://github.com/vercel/next.js/pull/18708 | c8d26edf5794c65a6b9d83b11ffbd6fb8412c9c5 | 7b6a61a750d888a1fa0c213c9b1916db1e21e740 | 2020-10-27T20:50:08Z | javascript | 2020-11-02T23:00:41Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 18,332 | ["packages/next/next-server/lib/router/router.ts", "test/integration/i18n-support/pages/frank.js", "test/integration/i18n-support/test/index.test.js"] | next/link & next/router - using getStaticProps with a route that starts with the same characters as defaultLocale | # Bug report
## Describe the bug
When using a `defaultLocale` (e.g. `"de"`) in combination with `getStaticProps` and a route that starts with the same characters as the `defaultLocale` (e.g. `/pages/details/[slug].js`) we cannot visit the page when using `next/link` or `next/router`.
## To Reproduce
Chec... | https://github.com/vercel/next.js/issues/18332 | https://github.com/vercel/next.js/pull/18712 | 7b6a61a750d888a1fa0c213c9b1916db1e21e740 | 3f84a55ba38649ee81fbc703ccb1173de896d4de | 2020-10-27T20:12:42Z | javascript | 2020-11-02T23:32:56Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 18,293 | ["packages/next/build/webpack/loaders/next-serverless-loader.ts", "test/integration/i18n-support/pages/not-found/blocking-fallback/[slug].js", "test/integration/i18n-support/test/index.test.js"] | [9.5.6-canary.17][notFound][Vercel] incorrect props in custom 404-page when using blocking fallback | # Bug report
## Describe the bug
I use the `notFound` feature on SSG pages with enabled **blocking** fallback. The custom 404-page gets incorrect props from `getStaticProps` when `notFound` occurs. This happens only when an app is deployed to Vercel.
## To Reproduce
Repository: [next.js-bug-not-found-props]... | https://github.com/vercel/next.js/issues/18293 | https://github.com/vercel/next.js/pull/18300 | f7ba546e8afca0e72c5198aa5e383d1bf85dc655 | 0f2505147031ffa4e767a4cce2a8634a32df42d8 | 2020-10-27T12:38:15Z | javascript | 2020-10-27T15:11:51Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 18,275 | ["docs/advanced-features/automatic-static-optimization.md", "docs/api-reference/next.config.js/static-optimization-indicator.md", "docs/manifest.json", "examples/with-magic/next.config.js", "packages/next/build/webpack-config.ts", "packages/next/client/dev/prerender-indicator.js", "packages/next/client/next-dev.js", "p... | Default Static Optimization Indicator to false | # Feature request
For validation of this feature request see [almost all the comments on "How to remove the clickable label "Prerendered Page" and loading Icon ? #7945"](https://github.com/vercel/next.js/issues/7945).
The automatic Static Optimization Indicator is providing important information, but that informa... | https://github.com/vercel/next.js/issues/18275 | https://github.com/vercel/next.js/pull/18629 | fb58d95db7a703ba1b0132000882716f44a0200e | 197d46ddb9bebc4a74360e66f50b091edd811ae0 | 2020-10-26T22:21:28Z | javascript | 2020-11-02T08:27:36Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 18,228 | ["packages/next/lib/is-serializable-props.ts", "test/unit/is-serializable-props.test.js"] | Nested empty arrays incorrectly detected as cyclical | # Bug report
## Describe the bug
Empty arrays that are nested in other arrays are detected as cyclical, despite no cycle existing.
## To Reproduce
```js
export const getServerSideProps: GetServerSideProps = async (context) => {
const x = [];
return {props: {foo: [x, [x]]}};
};
```
## Expecte... | https://github.com/vercel/next.js/issues/18228 | https://github.com/vercel/next.js/pull/18232 | 91d4aa54506a68a99f99b8edcfea10a73bea2ec2 | bbde18f1203342017e55e652172e459441295c03 | 2020-10-25T18:56:42Z | javascript | 2020-11-09T14:25:41Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 18,212 | ["packages/next/next-server/lib/router/router.ts", "packages/next/next-server/server/next-server.ts", "test/integration/i18n-support/pages/404.js", "test/integration/i18n-support/test/index.test.js"] | [9.5.6-canary.14][notFound] incorrect props in custom 404-page when using fallback | # Bug report
## Describe the bug
I use the experimental `unstable_notFound` feature on SSG pages with enabled fallback. The custom 404-page gets incorrect props from `getStaticProps` when `notFound` occurs.
## To Reproduce
Repository: [next.js-bug-not-found-props](https://github.com/rokinsky/next.js-bug-not... | https://github.com/vercel/next.js/issues/18212 | https://github.com/vercel/next.js/pull/18214 | 11fce3a6861c2415ed2dfdc411e428e142373f96 | 9a770bde841d39a5351b9e371b914c7f6dd84e70 | 2020-10-24T22:45:09Z | javascript | 2020-10-27T09:40:17Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 18,196 | ["packages/next/next-server/server/next-server.ts", "packages/next/next-server/server/render.tsx", "test/integration/i18n-support/pages/404.js", "test/integration/i18n-support/test/index.test.js", "yarn.lock"] | [9.5.6-canary.13][notFound] custom 404-page rendering crashes in prod mode | # Bug report
## Describe the bug
I use the experimental `unstable_notFound` feature on SSG/ISG pages and it fails in production mode when the custom-404 page uses `getStaticProps`.
## To Reproduce
Repository: [next.js-bug-not-found](https://github.com/rokinsky/next.js-bug-not-found)
Steps to reproduce the ... | https://github.com/vercel/next.js/issues/18196 | https://github.com/vercel/next.js/pull/18205 | 299fba162a539912e05c5000aae68641f3233dc5 | ebee2bafa935b6474d87a45060ffeb9b7770359f | 2020-10-24T14:42:54Z | javascript | 2020-10-24T19:22:48Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 18,163 | ["docs/advanced-features/multi-zones.md"] | [Docs] Deprecated @now/next used in code example | On [Multi Zones](https://nextjs.org/docs/advanced-features/multi-zones) we have this code example:
```json
{
"version": 2,
"builds": [
{ "src": "blog/package.json", "use": "@now/next" },
{ "src": "home/package.json", "use": "@now/next" }
],
"routes": [
{ "src": "/blog/_next(.*)", "dest": ... | https://github.com/vercel/next.js/issues/18163 | https://github.com/vercel/next.js/pull/18246 | a9984e4026256c7e300678be696221327a0dcdbc | 774286fcc3aea59f7c284c84b78b274eaec4958a | 2020-10-23T09:11:21Z | javascript | 2020-10-27T12:45:52Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 18,127 | ["packages/next/src/client/index.tsx"] | next/router - push function changes between renders when called | # Bug report
Depending on the `push` function of `useRouter` causes an infinite loop when the `push` function is called from inside a `useEffect`
## To Reproduce
1. Set up a catch-all optional dynamic route `[[...slug]].js`
2. Render the following component from this page
Example component
```
const BugExamp... | https://github.com/vercel/next.js/issues/18127 | https://github.com/vercel/next.js/pull/52177 | 4f75c7993815dac50a6db3e078c51e6ae8d5bbdc | ae3db7ce6b0c09cc9bc3e96105cb180ace516505 | 2020-10-22T10:54:39Z | javascript | 2023-07-04T09:11:21Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 18,096 | ["packages/next/build/babel/preset.ts", "test/unit/next-babel.unit.test.js"] | "React is not defined" when using a custom _app.tsx and .babelrc using React 17 | # Bug report
After upgrading to React 17, I can no longer compile my project with a custom `.babelrc` file without importing React in every `*.tsx` file. Having a `_app.tsx` file seems to be required to reproduce the issue. The error returned is:
```
Error occurred prerendering page "/". Read more: https://err.sh/... | https://github.com/vercel/next.js/issues/18096 | https://github.com/vercel/next.js/pull/19136 | 8ff52136146b3276bf53d40c7ee1cfe7f0c9647f | 415d7fd75ebfca4dc796bb7892a348bab3fa4920 | 2020-10-21T16:55:52Z | javascript | 2020-11-13T07:41:54Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 18,056 | ["packages/next/compiled/terser-webpack-plugin/cjs.js", "packages/next/compiled/terser/LICENSE", "packages/next/compiled/terser/bundle.min.js", "packages/next/package.json", "yarn.lock"] | Bumping project to 9.5.5 causes build errors | # Bug report
## Describe the bug
Upgrading to 9.5.5 causes `Failed to compile` error when running `next build`
```
static/chunks/228a2a7ba78e3ffd319f6ce5014dd859657e6b72.6c045b2e351579d8c08d.js from Terser
TypeError: e.computed_key is not a function
at Array.some (<anonymous>)
```
## To Reproduce
... | https://github.com/vercel/next.js/issues/18056 | https://github.com/vercel/next.js/pull/20063 | a5fea53bc8bcfefd0c46df2ab7e598404cbf42ef | 1692e931d97c9c17b5b62080e95697a42b61aab2 | 2020-10-20T16:21:01Z | javascript | 2020-12-10T16:49:23Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 18,048 | ["packages/next/package.json", "yarn.lock"] | upgrade resolve-url-loader to 3.1.2 to resolve Prototype Pollution vulnerability | # Bug report
## Describe the bug
resolve-url-loader is a production dependency inside next.
resolve-url-loader relies on adjust-sourcemap-loader as a production dependency.
adjust-sourcemap-loader relies on object-path as a production dependency.
object-path has a high severity vulnerability described here: ht... | https://github.com/vercel/next.js/issues/18048 | https://github.com/vercel/next.js/pull/18064 | 48a95d58048c4556417c0e2fbc05799a5b33a9ac | d4f53ec2bcecb0774f1e0c20cd10b353e97dbbf2 | 2020-10-20T09:30:22Z | javascript | 2020-10-20T20:26:38Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 18,044 | ["packages/next/package.json", "yarn.lock"] | Audit errors in node-fetch and object-path | # Bug report
## Describe the bug
There are audit errors for 2 transitively used dependencies.
## To Reproduce
1. Install next.js 9.5.5 into an npm project
2. Execute `npm audit`
## Expected behavior
No audit errors should be shown
## Actual behavior
<details>
<summary>`npm audit` output</summa... | https://github.com/vercel/next.js/issues/18044 | https://github.com/vercel/next.js/pull/18087 | 6212823735dc7e7bd6c4d13ae219ae6430680d58 | 71f3e8db7b4c952f07abe7b781e4497864eb56ea | 2020-10-20T08:40:32Z | javascript | 2020-10-21T16:04:31Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 18,023 | ["examples/with-firebase-authentication/utils/auth/mapUserData.js"] | Firebase authentication example not working correctly | # Bug report
## Describe the bug
The repo
https://github.com/vercel/next.js/tree/canary/examples/with-firebase-authentication
allows login but fails to fetch food. I see the following error message:
```
errorInfo: {
code: 'auth/argument-error',
message: 'Decoding Firebase ID token faile... | https://github.com/vercel/next.js/issues/18023 | https://github.com/vercel/next.js/pull/18074 | 91eb984d58cf4b85269b6ecd5d510700dea780f0 | c28d39e47d7337636e832134b26d6214357fe3d4 | 2020-10-19T18:21:10Z | javascript | 2020-10-21T01:17:39Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 17,930 | ["packages/next/client/index.tsx", "packages/next/client/page-loader.ts"] | Failed to read the 'cssRules' property from 'CSSStyleSheet': Cannot access rules | # Bug report
## Describe the bug
DOMException: Failed to read the 'cssRules' property from 'CSSStyleSheet': Cannot access rules
## To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:
1. Setting assetPrefix to subdomain
2. Use withSass default config, import scss fil... | https://github.com/vercel/next.js/issues/17930 | https://github.com/vercel/next.js/pull/18723 | b1503e13e8d767105a2e70038e94e695fb42e9fd | 27d7b76a39c23da1aa6455e0c2c36d6e3c1aad6c | 2020-10-16T05:11:06Z | javascript | 2020-11-03T12:50:15Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 17,828 | ["docs/advanced-features/custom-app.md", "docs/advanced-features/custom-document.md"] | Clarify use of getStaticProps / getServerSideProps with app / document | # Feature request
## Describe the solution you'd like
We currently don't explicitly mention you can't use `getStaticProps` or `getServerSideProps` with `_app.js` or `_document.js` in the docs. These proposals are still in RFC.
We should add a note to both the app and document section of the docs to mention thi... | https://github.com/vercel/next.js/issues/17828 | https://github.com/vercel/next.js/pull/17839 | d73b34c3fd4008d3a8a175ad52310c83c1e5c8a4 | f1b3818dadab089c9c4faaa2695372c9e07e2c96 | 2020-10-12T21:26:54Z | javascript | 2020-10-13T19:17:47Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 17,738 | ["packages/next/next-server/lib/router/router.ts", "test/integration/gssp-redirect/test/index.test.js"] | browser back issue of experimental redirects from getServerSideProps / getStaticProps | # Bug report
## Describe the bug
## To Reproduce
Here's simple repo to reproduce
https://github.com/TasukuUno/repro-nextjs-17738
1. Prepare a page using `unstable_redirect` option in GSSP or GSP... | https://github.com/vercel/next.js/issues/17738 | https://github.com/vercel/next.js/pull/17741 | d2e7f3c76992dc0392acc3ac9e2a023143891cc2 | 3f22490a59bf663e5d20d1c486c8111d64a278f9 | 2020-10-09T07:15:38Z | javascript | 2020-10-27T05:14:23Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 17,733 | ["packages/create-next-app/helpers/git.ts"] | Change default branch for create-next-app output to be `main` | # Feature request
## Is your feature request related to a problem? Please describe.
Currently, the generated codebase from `npx create-next-app x` yields a project named `x` with git initialized with `master` as the default branch. To match up with GitHub, it should be `main`.
| https://github.com/vercel/next.js/issues/17733 | https://github.com/vercel/next.js/pull/17745 | 266c7ed74c52cfe73c304a1adac7b986f4b723a5 | 19febb10c03280c200a00033a7d59ceded0d7923 | 2020-10-09T03:42:54Z | javascript | 2020-11-07T14:46:17Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 17,592 | ["errors/invalid-project-dir-casing.md", "errors/manifest.json", "packages/next/cli/next-build.ts", "packages/next/cli/next-dev.ts", "packages/next/cli/next-export.ts", "packages/next/cli/next-lint.ts", "packages/next/cli/next-start.ts", "packages/next/lib/get-project-dir.ts"] | 'Error: Invalid hook call. Hooks can only be called inside of the body of a function component' | # Bug report
## Describe the bug
I keep 'Error: Invalid hook call. Hooks can only be called inside of the body of a function component' after starting the next development server. This is the default next app with no configuration from me at all
## To Reproduce
1. Start a new next app with `npx create-next-... | https://github.com/vercel/next.js/issues/17592 | https://github.com/vercel/next.js/pull/29205 | faa39038ef458f69a3eb6aa9046d97a717532950 | ead56eaab68409e96c19f7d9139747bac1197aa9 | 2020-10-03T17:37:09Z | javascript | 2021-09-22T21:29:27Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 17,505 | ["docs/basic-features/built-in-css-support.md"] | The docs for global CSS imports from node_modules don't note the required version | The page should have a note saying that global CSS imports from node_modules require Next.js v9.5.4. | https://github.com/vercel/next.js/issues/17505 | https://github.com/vercel/next.js/pull/17506 | f06c58911515d980e25c33874c5f18ade5ac99df | 816798569a56c97108ecff37a85e6a3fd85648ab | 2020-10-01T02:35:00Z | javascript | 2020-10-01T08:58:22Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 17,454 | ["docs/manifest.json", "docs/migrating/from-create-react-app.md"] | Add migration guide from Create React App | # Feature request
As a user of [x] framework/language, I'd love to see an easy path towards migrating to Next.js
## Describe the solution you'd like
Documentation around common providers and how exactly you can switch to Next.js from them.
## Additional context
Let's start with a few of the most popular... | https://github.com/vercel/next.js/issues/17454 | https://github.com/vercel/next.js/pull/21212 | f8fecf57c3673975fcc33d3a979fc538de149b08 | 5d98874e8fbfde9188090c1b93eeb62cc141f397 | 2020-09-29T18:19:15Z | javascript | 2021-01-18T23:37:32Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 17,416 | ["packages/next/package.json", "yarn.lock"] | Obsolete and vulnerable dependencies (CVE-2020-15168 and CVE-2019-20149) | # Bug report
Hello. Several vulnerabilities were revealed in the chokidar and ampproject/toolbox-optimizer package dependencies. The packages causing the "security issues" are kind-of and node-fetch. Detailed info about CVE-2019-20149 and CVE-2020-15168 vulnerabilities are available here ([1] and [2]).
next@9.5.3... | https://github.com/vercel/next.js/issues/17416 | https://github.com/vercel/next.js/pull/19722 | 7ae76f4326840fb92cc542d867c5b9c27333a80c | bb1bdbb10fb7f8b4f5d6b05c5e63ba589151cb50 | 2020-09-28T10:31:00Z | javascript | 2020-12-02T12:55:43Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 17,299 | ["examples/with-redux-wrapper/store/store.js"] | with-redux-wrapper example bug | # Bug report
## Describe the bug
In with-redux-wrapper example index.js page has a code:
```
export const getStaticProps = wrapper.getStaticProps(async ({ store }) => {
store.dispatch(serverRenderClock(true))
store.dispatch(addCount())
})
```
the reducer.js
```
import { countActionTypes } from './act... | https://github.com/vercel/next.js/issues/17299 | https://github.com/vercel/next.js/pull/17335 | c45497e1c377ec010fc897406d72f92f5183467a | c388048f3efebff6cf6bdca4a41939e55975f91b | 2020-09-23T02:55:12Z | javascript | 2020-09-24T19:35:46Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 17,273 | ["packages/next/build/babel/preset.ts", "packages/next/build/swc/options.js", "test/unit/next-babel-loader-prod.test.ts"] | [9.5.4-canary.20] default loader doesn't transpile nullish coalescing and optional chaining | # Bug report
## Describe the bug
Loader `next-babel-loader` doesn't transpile nullish coalescing operator and optional chaining on canary
## To Reproduce
Repository: [next.js-bug-nullish-coalescing](https://github.com/rokinsky/next.js-bug-nullish-coalescing)
Steps to reproduce the behavior:
1. Go to [ht... | https://github.com/vercel/next.js/issues/17273 | https://github.com/vercel/next.js/pull/35976 | fe6e74dc57a811f83a4908bc2a138ce087b31be3 | 3ae571d97b429e9d7b57fb21d5e4dab4f39735e7 | 2020-09-21T23:50:24Z | javascript | 2022-04-16T02:48:43Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 17,242 | ["packages/next/build/webpack/config/blocks/css/loaders/global.ts", "packages/next/build/webpack/config/blocks/css/loaders/modules.ts", "packages/next/build/webpack/plugins/css-minimizer-plugin.ts", "packages/next/package.json", "packages/next/types/misc.d.ts", "yarn.lock"] | PostCSS 8 | # Bug report
## Describe the bug
Update PostCSS 7 → 8.
## Expected behavior
Without PostCSS 8, Next.js will not be able to load PostCSS 8 plugins (for instance, [Autoprefixer 10 doesn’t work in Nuxt.js](https://github.com/vercel/next.js/issues/17236)).
## Additional context
[PostCSS 8 changelog](https... | https://github.com/vercel/next.js/issues/17242 | https://github.com/vercel/next.js/pull/17415 | 80bf81a3cf8a99f569210670fe618f0b7cdc1d23 | b89d417b3714e98f6b8cef3baa0b6979cf1bb7d7 | 2020-09-20T14:36:51Z | javascript | 2020-10-21T10:31:07Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 17,220 | ["packages/next/build/webpack/loaders/next-serverless-loader.ts"] | "Optional catch all routes" is not working when deploying to Vercel | # Bug report
## Describe the bug
"Optional catch all routes" is not working when deploying to Vercel
## To Reproduce
- I have a page: `pages/the-loai/[[...slug]].tsx`
- When starts production server in local (http://localhost:3000/the-loai) => props: `"page":"/the-loai/[[...slug]]","query":{},"buildId":"vs... | https://github.com/vercel/next.js/issues/17220 | https://github.com/vercel/next.js/pull/17551 | 782b7e48ecfb0dddf5ea89b61881632d2aaa8c39 | b42be17593d69854b3f3cbed7b1ed14e999444dc | 2020-09-19T10:11:50Z | javascript | 2020-10-05T07:34:50Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 17,200 | ["docs/advanced-features/preview-mode.md", "docs/api-routes/dynamic-api-routes.md", "docs/api-routes/introduction.md", "docs/api-routes/response-helpers.md"] | [Feature](Docs) Give names to anonymous arrow functions in docs examples | For example, in [api-routes](https://nextjs.org/docs/api-routes/introduction)
we have this example
```js
export default (req, res) => {
res.statusCode = 200
res.setHeader('Content-Type', 'application/json')
res.end(JSON.stringify({ name: 'John Doe' }))
}
```
Exporting **anonymous** functions is arg... | https://github.com/vercel/next.js/issues/17200 | https://github.com/vercel/next.js/pull/17510 | 1659e4da617db3effc63f1dd919ce628eb59e135 | 7dec91175cb69f773fa623417e0e497acc606dc2 | 2020-09-18T13:05:19Z | javascript | 2020-10-05T21:16:47Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 17,113 | ["packages/next/build/webpack/loaders/next-serverless-loader.ts", "packages/next/next-server/server/next-server.ts", "packages/next/next-server/server/render.tsx", "test/integration/getserversideprops/pages/blog/[post]/index.js", "test/integration/getserversideprops/pages/something.js", "test/integration/getserversidep... | [9.5.4-canary.18] Different router.asPath between server and client. | # Bug report
From `9.5.4-canary.18` `router.asPath` in the sever-side return incorrect value.
## Describe the bug
```js
// next.config.js
module.exports = {
rewrites() {
return [
{
source: "/my-post",
destination: "/post"
}
];
}
};
```
## To Reproduce
https:/... | https://github.com/vercel/next.js/issues/17113 | https://github.com/vercel/next.js/pull/17121 | 6a4c256491f4643bf6baf456487dcde542244c25 | 2cf1d1c191923f7f1a8edbbc684da5cf9b3bdebf | 2020-09-15T14:40:09Z | javascript | 2020-09-15T19:19:07Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 17,096 | ["packages/next/server/base-server.ts", "test/e2e/dynamic-route-interpolation/index.test.ts"] | dynamic routes param value is not defined for server side render when literal dynamic route value is provided as the pathname | # Bug report
## Describe the bug
When using [dynamic routes](https://nextjs.org/docs/routing/dynamic-routes) the `param` value is not defined when navigating to a page whose pathname is the string literal value for the dynamic route.
From the dynamic routes example:
Given a page defined as `pages/post/[pid... | https://github.com/vercel/next.js/issues/17096 | https://github.com/vercel/next.js/pull/33808 | 39d3210776d37e7dc11e77b54a65b33b5454c0ce | 965d26eba373e760c5440054c76d77ea20d96fef | 2020-09-14T23:29:29Z | javascript | 2022-02-02T02:57:04Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 17,073 | ["packages/next/client/index.tsx", "packages/next/next-server/lib/router/router.ts", "test/integration/build-output/test/index.test.js"] | Experimental scrollRestoration + Sentry causes performance issues | # Bug report
## Describe the bug
Every scroll event is apparently watched by Sentry which registers it as `navigation` breadcrumb event.
## To Reproduce
1. enable `scrollRestoration` in `next.config.js`
2. initialize Sentry in the application and observe `__SENTRY__.hub._stack[0].scope._breadcrumbs` changi... | https://github.com/vercel/next.js/issues/17073 | https://github.com/vercel/next.js/pull/20633 | 380afbfba2a277ed19bc69a608cf5053c44cdcf7 | dbe1e626f877a9ef7bbffc2f360bae809874790d | 2020-09-14T07:55:10Z | javascript | 2020-12-31T16:08:12Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 17,066 | ["packages/next/package.json", "yarn.lock"] | Disable cssnano's postcss-calc | # Bug report
`next build` messes up complex css calc that works as expected in `next dev`
## To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:
1. Clone https://github.com/theMosaad/tailwindcss-capsize
2. On the dev server `npm run dev` the calc function works as ex... | https://github.com/vercel/next.js/issues/17066 | https://github.com/vercel/next.js/pull/18879 | db0587c4ac186d46709878500382127abee0281e | 6b8903f1b74e1f0e6704397afb08343d444d616c | 2020-09-13T18:02:15Z | javascript | 2020-11-06T05:46:19Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 16,988 | ["package.json", "packages/next/build/webpack-config.ts", "test/package-managers-tests/basic-pnpm/pages/about.js", "test/package-managers-tests/basic-pnpm/pages/about2.js", "test/package-managers-tests/basic-pnpm/pages/day/index.js", "test/package-managers-tests/basic-pnpm/pages/index.js", "test/package-managers-tests/... | 9.5.x build fails if `node_modules` folder is a symlink and imported packages use hooks | # Bug report
## Describe the bug
Next.js 9.5.x build and dev modes fail with "Invalid hook call" error if `node_modules` folder is a symlink to another folder and imported packages use hooks:
```
Error: Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen f... | https://github.com/vercel/next.js/issues/16988 | https://github.com/vercel/next.js/pull/17279 | fad07cc09a485f5e8a0d25df6269146397191476 | 5c4d0bded684c2bec3073c0c78fea9f7d95037fa | 2020-09-10T10:24:41Z | javascript | 2020-10-14T11:36:59Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 16,974 | ["packages/next/next-server/lib/router/router.ts", "packages/next/next-server/lib/router/utils/resolve-rewrites.ts", "test/integration/custom-routes/pages/auto-export/[slug].js", "test/integration/custom-routes/pages/nav.js", "test/integration/custom-routes/test/index.test.js"] | Supplying a rewrite to next/link should resolve correctly without href and as | When supplying only a `href` with a rewrite we should resolve the correct page automatically without triggering a full navigation, e.g.
```jsx
<Link href="/my-post/1?another=another">
<a>Post 1</a>
</Link>
```
with the page `post.js` and the rewrite
```js
// next.config.js
module.exports = {
rewrites... | https://github.com/vercel/next.js/issues/16974 | https://github.com/vercel/next.js/pull/16975 | 72b78f3be3ce7c1c6ecc99f1822c04ceed86d922 | dcdcf49a87f28f0b90991b7e44280803baa1e5f7 | 2020-09-09T21:03:20Z | javascript | 2020-09-10T00:55:22Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 16,950 | ["packages/next/pages/_document.tsx", "test/integration/production/components/dynamic-css/with-css.js", "test/integration/production/components/dynamic-css/with-css.module.css", "test/integration/production/pages/dynamic/pagechange1.js", "test/integration/production/pages/dynamic/pagechange2.js", "test/integration/prod... | CSS module removed when navigating pages that contain the same next/dynamic component | # Bug report
## Describe the bug
Components that use next/dynamic to load and that have a CSS module lose their CSS when navigating to another page that contains the same dynamically loaded component.
## To Reproduce
Here is a [repo](https://github.com/adamayres/next-dynamic-css-issue) that contains the min... | https://github.com/vercel/next.js/issues/16950 | https://github.com/vercel/next.js/pull/17173 | 56bd46486180e596aadfe48918151d1e62beed52 | b1503e13e8d767105a2e70038e94e695fb42e9fd | 2020-09-08T20:35:40Z | javascript | 2020-11-03T05:23:31Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 16,944 | ["errors/href-interpolation-failed.md", "packages/next/next-server/lib/router/router.ts", "test/integration/build-output/test/index.test.js", "test/integration/dynamic-routing/pages/index.js", "test/integration/dynamic-routing/test/index.test.js"] | When href interpolation fails we should error properly | Another thing I noticed: when I provide fewer params than necessary, the url resolves to the index page without warning, e.g. {pathname: „/[locale]/blog/[id]“, query: {id: 1}} (locale missing) becomes /?id=1. Maybe in this case a warning should be logged or an even error thrown?
_Originally posted by @herrstucki in ... | https://github.com/vercel/next.js/issues/16944 | https://github.com/vercel/next.js/pull/16946 | c12afa066e08a1aa0984f18dc4b7c2141367f6aa | 47d983f71f90a4c3fccd43479505b0270f7fb258 | 2020-09-08T16:36:29Z | javascript | 2020-09-10T20:05:02Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 16,938 | ["packages/next/server/hot-reloader.ts", "test/integration/gssp-ssr-change-reloading/pages/another/index.js", "test/integration/gssp-ssr-change-reloading/pages/index.js", "test/integration/gssp-ssr-change-reloading/test/index.test.js"] | GS(S)P data refreshing doesn't trigger properly for `/index` routes | We need to make sure to normalize the page path correctly when collecting the changed GS(S)P pages so that the data refreshing is triggered for normalized pages like `/index` and `/another/index` | https://github.com/vercel/next.js/issues/16938 | https://github.com/vercel/next.js/pull/16939 | ac0c892acc700ef36986f9e16492b8020c34f285 | f46ddc693302b2f32c5aadfb91d82d9975ee014a | 2020-09-08T15:25:19Z | javascript | 2020-09-08T16:00:05Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 16,932 | ["packages/next/client/page-loader.ts", "test/integration/css-client-nav/test/index.test.js", "test/integration/css-fixtures/composes-ordering/pages/index.js", "test/integration/css/test/index.test.js"] | Unused CSS preload | I've only just started getting this problem with a new nextjs app, where css files aren't preloaded, and therefore not used at all:
```
A preload for 'https://*******.vercel.app/_next/static/css/db098983a22a0aa338df.css' is found, but is not used because the request credentials mode does not match. Consider taking ... | https://github.com/vercel/next.js/issues/16932 | https://github.com/vercel/next.js/pull/18846 | ac54573b74d50469c826d438d72929cfc34ad369 | e9054744d84638555c10a33a76949c845d175fe0 | 2020-09-08T13:36:28Z | javascript | 2020-11-06T16:24:02Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 16,851 | ["packages/next/client/page-loader.ts", "packages/next/next-server/lib/router/router.ts", "test/integration/build-output/test/index.test.js", "test/integration/dynamic-routing/pages/[name]/index.js", "test/integration/dynamic-routing/pages/index.js", "test/integration/dynamic-routing/test/index.test.js"] | Interpolating dynamic href values doesn't preserve extra query params | # Bug report
This is a feedback to #16774 which I'm very excited about since it solves a big pain point in most apps I've been writing!
## Describe the bug
Adding extra query params to the `href` prop doesn't construct the expected URL; only the dynamic params are interpolated, while the extra query params are... | https://github.com/vercel/next.js/issues/16851 | https://github.com/vercel/next.js/pull/16878 | 2058c9f8de898aac032663c1620efe25d035bc1c | f942d9e89295b98cb48eee3e1fbf074c936a98f9 | 2020-09-04T12:32:23Z | javascript | 2020-09-07T11:09:02Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 16,828 | ["examples/with-rebass/package.json"] | Fix or remove the with-rebass example | # Bug report
## Describe the bug
The current `with-rebass` example is broken.
## To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:
1. Download the wit... | https://github.com/vercel/next.js/issues/16828 | https://github.com/vercel/next.js/pull/16839 | eaea7a8793723493d9284d69fe90e33e22c760c9 | 2e87e22731017551e5f2582b9c0475faf5cf9aed | 2020-09-03T18:05:59Z | javascript | 2020-09-21T02:16:15Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 16,825 | ["packages/next/next-server/lib/router/router.ts", "test/integration/custom-routes/pages/nav.js", "test/integration/custom-routes/pages/with-params.js", "test/integration/custom-routes/test/index.test.js", "test/integration/dynamic-routing/pages/another.js"] | [9.5.3 - Rewrites] Navigating route with dynamic routes no longer work properly | ## Describe the bug
```js
// next.config.js
module.exports = {
rewrites() {
return [
{
source: "/my-post/:id",
destination: "/post"
}
];
}
};
```
Navigating via `Link` or `router.push`
```js
<Link
href={{
pathname: "/post",
que... | https://github.com/vercel/next.js/issues/16825 | https://github.com/vercel/next.js/pull/16860 | 1c7cc60b8adc2119e0780afc53c367ff2eaaea73 | 6233ef7ed89b9d369580a2ac13b6119bc4b18a1c | 2020-09-03T14:38:34Z | javascript | 2020-09-04T19:19:17Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 16,792 | ["docs/basic-features/data-fetching.md"] | Docs on preview say `false` but code says `undefined` | # Bug report
## Describe the bug
Docs and code are out of sync. See
https://nextjs.org/docs/basic-features/data-fetching#getstaticprops-static-generation
and
https://github.com/Timer/next.js/blob/canary/packages/next/next-server/server/render.tsx#L611
## To Reproduce
```
export async function get... | https://github.com/vercel/next.js/issues/16792 | https://github.com/vercel/next.js/pull/16843 | f46ddc693302b2f32c5aadfb91d82d9975ee014a | b22769194262a700728be9b912cce2f63383bca0 | 2020-09-02T17:44:59Z | javascript | 2020-09-08T16:29:42Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 16,790 | ["packages/next/client/dev/dev-build-watcher.js", "packages/next/client/next-dev.js", "test/integration/gssp-ssr-change-reloading/pages/gsp-blog/[post].js", "test/integration/gssp-ssr-change-reloading/test/index.test.js"] | Show the build/activity indicator while re-fetching data for GS(S)P being edited | As a follow-up to https://github.com/vercel/next.js/pull/16744 we should also show the build/activity indicator while the data is being re-fetched so the user knows something is happening | https://github.com/vercel/next.js/issues/16790 | https://github.com/vercel/next.js/pull/16789 | 064917682f9b26c3a895dee6168a2167be83ba2a | 8426f13713c6a1ac498562479d864633cf355c6d | 2020-09-02T17:29:29Z | javascript | 2020-09-03T12:27:08Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 16,775 | ["packages/next/build/babel/plugins/next-page-config.ts", "test/integration/page-config/pages/valid/config-import.js", "test/integration/page-config/pages/valid/not-config-export.js", "test/integration/page-config/pages/valid/not-config-import-export.js"] | import config in _app raises https://err.sh/vercel/next.js/invalid-page-config | # Bug report
## Describe the bug
I use the package `@fortawesome/fontawesome-svg-core` and since nextjs **9.5.3** it causes an error, due to this code in `_app`:
```
import { config } from '@fortawesome/fontawesome-svg-core';
config.autoAddCss = false;
```
The error:
```
error - ./pages/_app.js
Erro... | https://github.com/vercel/next.js/issues/16775 | https://github.com/vercel/next.js/pull/16834 | 3c992063135f553b507dd49d28d2b19aebed3ac6 | d97237a292b3a0740ea1ee90e93be8e44c22673c | 2020-09-02T08:28:54Z | javascript | 2020-09-04T13:19:12Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 16,771 | ["packages/next/client/link.tsx", "packages/next/client/page-loader.ts", "packages/next/next-server/lib/router/router.ts", "test/integration/dynamic-routing/pages/index.js", "test/integration/dynamic-routing/test/index.test.js"] | We should handle interpolating dynamic href values correctly | When the dynamic route is provided with the query params we should support interpolating the values automatically.
Example:
```jsx
<Link href={{
pathname: '/blog/[slug]'
query: { slug: 'post-1' }
}}>
<a>To /blog/post-1</a>
</Link>
```
x-ref: https://github.com/vercel/next.js/pull/16634 | https://github.com/vercel/next.js/issues/16771 | https://github.com/vercel/next.js/pull/16774 | 22800319159d8594224e22766c33ca387761d05c | f8d92a67f04481cba7e8a3ac1ebc5a6b7dadc873 | 2020-09-02T07:21:39Z | javascript | 2020-09-02T16:23:26Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 16,752 | ["examples/with-react-intl/lang/en-GB.json", "examples/with-react-intl/lang/zh-Hans-CN.json", "examples/with-react-intl/lang/zh-Hant-HK.json", "examples/with-react-intl/package.json", "examples/with-react-intl/pages/_app.tsx", "examples/with-react-intl/pages/_document.tsx"] | [examples, react-intl] Application cannot be deployed using serverless target (Vercel, Netlify) | # Bug report
The current version of the `react-intl` example was simplified by @longlho in #16215 but it keeps the usage of a custom server
## Describe the bug
The custom server prevents usage of the serverless build target, which also prevents it from using it with Vercel.
I'm currently running a version o... | https://github.com/vercel/next.js/issues/16752 | https://github.com/vercel/next.js/pull/16806 | 4ba768e22c56141d5488f8ee1f1d78d703b0fbfd | 67b67b28b229fca0bd937d154270c6a6312e2bce | 2020-09-01T15:13:41Z | javascript | 2020-09-16T23:01:21Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 16,725 | ["examples/ssr-caching/package.json", "examples/ssr-caching/server.js"] | SSR caching example is broken (UnhandledPromiseRejectionWarning: TypeError: argument entity is required) | # Bug report
## Describe the bug
The SSR caching login is broken with the error below.
```
(node:14465) UnhandledPromiseRejectionWarning: TypeError: argument entity is required
at etag (/home/omar/Desktop/ssr-caching-app/node_modules/etag/index.js:72:11)
at /home/omar/Desktop/ssr-caching-app/node_module... | https://github.com/vercel/next.js/issues/16725 | https://github.com/vercel/next.js/pull/18786 | 1773b991bc300ea1943e2c94434bc2f16857181a | fb843a5577fb9382203702926391a9628582c706 | 2020-08-31T14:43:45Z | javascript | 2021-02-07T18:20:00Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 16,715 | ["packages/next-polyfill-module/src/index.js"] | Edge 18 (Object.fromEntries) not supported even with correct polyfills | # Bug report
using the following `.babel.rc` leads to a build that should in theory support edge 18.
```
{
"presets": [
[
"next/babel",
{
"preset-env": {
"targets": "> 0.25%"
}
}
]
],
"pl... | https://github.com/vercel/next.js/issues/16715 | https://github.com/vercel/next.js/pull/36426 | ab48f547864a1e325dd92bfb4790833917e1d71f | 4199da09b8211a6687ca1ea4acbde6a1d597c576 | 2020-08-31T09:36:58Z | javascript | 2022-08-08T05:04:19Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 16,690 | ["packages/next/client/index.tsx", "packages/next/next-server/lib/router/router.ts", "test/integration/build-output/test/index.test.js"] | Experimental scrollRestoration flag causes browser to make a favicon request on every scroll event | # Bug report
## Describe the bug
When the `experimental.scrollRestoration: true` feature is enabled, the resulting `replaceState` triggered by each scroll event will (potentially depending on caching, I assume) cause Chrome to re-request the favicon URL.
(I'm not sure why Chrome would re-request that just for ... | https://github.com/vercel/next.js/issues/16690 | https://github.com/vercel/next.js/pull/20633 | 380afbfba2a277ed19bc69a608cf5053c44cdcf7 | dbe1e626f877a9ef7bbffc2f360bae809874790d | 2020-08-29T22:36:17Z | javascript | 2020-12-31T16:08:12Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 16,689 | ["examples/with-react-intl/lang/en.json", "examples/with-react-intl/lang/fr.json", "examples/with-react-intl/package.json", "examples/with-react-intl/pages/_app.tsx", "examples/with-react-intl/pages/_document.tsx", "examples/with-react-intl/server.ts"] | [Example] Fix latest with-react-intl | # Bug report
## Describe the bug
The latest `with-react-intl` example https://github.com/vercel/next.js/pull/16215 has a few issues:
- The extracted message ids don't match the ones produced in the `.next` cache. The compiled langs are therefore not used and default to the ones defined in the components.
``... | https://github.com/vercel/next.js/issues/16689 | https://github.com/vercel/next.js/pull/16692 | f1c4cb8b3b9c1ae7ab3b6632130e00de1e25d78f | 6f60a2237785f2594d376990da4db88b346d2078 | 2020-08-29T22:12:07Z | javascript | 2020-09-01T01:33:24Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 16,661 | ["docs/advanced-features/preview-mode.md"] | Preview mode should include API Routes on docs | API Routes also have access to the preview data added by Preview Mode in `req.previewData`. Our docs should be updated to reflect that. | https://github.com/vercel/next.js/issues/16661 | https://github.com/vercel/next.js/pull/16705 | ce994365b74b89d97dff90707158bb63c99687de | f1c4cb8b3b9c1ae7ab3b6632130e00de1e25d78f | 2020-08-28T19:43:24Z | javascript | 2020-08-31T03:02:24Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 16,649 | ["examples/with-framer-motion/components/Gallery.js", "examples/with-framer-motion/components/SingleImage.js", "examples/with-framer-motion/constants.js", "examples/with-framer-motion/pages/image/[index].js"] | Missing images in with-framer-motion example | # Bug report
Images referenced in the `with-framer-motion` example link to an expired site on squarespace.
The example is broken.
## Describe the bug
The `SingleImage` component generates this kind of URLs :
```
https://static1.squarespace.com/static/5b475b2c50a54f54f9b4e1dc/t/5b5a3938562fa764113169a6/153... | https://github.com/vercel/next.js/issues/16649 | https://github.com/vercel/next.js/pull/16714 | 1c45f709528e77d758129bcff5d593161b848028 | 808d6b94eb8d806e60bc46623e61996e8e0348d9 | 2020-08-28T12:08:57Z | javascript | 2020-09-01T18:03:41Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 16,633 | ["docs/api-reference/next.config.js/basepath.md", "docs/api-reference/next/link.md", "docs/api-reference/next/router.md", "docs/routing/dynamic-routes.md", "docs/routing/introduction.md"] | Update docs for linking to dynamic routes | In our current `canary` release `Link` no longer requires to know the path of a page for client side transitions. We should update our docs to reflect that the usage of the `as` parameter is now optional. | https://github.com/vercel/next.js/issues/16633 | https://github.com/vercel/next.js/pull/16634 | 4c5c7cd2daf0f88a060b098c4f7906936bbeb883 | ea2df6c0c28cc753b81b25c2f57a13a624a30fee | 2020-08-27T20:44:40Z | javascript | 2020-09-07T16:35:30Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 16,624 | ["packages/next/client/page-loader.ts"] | [Next 9.5] Prefetch related Uncaught Exceptions on Firefox | # Bug report
## Describe the bug
Whenever a dynamic route is referenced in a page through the use of the `next/link` with prefetching enabled, **on a production build**, Firefox throws `Uncaught Exceptions` for each one of the `<link link="..." rel="prefetch" as="fetch" />` entries.
An example image can be fou... | https://github.com/vercel/next.js/issues/16624 | https://github.com/vercel/next.js/pull/16757 | 808d6b94eb8d806e60bc46623e61996e8e0348d9 | e34e5e09d91f6e33867ed0b0eec9648680ffa024 | 2020-08-27T11:56:40Z | javascript | 2020-09-01T18:09:25Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 16,610 | ["packages/next/client/index.tsx", "packages/next/client/page-loader.ts"] | Do not rely on browser `cssText` field | https://github.com/vercel/next.js/issues/16610 | https://github.com/vercel/next.js/pull/16611 | 42e8dcf281526b5dde27448010e96edcd5ceb196 | 328abb72ca83d47dd1ae0e7c4237de281e33e5d6 | 2020-08-26T19:38:10Z | javascript | 2020-08-27T02:13:28Z | |
closed | vercel/next.js | https://github.com/vercel/next.js | 16,566 | [".github/workflows/build_test_deploy.yml", "packages/next/build/webpack/plugins/font-stylesheet-gathering-plugin.ts"] | Webpack 5 Builds Break with optimizeFonts | # Bug report
## Describe the bug
Unclear if this warrants a bug report since it's an experimental feature, but if you use optimizeFonts with webpack 5, it breaks when deploying to Vercel.
## To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:
Repro: https://github.... | https://github.com/vercel/next.js/issues/16566 | https://github.com/vercel/next.js/pull/17450 | 1c4aecbeaf9de44cec3484f76d23ec8103f3bc50 | 71d798ce889932311f2ef575c4c80b09ad57bb6f | 2020-08-25T17:29:57Z | javascript | 2020-10-12T18:58:09Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 16,563 | ["docs/basic-features/built-in-css-support.md", "packages/next/build/webpack/config/blocks/css/index.ts", "test/integration/css-fixtures/import-global-from-module/node_modules/example/index.css", "test/integration/css-fixtures/import-global-from-module/node_modules/example/index.js", "test/integration/css-fixtures/impo... | Flag to let components load global styles | # Feature request
Ability to load 3rd party global styles either conditionally or directly from a component.
## Problem description
Forcing the use of .module.css or global.css in app is great when it comes to organizing and practicing healthy css structure, but it starts to be limiting when it comes to 3rd part... | https://github.com/vercel/next.js/issues/16563 | https://github.com/vercel/next.js/pull/16993 | 5aed1d2e353a1e49db49a69405ab6cd17328743a | 1ea674510665f950509e6a63ea080cf33fa8990d | 2020-08-25T15:54:32Z | javascript | 2020-09-10T17:45:30Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 16,551 | ["packages/next/types/index.d.ts"] | Feature request: Export a "GetStaticPathsResult" Typescript type | # Feature request
NextJS currently exports the `GetStaticPropsResult` and `GetStaticPropsContext` types which helps us to type our module boundaries like so:
```ts
import { GetStaticPropsContext, GetStaticPropsResult } from "next";
export async function getStaticProps(
context: GetStaticPropsContext
): P... | https://github.com/vercel/next.js/issues/16551 | https://github.com/vercel/next.js/pull/16580 | d59f12c41600d001e6ed6d1df98892fb4fb17995 | d20dbd6c2ecd0544ae737614db266b069028ed4f | 2020-08-25T09:50:07Z | javascript | 2020-09-01T17:20:17Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 16,550 | ["examples/with-typescript-graphql/lib/resolvers.ts", "examples/with-typescript-graphql/lib/type-defs.graphqls", "examples/with-typescript-graphql/lib/viewer.graphql", "examples/with-typescript-graphql/pages/index.tsx", "examples/with-typescript-graphql/test/__snapshots__/index.test.tsx.snap"] | add graphql-let mutation sample code i | # Feature request
add graphql-let mutation sample code in this example. https://github.com/vercel/next.js/blob/canary/examples/with-typescript-graphql/README.md#readme
## Is your feature request related to a problem? Please describe.
A clear and concise description of what you want and what your use case is.
... | https://github.com/vercel/next.js/issues/16550 | https://github.com/vercel/next.js/pull/16742 | 530b14616f64071b7207fb7aa0184673eae74fd6 | a2bea9b49293c33fd7f2f68baa103aa18c623ebe | 2020-08-25T09:47:45Z | javascript | 2020-11-10T21:10:54Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 16,542 | ["packages/next/build/webpack/loaders/next-serverless-loader.ts", "packages/next/next-server/server/next-server.ts", "packages/next/next-server/server/render.tsx", "test/integration/getserversideprops/test/index.test.js", "test/integration/revalidate-as-path/pages/_app.js", "test/integration/revalidate-as-path/pages/an... | deploying to Vercel causes conditional statements to evaluate incorrectly | # Bug report
## Describe the bug
When rendering a page using Incremental Static Regeneration a *conditional statement is erroneously applied to the wrong element.
*I'm referring to conditional rendering expressions of the following form:
```jsx
<div>
{true && <div />}
<div />
</div>
```
## To ... | https://github.com/vercel/next.js/issues/16542 | https://github.com/vercel/next.js/pull/17081 | 80000f42383af03e2f21cf1ba60b860ee78ffb08 | 94a5bd6109b84ef55c1a07b0be019ea32a559390 | 2020-08-25T03:35:31Z | javascript | 2020-09-14T16:48:04Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 16,495 | ["packages/next/build/babel/plugins/no-anonymous-default-export.ts"] | Link Fash Refresh warning to codemod | Update the Fast Refresh warning to include a link to the next-codemod: https://nextjs.org/docs/advanced-features/codemods#name-default-component
| https://github.com/vercel/next.js/issues/16495 | https://github.com/vercel/next.js/pull/16496 | a7550bf1d7b2a2c4075b4ba958a03e21612e93ad | 735aab6f03a9b70dd8c2cb70c8702bd86e6c9005 | 2020-08-23T16:59:02Z | javascript | 2020-08-24T03:04:25Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 16,482 | ["packages/next/build/webpack/loaders/next-serverless-loader.ts", "packages/next/next-server/server/render.tsx", "test/integration/fallback-route-params/pages/[slug].js", "test/integration/fallback-route-params/test/index.test.js"] | Fallback SSG pages have incorrect default dynamic route params in production | In production fallback SSG pages' dynamic route params should be undefined for initial render although they currently are provided as the params path part e.g. `{ id: '[id]' }`, this only occurs in serverless mode currently | https://github.com/vercel/next.js/issues/16482 | https://github.com/vercel/next.js/pull/16485 | 32ee65efa1a28f2c0a9b9199af58c2b8b4daed33 | 4e0b40145d289736a7c67bbf26d8c8e10fa6fe99 | 2020-08-23T00:47:21Z | javascript | 2020-08-23T12:35:30Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 16,481 | ["packages/next/build/webpack/loaders/next-serverless-loader.ts", "packages/next/next-server/server/render.tsx", "test/integration/fallback-route-params/pages/[slug].js", "test/integration/fallback-route-params/test/index.test.js"] | Fallback SSG pages don't have undefined dynamic route params in dev mode | During development we aren't matching production behavior currently and dynamic route params are available during the initial render when they won't be in production for fallback SSG pages | https://github.com/vercel/next.js/issues/16481 | https://github.com/vercel/next.js/pull/16485 | 32ee65efa1a28f2c0a9b9199af58c2b8b4daed33 | 4e0b40145d289736a7c67bbf26d8c8e10fa6fe99 | 2020-08-23T00:45:34Z | javascript | 2020-08-23T12:35:30Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 16,478 | ["docs/advanced-features/module-path-aliases.md"] | Update documentation on module path aliases | The [module path alias documentation](https://nextjs.org/docs/advanced-features/module-path-aliases) is incomplete. It will cause a "Module not found" error at build time. You also have to update the webpack configuration, i.e. https://github.com/vercel/next.js/issues/10929
This webpack configuration update should b... | https://github.com/vercel/next.js/issues/16478 | https://github.com/vercel/next.js/pull/16479 | 85d58298a3e324eabe8f27a2b243928d1edbe652 | 4d0d09ba9da07fcfe4825ca4e3118dabfae9c45f | 2020-08-22T19:18:42Z | javascript | 2020-08-22T21:28:47Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 16,454 | ["packages/next/next-server/lib/router/router.ts", "packages/next/next-server/lib/router/utils/resolve-rewrites.ts", "test/integration/rewrites-client-resolving/next.config.js", "test/integration/rewrites-client-resolving/pages/404.js", "test/integration/rewrites-client-resolving/pages/category/[...slug].js", "test/int... | Rewrites resolving on the client should break after matching dynamic route | When using the rewrite `{ source: '/:path*', destination: '/path*' }` the rewrites chain should be broken on the client same as on the server when a dynamic route or page file is matched after.
| https://github.com/vercel/next.js/issues/16454 | https://github.com/vercel/next.js/pull/16455 | 42e1d5b5dc9c33b07319bdc1952fdddcf7c15aca | 8a1c9937b67c4ba6611d44fb6309215a8235f5ca | 2020-08-21T19:20:59Z | javascript | 2020-08-22T05:15:45Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 16,445 | ["packages/next/client/index.tsx", "packages/next/next-server/lib/router/router.ts", "test/integration/route-load-cancel-css/next.config.js", "test/integration/route-load-cancel-css/pages/index.js", "test/integration/route-load-cancel-css/pages/page1.js", "test/integration/route-load-cancel-css/pages/page1.module.css",... | [experimental react] Next throws on cancelled renders | PR fixing https://github.com/vercel/next.js/pull/16424 | https://github.com/vercel/next.js/issues/16445 | https://github.com/vercel/next.js/pull/16462 | 8a1c9937b67c4ba6611d44fb6309215a8235f5ca | 9acd001e092b7d3e96de92e39c006f43e6083352 | 2020-08-21T13:58:05Z | javascript | 2020-08-22T11:47:21Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 16,444 | ["docs/api-reference/next.config.js/cdn-support-with-asset-prefix.md"] | getServerSideProps disables staticPrefix | # Bug report
## Describe the bug
When using getServerSideProps, the staticPrefix seems to be disabled for that page.
## To Reproduce
Enable staticPrefix in next.config.js
```js
export async function getServerSideProps(context) {
return {
props: { translations: [] },
}
}
```
## Expected b... | https://github.com/vercel/next.js/issues/16444 | https://github.com/vercel/next.js/pull/16998 | fa9523c0632b7bdfb06e98a87c9d3638abe78cfd | 6ecb740415bff7e45a62bfd39908ec38d610f7ca | 2020-08-21T13:52:13Z | javascript | 2020-09-10T17:46:37Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 16,442 | ["docs/advanced-features/debugging.md"] | Incorrect / missing documentation for debugging client-side javascript in VS Code | # Bug report
## Describe the bug
As best as I can tell, the documentation at https://nextjs.org/docs/advanced-features/debugging only describes how to configure debugging for the `node` process in vscode. It doesn't provide any specific instructions on how to debug code that is run in browser, in chrome at the cl... | https://github.com/vercel/next.js/issues/16442 | https://github.com/vercel/next.js/pull/28815 | c491adfe12dfad89581be3cd751d30ddb3855477 | c7e187f893bb399f5f8d51f35afea6e7ec869162 | 2020-08-21T13:42:24Z | javascript | 2021-09-16T07:07:56Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 16,440 | ["packages/next/build/webpack/loaders/next-serverless-loader.ts", "packages/next/next-server/lib/router/utils/path-match.ts", "packages/next/next-server/lib/router/utils/resolve-rewrites.ts", "packages/next/next-server/server/next-server.ts", "packages/next/next-server/server/router.ts", "test/integration/production-na... | Spread operator not working in Safari 11.0.3 | # Bug report
## Describe the bug
A user has reported this issue for our site, which is running on nextjs 9.4.0. This also happens on vercel.com/login. Certain elements on the site fails to load on with console error `SyntaxError: Unexpected token '...'. Expected a property name.`.
For our site, our mapbox bas... | https://github.com/vercel/next.js/issues/16440 | https://github.com/vercel/next.js/pull/16453 | 7c7ecaa6369690987876f3fc61479b8331f5bbb5 | 78ef13914a732b2a74255e685ecca2b022418e45 | 2020-08-21T13:13:22Z | javascript | 2020-08-21T19:11:25Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 16,426 | ["packages/eslint-plugin-next/lib/rules/no-html-link-for-pages.js"] | no-html-link-for-pages eslint rule should work with src/pages folder | # Bug report
## Describe the bug
currently, the `no-html-link-for-pages` eslint-rule by default only looks in the `pages` folder for pages. it should also look [in `src/pages`](https://nextjs.org/docs/advanced-features/src-directory).
## To Reproduce
1. yarn create next-app .
2. yarn add -D eslint @next/es... | https://github.com/vercel/next.js/issues/16426 | https://github.com/vercel/next.js/pull/16743 | 67b67b28b229fca0bd937d154270c6a6312e2bce | fa0351639a184264375e7ecbe44db3a15c0917ca | 2020-08-21T07:58:26Z | javascript | 2020-09-18T00:09:25Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 16,407 | ["docs/basic-features/data-fetching.md", "packages/next/build/webpack/loaders/next-serverless-loader.ts", "packages/next/next-server/server/next-server.ts", "packages/next/next-server/server/render.tsx", "packages/next/types/index.d.ts", "test/integration/getserversideprops/next.config.js", "test/integration/getservers... | Add "asPath" (or similar) in getServerSideProps | # Feature request
Add in `getServerSideProps`'s function a parameter similar to `asPath` from `getInitialProps`, which would contain the URL path the user will see in it's browser.
Use cases include path logging and dynamic path analysis.
## Describe the solution you'd like
For a file `./pages/items-search/... | https://github.com/vercel/next.js/issues/16407 | https://github.com/vercel/next.js/pull/17082 | 71a01815728303c5dd4dd1a840568a9f251909ce | d3f4a4cb2afc9e18a82609d907d50a311578470f | 2020-08-20T18:07:33Z | javascript | 2020-09-14T21:01:04Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 16,335 | ["packages/next/client/index.tsx", "test/integration/production/pages/css-and-back.js", "test/integration/production/pages/css-modules.js", "test/integration/production/test/index.test.js"] | Fix IE11 compatibility on `next@canary` | Currently, `next@canary` errors in IE11 with the following error:
(remove, ignore append)
 | https://github.com/vercel/next.js/issues/16335 | https://github.com/vercel/next.js/pull/16336 | 25fa1653bd27fff79acd61d5cb28659e878f0111 | 9746043354c57f4d40ab0b8b58282268a3bf9caf | 2020-08-19T05:00:16Z | javascript | 2020-08-19T06:34:44Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 16,333 | ["packages/next/client/page-loader.ts", "test/integration/client-404/pages/missing.js", "test/integration/client-404/pages/to-missing-link.js", "test/integration/client-404/test/client-navigation.js", "test/integration/client-404/test/index.test.js"] | Next.js router can sometimes hang for existing users on app after a new deployment | The Next.js router can sometimes hang (an edge case) when a user is on the app and a new deployment is made. This causes routing assets to go missing, and under certain conditions, prevents Next.js from automatically reloading to the new version. | https://github.com/vercel/next.js/issues/16333 | https://github.com/vercel/next.js/pull/16334 | 8ef253fd021c516279fbbd59cc84423a6d55f2b3 | 0a72d14deb2249d6f03e6d2eb370ff8394db4189 | 2020-08-19T02:59:11Z | javascript | 2020-08-19T11:41:01Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 16,283 | ["packages/next/client/index.tsx"] | [internal] [canary only] Fix IE 11 compat | The latest canary is failing on IE 11. | https://github.com/vercel/next.js/issues/16283 | https://github.com/vercel/next.js/pull/16282 | d824189bcd40913d2961764dc62d0e273d600e83 | 9aadd1aa36eef8d09232eda3e8b4da5625a265b0 | 2020-08-18T03:55:14Z | javascript | 2020-08-18T03:56:14Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 16,269 | ["packages/next/build/webpack/loaders/next-serverless-loader.ts", "test/integration/prerender-fallback-aspath/next.config.js", "test/integration/prerender-fallback-aspath/pages/blog/[post]/[comment].js", "test/integration/prerender-fallback-aspath/pages/blog/[post]/index.js", "test/integration/prerender-fallback-aspath... | Fallback SSG pages have inconsistent asPath values | I use router.asPath in _app in order to set alternate link tags. i.e.: for the page /pages/article/[id].js SSR returns /article/123, but in case of SSG it return /article/[id]. I see this behavior on the Vercel platform, not locally.
I use Next.js 9.5.2.
_Originally posted by @hk86 in #16256_
<hr />
We need... | https://github.com/vercel/next.js/issues/16269 | https://github.com/vercel/next.js/pull/16352 | 1388aa41d5309525eecdf6c70aa52c6346a965cc | 67482914c686e2a660eaea157475ad5e80bae1a8 | 2020-08-17T19:01:11Z | javascript | 2020-08-19T15:23:02Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 16,260 | ["packages/next/client/page-loader.ts", "packages/next/next-server/lib/router/router.ts"] | Legacy TypeScript version support | The latest `canary` Next.js is publishing types not compatible with old TS versions:
```
yarn run v1.22.4
$ cross-env NODE_ENV=production next build
info - Loaded env from /Users/z/projects/front/.env.production
Failed to compile.
./node_modules/next/dist/next-server/lib/router/router.d.ts:5:13
Type error: '=... | https://github.com/vercel/next.js/issues/16260 | https://github.com/vercel/next.js/pull/16288 | 0fbc9d23ef3f9c6f9bc70617ae511797b880a166 | 8916e401a2dc482ef56ff112b8d164f6e5bd9ff5 | 2020-08-17T14:02:48Z | javascript | 2020-08-18T14:06:10Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 16,259 | ["package.json", "packages/next/build/webpack-config.ts", "test/integration/build-output/fixtures/with-crypto/pages/index.js", "test/integration/build-output/test/index.test.js", "yarn.lock"] | After upgrading to to 9.5.2, client bundle includes unnecessary browser-node-polyfills | # Bug report
## Describe the bug
After upgrading to next@9.5.2, client bundle includes `browser polyfils for Node.js`, probably related to #16022.
As far as I can tell, no code relies on these modules, because doing
```js
delete config.resolve.alias.crypto;
delete config.resolve.alias.... | https://github.com/vercel/next.js/issues/16259 | https://github.com/vercel/next.js/pull/16452 | 450742274a5b37131f77f89f9d3c46ad8ced34b6 | 7c7ecaa6369690987876f3fc61479b8331f5bbb5 | 2020-08-17T13:03:38Z | javascript | 2020-08-21T18:50:24Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 16,197 | ["examples/with-sentry/next.config.js"] | BasePath causes withSourceMaps to fail in with-sentry example | # Bug report
## Describe the bug
Using a `basePath` different from null on the webpack config makes the sourcemaps plugin fail
## To Reproduce
Steps to reproduce the behavior:
1. git clone git@github.com:Agupane/next.js-1.git
2. Install the dependencies
3. Setup the env variables for a sentry project: ... | https://github.com/vercel/next.js/issues/16197 | https://github.com/vercel/next.js/pull/16376 | f2ba97d866863b46b3dcb68c9652a78d9fa0c4a9 | c97e53efe1a9741bb8762659aaac339961318b73 | 2020-08-14T19:02:28Z | javascript | 2020-08-24T02:00:43Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 16,182 | ["packages/next/next-server/lib/utils.ts", "packages/next/next-server/server/render.tsx", "packages/next/pages/_document.tsx"] | [internal] Refactor /_document to rely on BuildManifest | Currently, `/_document` relies on information from the `BuildManifest` being passed to it instead of directly reading the `BuildManifest` itself. | https://github.com/vercel/next.js/issues/16182 | https://github.com/vercel/next.js/pull/16184 | db40a39f5ec260d29b245d2f5ea54441e9b2cdc4 | 9fcf39acd45966d8a6c362bec62e49a53dcd8581 | 2020-08-14T03:37:35Z | javascript | 2020-08-14T14:20:03Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 16,173 | ["packages/next/bin/next.ts", "test/integration/cli/test/index.test.js", "test/lib/next-test-utils.js"] | Handle SIGTERM to allow graceful process exit | # Bug report
## Describe the bug
Server process won't handle SIGTERM / SIGINT anymore, exiting with code 1.
The change was introduce by https://github.com/vercel/next.js/pull/6450
With the new addition of custom Headers in `getStaticProps` pages, I was looking to get rid of my custom server and stumbled with ... | https://github.com/vercel/next.js/issues/16173 | https://github.com/vercel/next.js/pull/19433 | f4bf8a4696af6f9a0b64636205356ba207fb1ea9 | 397a375b37ca7727f13d73b36fcc80df61cfc66a | 2020-08-13T21:14:50Z | javascript | 2020-11-25T13:30:06Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 16,166 | ["packages/next/client/index.tsx", "packages/next/next-server/lib/router/router.ts"] | [internal] Convert `next/client` to TypeScript | https://github.com/vercel/next.js/issues/16166 | https://github.com/vercel/next.js/pull/16167 | 09afc376cd67357949d1e1d2ae52aeb82e654a1b | 0e48ea3938a6d57bc85c2d903f8401d147bfc4f6 | 2020-08-13T16:28:16Z | javascript | 2020-08-13T17:39:33Z | |
closed | vercel/next.js | https://github.com/vercel/next.js | 16,147 | ["packages/next/next-server/lib/router/utils/querystring.ts", "test/integration/build-output/test/index.test.js", "test/integration/client-navigation/pages/nav/query-params.js", "test/integration/client-navigation/pages/query.js", "test/integration/client-navigation/test/index.test.js", "test/integration/size-limit/tes... | [9.5.2] The query string doesn't cleanup undefined value | # Bug report
## Describe the bug
Navigating router via `push`:
```js
router.push({
pathname: "/page-a",
query: {
param1: "ok",
param2: undefined
}
})
```
```js
// /pages/page-2
const router = useRouter();
console.log(router.query);
```
Result
```js
{
param1: "ok",
param2: "und... | https://github.com/vercel/next.js/issues/16147 | https://github.com/vercel/next.js/pull/16608 | ca986abd95b39b876236815490bcb2d591ddff5d | 5aed1d2e353a1e49db49a69405ab6cd17328743a | 2020-08-13T04:02:04Z | javascript | 2020-09-10T15:12:37Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 16,143 | ["packages/next/client/head-manager.ts"] | [internal] Strongly type Head Manager | https://github.com/vercel/next.js/issues/16143 | https://github.com/vercel/next.js/pull/16144 | 9e65c6a958baad321f118c52907c117511cb239e | 16e4f9e79ef804221b7a761ced2971842fff98a5 | 2020-08-13T03:32:07Z | javascript | 2020-08-13T03:54:48Z | |
closed | vercel/next.js | https://github.com/vercel/next.js | 16,131 | ["packages/next/build/index.ts", "packages/next/build/webpack/plugins/build-manifest-plugin.ts", "packages/next/client/page-loader.ts"] | [internal] Strongly type page loader | This will let us make changes to the page loader with more confidence. | https://github.com/vercel/next.js/issues/16131 | https://github.com/vercel/next.js/pull/16132 | e72ac7642235d37891deba08fdad31e9963f164c | 9e65c6a958baad321f118c52907c117511cb239e | 2020-08-12T20:04:11Z | javascript | 2020-08-12T20:42:05Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 16,107 | ["packages/next/client/link.tsx", "packages/next/package.json", "test/acceptance/ReactRefreshLogBox.test.js", "yarn.lock"] | Link without href throws error | # Bug report
Server Error
TypeError: Cannot destructure property 'auth' of 'urlObj' as it is undefined.
## Describe the bug
Link without passed href results in this bug
## To Reproduce
Use Link without href.
## Expected behavior
Even though that typescript indicates the error, maybe a more helpf... | https://github.com/vercel/next.js/issues/16107 | https://github.com/vercel/next.js/pull/15953 | b0d2a80a18645b5b7278c8e72829e76063b91945 | ff33e07afe875a29a32b4942564cbb379fa7935e | 2020-08-12T09:19:54Z | javascript | 2020-08-18T16:36:40Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 16,088 | ["docs/api-reference/next.config.js/headers.md"] | Docs should mention headers overriding behavior | We should add a note to the headers documentation mentioning that if a header is already set successive ones with the same key will override the value | https://github.com/vercel/next.js/issues/16088 | https://github.com/vercel/next.js/pull/16089 | 2301331703c118927b8d09811802d9d081a392a0 | ceeb6c3fce983cf96c6a9d8844a5cded2eedd9a3 | 2020-08-11T18:14:01Z | javascript | 2020-08-12T04:27:31Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 16,074 | ["docs/basic-features/data-fetching.md"] | Documentation needs to mention writing server-side code in GS(S)P props earlier | Lots of users miss that they can write server side code in `getStaticProps` and `getServerSideProps`.
We also see numerous issues about people trying to fetch API routes. We need to fix this in the documentation by making this one of the **first things** we have in the docs. | https://github.com/vercel/next.js/issues/16074 | https://github.com/vercel/next.js/pull/16198 | bb8374126f03e1cb27438b48deda44f1edc28655 | 512782ee2916bd03725af249f7718a0f643bc095 | 2020-08-11T13:11:13Z | javascript | 2020-08-18T05:14:26Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 16,073 | ["docs/advanced-features/codemods.md", "docs/manifest.json", "packages/next-codemod/README.md"] | Add `@next/codemod` documentation | https://github.com/vercel/next.js/issues/16073 | https://github.com/vercel/next.js/pull/16067 | b8662d57665ac4e410aab6cd97a0f43c7de91d83 | 16345f631e380afa836c12e4918ad4ea68fb4e7d | 2020-08-11T12:57:52Z | javascript | 2020-08-11T13:12:00Z | |
closed | vercel/next.js | https://github.com/vercel/next.js | 16,066 | ["docs/api-reference/create-next-app.md", "docs/getting-started.md", "docs/manifest.json"] | link is not working `you can review the create-next-app documentation` | # Bug report
## Describe the bug
On https://nextjs.org/docs page 'create-next-app documentation' on click link is not working
A clear and concise description of what the bug is.
## To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:
1. Go to the setup section
2... | https://github.com/vercel/next.js/issues/16066 | https://github.com/vercel/next.js/pull/16069 | 9e70b3de4405d91c7489e5af29a7f34708a86999 | b8662d57665ac4e410aab6cd97a0f43c7de91d83 | 2020-08-11T08:14:12Z | javascript | 2020-08-11T10:08:43Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 16,028 | ["packages/next/next-server/lib/router/router.ts", "test/integration/client-shallow-routing/pages/[slug].js", "test/integration/client-shallow-routing/test/index.test.js"] | Navigating Between Dynamic Routes with Browser Back Button Breaks After Shallow Routing | # Bug report
## Describe the bug
I have a `/movie/[movieId]` page. It has `getServerSideProps` function for SEO purposes and fetches base movie info at server-side. In this page, there is an image list and when you click an image it opens a modal by adding a query string like `?view=/xXBnM6uSTk6qqCf0SRZKXcga9Ba.j... | https://github.com/vercel/next.js/issues/16028 | https://github.com/vercel/next.js/pull/16477 | 120b41ec8a304ebec7c34648bc0fd4ecc8e9a778 | 32ee65efa1a28f2c0a9b9199af58c2b8b4daed33 | 2020-08-09T23:05:12Z | javascript | 2020-08-22T21:51:14Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 16,020 | ["test/integration/preview-fallback/pages/api/disable.js", "test/integration/preview-fallback/pages/api/enable.js", "test/integration/preview-fallback/pages/fallback/[post].js", "test/integration/preview-fallback/pages/index.js", "test/integration/preview-fallback/pages/no-fallback/[post].js", "test/integration/preview... | Preview mode pages can be accessed publicly | ## Description
I have a post in draft, path for which is `/posts/id`. I want for rebuild it on request since data is new.
So I made it a preview url using preview mode feature. Now the url is `/api/preview?secret=token&slug=/posts/id`.
Now when I make this request this page is generated and stored on disk and any on... | https://github.com/vercel/next.js/issues/16020 | https://github.com/vercel/next.js/pull/16579 | 5fbe50c49ace43edc95f5ca91483bbe6a9e9501a | 990c1792d2af53e1c178ca675a3b40e11c6b159d | 2020-08-09T14:13:54Z | javascript | 2020-08-26T11:07:32Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 15,979 | ["packages/next/package.json", "yarn.lock"] | Styles not getting passed to Amp Toolbox after Next update to 9.5 | # Bug report
Looks like styles may not be passed to apmtoolbox after updating to 9.5
## Describe the bug
Error thrown
TypeError: Cannot read property 'data' of undefined
This error happened while generating the page. Any console logs will be displayed in the terminal window.
Call Stack
ApplyCommonAttributes... | https://github.com/vercel/next.js/issues/15979 | https://github.com/vercel/next.js/pull/16043 | e08b633c3acf4f7f7f16d1eef1cbfa02753c1c7c | d6ad0d084308c6c11aadf87164f7b9f04fc8b017 | 2020-08-07T17:46:00Z | javascript | 2020-08-10T16:06:00Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 15,948 | ["packages/next/build/webpack-config.ts", "packages/next/package.json", "test/integration/basic/pages/node-browser-polyfills.js", "test/integration/basic/test/index.test.js", "test/integration/production/pages/node-browser-polyfills.js", "test/integration/production/test/index.test.js", "yarn.lock"] | Polyfill common Node.js packages for webpack 5 | Webpack 5 stopped polyfilling Node.js packages, however, their usage is prolific throughout the npm ecosystem.
We should provide default polyfills for the most common usages:
- [x] Add `process` and `buffer`: https://github.com/vercel/next.js/pull/15499
- [x] [`path`](https://github.com/vercel/next.js/issues/133... | https://github.com/vercel/next.js/issues/15948 | https://github.com/vercel/next.js/pull/16022 | 394e24073d0439f4e277ab2a194cd6cbaf3052e7 | 843d58425b65fc00cfc1b416128fdd3343a3b083 | 2020-08-06T17:33:53Z | javascript | 2020-08-10T01:26:21Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 15,947 | ["packages/next/build/webpack/plugins/mini-css-extract-plugin/src/index.js", "packages/next/build/webpack/plugins/mini-css-extract-plugin/src/loader.js", "packages/react-dev-overlay/src/middleware.ts"] | Fix webpack 5 deprecation warnings | Next.js fully supports webpack 5, however, some of our plugins are using deprecated APIs.
Before we can consider webpack 5 stable, we should completely eliminate deprecated webpack 5 API usage.
Known warnings:
- [x] https://github.com/webpack-contrib/terser-webpack-plugin/pull/283
- [x] https://github.com/web... | https://github.com/vercel/next.js/issues/15947 | https://github.com/vercel/next.js/pull/16390 | 3e81809df44e5c36a52abc89b46bc53f18b83695 | 08ab3ac6c14db1d4c7dfd204e96e4f9cf7e83128 | 2020-08-06T17:32:22Z | javascript | 2020-08-20T13:56:52Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 15,940 | ["packages/next/build/webpack/loaders/next-serverless-loader.ts", "test/integration/dynamic-optional-routing/pages/about.js", "test/integration/dynamic-optional-routing/server.js", "test/integration/dynamic-optional-routing/test/index.test.js"] | Serverless wrapper error | Trying this out, I got the following error on a non-dynamic route page:
```
defaultRouteRegex is not defined
```
_Originally posted by @kevva in https://github.com/vercel/next.js/pull/15914#issuecomme... | https://github.com/vercel/next.js/issues/15940 | https://github.com/vercel/next.js/pull/15960 | db69e4747a1feb96b09c393385555b391a6006c7 | b1ef76df3133988bb86eb8b3ee174eb4ef937d6c | 2020-08-06T14:31:07Z | javascript | 2020-08-07T07:01:34Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 15,928 | ["packages/next/cli/next-dev.ts", "test/integration/cli/test/index.test.js"] | Development server reports boot too early | # Bug report
## Describe the bug
```
❯ yarn next dev examples/z-experimental-refresh/
yarn run v1.22.4
$ node --trace-deprecation packages/next/dist/bin/next dev examples/z-experimental-refresh/
ready - started server on http://localhost:3000
Port 3000 is already in use.
Use `npm run dev -- -p <some other p... | https://github.com/vercel/next.js/issues/15928 | https://github.com/vercel/next.js/pull/15929 | 817d558a6d6aafd2bbd5c37ddabd79c1d9cf2b91 | 2d42b8e0765050bc61cb2f6efadd1f5825a41f6c | 2020-08-06T03:48:46Z | javascript | 2020-08-06T06:47:01Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 15,913 | ["package.json", "packages/next/types/index.d.ts", "pnpm-lock.yaml", "test/unit/infer-get-server-side-props-type.test.ts", "test/unit/infer-get-static-props.test.ts"] | Infer Types leading to `props: never` | ## Describe the bug
```ts
export const getServerSideProps = async ({ params }) => {
return {
props: { foo: "bar" }
}
};
export const Page = (props: InferGetServerSidePropsType<typeof getServerSideProps>) => { ... }
```
causes `props: never`
however the following works fine:
```ts
export const ... | https://github.com/vercel/next.js/issues/15913 | https://github.com/vercel/next.js/pull/40635 | c2f48ea86d448c8be1982b46f184b1d2f2d6cd50 | 3943b20f554ba6558fa2f8262a302c14c42c134e | 2020-08-05T18:28:12Z | javascript | 2022-09-20T22:25:01Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 15,906 | ["docs/api-reference/next.config.js/runtime-configuration.md"] | Runtime configuration docs incorrectly state that serverless build are not supported | # Bug report
According to https://nextjs.org/docs/api-reference/next.config.js/runtime-configuration, `Runtime configuration is not available when using the serverless target.`.
This is incorrect, it has been supported since `9.2.2` see: https://github.com/vercel/next.js/pull/10365
# Describe the bug
N/A
##... | https://github.com/vercel/next.js/issues/15906 | https://github.com/vercel/next.js/pull/15907 | 026785d5adc2e721d3a77254ed657c1bfb178b4e | abf6e74e8d79c096f2c035d4187fbae86c1b4ac0 | 2020-08-05T15:50:36Z | javascript | 2020-08-05T16:11:01Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 15,904 | ["errors/export-all-in-page.md", "packages/next/build/babel/plugins/next-page-disallow-re-export-all-exports.ts", "packages/next/build/webpack/loaders/next-babel-loader.js", "test/integration/re-export-all-exports-from-page-disallowed/component/child.js", "test/integration/re-export-all-exports-from-page-disallowed/com... | getServerSideProps not called when exported for multiple pages. | # Bug report
## Describe the bug
When a common react component is exported from multiple pages, `getServerSideProps` is not called except when revisiting the page that the component was initially visited.
## To Reproduce
Repository Structure
```
pages
- index.ts
- home.ts
views
Home.tsx
```
... | https://github.com/vercel/next.js/issues/15904 | https://github.com/vercel/next.js/pull/14325 | 3c04111c9c48065890fcf08cdc4890093ef9d996 | 0fd1958ae465e6b22c77ad786601a8ba05ea36a1 | 2020-08-05T14:40:08Z | javascript | 2020-08-05T20:21:40Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 15,879 | ["packages/next/build/webpack/loaders/next-serverless-loader.ts", "test/integration/dynamic-optional-routing/pages/[[...optionalName]].js", "test/integration/dynamic-optional-routing/pages/nested/[[...optionalName]].js", "test/integration/dynamic-optional-routing/test/index.test.js"] | Vercel deployments include query string in `asPath` | 
Reproduction:
https://github.com/MJHLS/slug-test
https://slug-test.vercel.app/yeet | https://github.com/vercel/next.js/issues/15879 | https://github.com/vercel/next.js/pull/15914 | 405e42e41ef5df28ef69c035c9ae611139d8ec21 | 7d7a8fc3000bb830a24225bc362a73a65bda3936 | 2020-08-04T19:36:19Z | javascript | 2020-08-05T19:29:38Z |
closed | vercel/next.js | https://github.com/vercel/next.js | 15,877 | ["examples/with-cxs/pages/_document.js", "examples/with-glamor/pages/_document.js", "examples/with-goober/pages/_document.js", "examples/with-react-native-web/pages/_document.js", "examples/with-tailwindcss-emotion/pages/_document.js", "examples/with-typestyle/pages/_document.js"] | Update examples for TypeScript compat & renderPage() call | Examples currently don't always await `renderPage()` even though we say it can return a Promise. | https://github.com/vercel/next.js/issues/15877 | https://github.com/vercel/next.js/pull/15528 | 1968f7f552989e05c636fc834b365e46c99afcfe | fcc4d8cd50eb2170fda9fbac6f9853799ceb9959 | 2020-08-04T17:27:22Z | javascript | 2020-08-04T18:46:40Z |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.