-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The "sass" file extension doesn't work #5
Comments
Thank you! Its because I forgot to add the "sass" extension support. "scss" should work. Check this lines: |
Hmm... I replaced all instances of As soon as I change anything that causes hot module replacement, I get this error: This also happens if I just use If I just use |
Woopsie! My bad, turns out I need some extra TypeScript configuration to allow importing weird extensions like "scss" and "sass". Weirdly enough "css" worked by default though. Probably because of the references in Anyway, I just added these 2 lines to the bottom of declare module "*.sass";
declare module "*.scss"; I'll make a pull request asap. |
I'm having issues with the sass support built in to Next.js (specifically vercel/next-plugins#149), so I decided to try your fix.
It doesn't seem to work though.
Here is my
next.config.js
:(I added that last line in an attempt to check what next-styles added, but as it's all done in the
webpack
function it didn't help.)Here is my
src/pages/_app.tsx
file:When I run the dev server, it's throwing an error as if I hadn't configured a loader at all:
Any idea what's wrong here? Did I mess something up, or doesn't next-styles work with this Next.js version?
The text was updated successfully, but these errors were encountered: