-
Notifications
You must be signed in to change notification settings - Fork 32
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
Handling Sass Imports #24
Comments
|
:( same here, any soluction? |
same here |
Anyone figure out how to resolve this? I'm able to use .css files, but the moment I switch over to .scss I get a similar error: |
Same thing here. Didnt have this issue when running only docz not attached to a real project. |
I believe this plugin |
Just figured out the solution for our team: We don't use docz:build nor docz:dev if it's a gatsby project. You have to run gatsby develop and the error won't occur. Just set up the route in index.mdx to be on /docs, and everything works. Set up the routes on every .mdx file to be relative to /docs. If you project isn't build on top of gatsby, this won't work for you. I got this error because i didn't understood the documentation correctly, if your project is built with gatsby you shouldn't run docz commands, just configure the routes on de mdx files properly and it works. |
My app has a Sass structure where individual component
.scss
files, collocated with the components they style, use Sass imports (@import ...
) to pull in global variables from a centralized styles folder.When I try using this package:
I get the following error on doc build:
I assume once I clear up this error, I may also have to set up the root folder for Webpack to search for these styles (eg something like the below):
But before I hit that error, I'm having trouble figuring out how to handle this one, and get the internal Sass dependencies to import.
Is this something this plugin supports?
The text was updated successfully, but these errors were encountered: