-
-
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
[[email protected]] import stylesheet from npm package #165
Comments
This is being discussed here: meteor/meteor#6037 |
Does not see any |
@vitalyrotari Well, we just process the scss files Meteor tool feeds us. So this would require changes to meteor tool. Not much we can do with this package. |
I think the problem is in the |
Problem solved :) |
Can you create a PR |
@sebakerckhof a bit later will do ;) |
Is this working already? |
Just ran into this issue @sebakerckhof. I created a new Meteor 1.2 project, added the This created the css files in
Then I manually created
And I get:
|
Filenames of file to import need to start with an underscore, otherwise meteor does not see the file as an import. But even then it won't work due to a bug in lib-sass with old sass (indented syntax) files: sass/node-sass#1192 |
Is this issue still pending? Any new development? |
@sebakerckhof Any update on this or the PR from @vitalyrotari, thanks! |
I am also looking for a solution to this |
I follow these steps in meteor1.3, it works well |
any solution to this issue , because the bootstrap solution is too much complex |
Meteor 1.3.2 should allow you to import scss files.
See this repo for an example: https://github.com/juliancwirko/meteor-npm-foundation-test |
@skirunman does it only work if the file is SCSS? I am unable to get it to work with CSS files |
@skirunman you can add css file in your js file. for instance: |
That solution works just fine for CSS files, but it doesn't work for SCSS imports. I can't use that method to import mixins and such from an NPM module. Cross-referencing my response on meteor/meteor#6846 here. |
I am trying this
But it yields the following error. Unexpected token (3:1) |
any updates? |
As an effort to support npm, where is this issue currently at? |
I recently moved to the bay area so I'm currently too busy to look into it, but a pull request would be accepted. |
Sorry but as Meteor tries to get closer to JS land it's incredibly important to being able to |
@sebakerckhof Any guidance or help would be good. |
After updating a few Meteor packages (also npm packages) any CSS files imported from my JS modules are no longer imported. Also,
|
@skirunman any updates on this issue please? I am currently doing this |
@nosizejosh Sorry, but have not kept up on this as we are no longer using SASS or importing directly from node_modules. Hope you find a solution. |
@skirunman thank you. |
Hey, I tried to - finally upgrade - my app to Meteor 1.3. But as in any other upgrade, fourseven:scss is causing the biggest problems. Now I stumbled upon this issue, trying to import styles from npm modules I had previously imported using mquandalle:bower. I hoped that - after so many months - this would have been fixed in the meantime. But is it really still open? I was also wondering how to import fonts that are referenced in SASS files. It was so easy using mquandalle:bower in 1.2, but now I am running into this upgrade nightmare. |
This is being discussed here as well meteor/meteor/6846 |
Closing in favor of #309 |
just wonder is it possible?
1.3 introduces better npm support so we can just do
npm install foundation-sites --save
for example, but how to use it?it's so easy to import js:
import Foundation from 'foundation-sites';
but in SCSS nothing of this works:
The text was updated successfully, but these errors were encountered: