rsnext/errors/invalid-resolve-alias.mdx
Delba de Oliveira 44d1a1cb15
docs: Migrate error messages to MDX and App Router. (#52038)
This PR is part of a larger effort to migrate error messages to MDX and
use App Router: https://github.com/vercel/front/pull/23459
2023-07-05 06:11:16 -07:00

24 lines
659 B
Text

---
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)