Download next.js/errors/config-resolve-alias.mdx from Devendra174/react-code-dataset: direct link, hf CLI and curl.
- Browser
- Download file 655 Bytes
-
https://huggingface.co/datasets/Devendra174/react-code-dataset/resolve/main/next.js/errors/config-resolve-alias.mdx
- Command line
-
hf download hf://datasets/Devendra174/react-code-dataset/next.js/errors/config-resolve-alias.mdx
-
curl -L -o config-resolve-alias.mdx https://huggingface.co/datasets/Devendra174/react-code-dataset/resolve/main/next.js/errors/config-resolve-alias.mdx
655 Bytes
| title: Invalid webpack resolve alias | |
| ## Why This Error Occurred | |
| When overriding `config.resolve.alias` incorrectly in `next.config.js` webpack will throw an error because private-next-pages is not defined. | |
| ## Possible Ways to Fix It | |
| This is not a bug in Next.js, it's related to the user adding a custom webpack(config) config to next.config.js and overriding internals by not applying Next.js' aliases. Solution would be: | |
| ```js filename="next.config.js" | |
| webpack(config) { | |
| config.resolve.alias = { | |
| ...config.resolve.alias, | |
| // your aliases | |
| } | |
| } | |
| ``` | |
| ## Useful Links | |
| - [Related issue](https://github.com/vercel/next.js/issues/6681) | |