Failed to load config "next/babel" to extend from.
Answered
American Crocodile posted this in #help-forum
American CrocodileOP
I used the default ESLint setup when creating my Next app, and when executing
Has anyone run into this, and would like to provide me with some guidance?
For more info:
I'm using Next 13.4.13
My .eslintrc.json contains:
I tried the following but still getting the error: https://stackoverflow.com/questions/71662525/failed-to-load-config-next-babel-to-extend-from-eslintrc-json
npm run lint I get this error: Failed to load config "next/babel" to extend from.Has anyone run into this, and would like to provide me with some guidance?
For more info:
I'm using Next 13.4.13
My .eslintrc.json contains:
{
"extends": ["next/babel", "next/core-web-vitals"]
}I tried the following but still getting the error: https://stackoverflow.com/questions/71662525/failed-to-load-config-next-babel-to-extend-from-eslintrc-json
Answered by American Crocodile
I solved the issue. Had to create a .vscode file at the root of my directory, and add a settings.json file that allows ESLint to access the correct directories: https://stackoverflow.com/questions/68163385/parsing-error-cannot-find-module-next-babel
Answer by Craig Kelly
Answer by Craig Kelly
3 Replies
American CrocodileOP
I solved the issue. Had to create a .vscode file at the root of my directory, and add a settings.json file that allows ESLint to access the correct directories: https://stackoverflow.com/questions/68163385/parsing-error-cannot-find-module-next-babel
Answer by Craig Kelly
Answer by Craig Kelly
Answer
American CrocodileOP
I also had to change "next/babel" to "next" in the .eslint.json file
Gray-tailed Tattler
This caused a module resolution error on Vercel for me. Since the issue was that I was not opening my VSCode project at my frontend root, this was the solution for me https://github.com/vercel/next.js/issues/40687#issuecomment-1275184829