-
-
Notifications
You must be signed in to change notification settings - Fork 71
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
Package not working in project. #1
Comments
Hey Sam, could you either include the error messages or link me to a gist is breaking please? It works for me but I'm happy to try and work out what's not working for you. |
Hi there,
|
Which version of node are you running? |
Im running version v.0.10.7 |
Is this the first meteor project that you've used this scss package in? I'm still trying to reproduce it, judging from your file paths it's running on Mac OS? Which version? I'll try and update the package to the new node-sass release which may help, but there's no guarantee. |
yeah this is the first project using the scss package. Yeah running Mountain Lion. Could it be something to do with folder structure of the app or does that have no relevance? |
The app structure should not be a factor - this package associates .scss files to node-sass (anywhere in the file structure) and hands off to that to do the compilation. There have been a few issues raised in the node-sass project about the Module version mismatch error, which is associated with modules and node versions not matching (0.8.x vs 0.10.x) - however I don't see why the Mac OS one is broken, it should be compiled for 0.10.x and is functioning for me. Do you have node-sass installed globally? |
Ah maybe it's because I don't have node-sass installed. I thought the meteor scss package installed it as a dependency. What's the best way of installing it? |
It should, so the fact that it is installed is a good thing. node-sass should be hidden away in: $PROJECT_FOLDER/.meteor/meteorite/packages/scss/.npm/node_modules if meteor is doing it's thing correctly. The package.json file in that (node-sass sub-)folder should also list it's version, which, with luck should be 0.4.4. Can you confirm this for me please? |
Apologies for the delay in getting back I can confirm that the package.json reads version 0.4.4 |
I've just had @bowmande update the versions to the latest node-sass, does that help? (scss package latest is 0.5.1.1) |
How would I go a out updating the package? Everytime I run mrt update it On Thursday, June 6, 2013, Mathew Hartley wrote:
|
The less drastic way is mrt update scss or remove and re-add the package. |
I just added travis configuration, and that's failing with the same problem as you're experiencing. Which is good, but I'm still perplexed - https://travis-ci.org/fourseven/meteor-scss/builds/7858318 |
It looks like its passing now on Travis. |
Just reinstalled the package though and its still crashing as soon as I create and scss file |
I'll investigate to why it is working for me. Sent from my iPhone On Jun 7, 2013, at 3:52 AM, Sam Mason notifications@github.com wrote:
|
It's passing, but it shouldn't be, the log is showing the same error as you've referenced above. |
I'm still looking into this, node modules are cryptic when they're not obscured by meteor... |
This seems to be a problem with node-sass directly. They suspect a node version issue. sass/node-sass#102 |
Strange though as it looks like the issue is on older versions of node. I'm On Tuesday, June 25, 2013, Matthew Turney wrote:
|
We actually got this working after just bouncing the VM. Not sure how that could have affected anything, but it happened. |
Ah I see, I have just checked again and it it still throwing the same error On Tuesday, June 25, 2013, Matthew Turney wrote:
|
i'm having the same issue, is there any workaround or fix?
versions: |
Hey all, I'm still struggling to find the cause for this - it works fine in isolation, but in some configurations it's doing what you see above. I'm still working on it, though any help appreciated. |
Hey I had the same issue on two different machines (both osx) |
after i formatted my HD and reinstalled all aplications, sass does not give me this error anymore and it is fully working. |
I've released a new version (0.6.4.1) to match the Meteor 0.6.5 packages API, please let me know if that helps. |
Having this issue. Tell me if any information would help. |
Hi guys, having this issue on Ubuntu 13.04. Any info? |
I was having similar issues. To resolve, I updated my node version via NPM: From there, I removed node-sass and then reinstalled using:
Using mrt, I added the meteor-scss packaged back to my project:
All is well now. Cheers. |
This has been properly resolved with #7 |
updated readme to include Compatibility matrix for Meteor version 1.4
I installed the package in a meteor project and for some reason whenever I try and boot the app it fails. Should it be in a certain folder or named a certain thing?
The text was updated successfully, but these errors were encountered: