CSS Imports seems broken
Answered
Ninhache posted this in #help-forum
NinhacheOP
Any idea where the problem can comes from ?
I've already check the hierarchy and seems not from it :
Some topics are talking about bad
And i've already read the provided link and.. i didnt found anything interesting..
I've already check the hierarchy and seems not from it :
// Similar Hierarchy reproduction
> components
⌄ pages
> api
- _app.js
- index.js
⌄ styles
- globals.css
- Header.module.cssSome topics are talking about bad
next.config.js but idk if it's from there..And i've already read the provided link and.. i didnt found anything interesting..
Answered by joulev
you need to configure absolute path config with tsconfig or jsconfig like so https://nextjs.org/docs/app/building-your-application/configuring/absolute-imports-and-module-aliases#absolute-imports
9 Replies
@Ninhache Any idea where the problem can comes from ?
I've already check the hierarchy and seems not from it :
txt
// Similar Hierarchy reproduction
> components
⌄ pages
> api
- _app.js
- index.js
⌄ styles
- globals.css
- Header.module.css
Some topics are talking about bad `next.config.js` but idk if it's from there..
And i've already read the provided link and.. i didnt found anything interesting..
you need to configure absolute path config with tsconfig or jsconfig like so https://nextjs.org/docs/app/building-your-application/configuring/absolute-imports-and-module-aliases#absolute-imports
Answer
it was never an automatically enabled feature, you need to explicitly enable it
NinhacheOP
I'm the clownest
ty tho.. i've figured out the jsconfig got deleted.. uh i feel stupid rn
yeah, recover that file and absolute path import will work again