-
-
Notifications
You must be signed in to change notification settings - Fork 72
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
Can't import css files from node_modules #264
Comments
Yes, it seems loading CSS files really does not work. Loading SCSS files does, but not CSS. It seems it is all because of the wrong filename. So if I do |
I think the issue is that this code searches only over files which are known to Meteor (part of Meteor packages or app) and not over the file system. |
See #258. |
If you are using webpack you can add this to your sass-loader
else you can make a
then you can do something like |
I made a PR with CSS imports working with POSTCSS in this Meteor React boilerplate from @juliancwirko. If you're having trouble making it work, take a look. It has the SCSS preprocessor working along with the POSTCSS as well. |
@livimonte I tried the boilerplate you posted. Using leaflet as an example I can load the leaflet css but the icons won't load. I'll try to get a MWE to show you this. |
Hi @pilarArr, I think this is planned to be solved in the future as feature request see: meteor/meteor#6846 |
This issue is now moved to meteor/meteor-feature-requests#278 |
This has now been fixed in version 4.14.1 Refer to these lines in the code for details: meteor-scss/plugin/compile-scss.js Lines 182 to 185 in 1359363
|
I'm trying to import
leaflet.css
into myapp.scss
like this:I always get variations of this error
I've seen this error in many issues and I've yet to find an answer. Right now I'm using
fourseven:[email protected]
and[email protected]
. I also have this problem when importing any other css file from node_modules. Importing.scss
files fromnode_modules
does work.This is some of the research I've done:
The thing is that issue #219 is closed, in there they say that issue is a duplicate of #195, then issue #195 is also closed, and they point to issue #165 to continue the discussion there, on issue #165 they point to meteor/meteor#6037 which is also closed.
But issue #165 is off topic in the sense that it refers specifically to Meteor 1.3.
I'm using 1.5 and still have this issue.
UPDATE: This issue is now being dicussed here meteor/meteor#6846
The text was updated successfully, but these errors were encountered: