Skip to content
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

perf: ionic setup sass #234

Closed
jbavari opened this issue Feb 9, 2015 · 10 comments
Closed

perf: ionic setup sass #234

jbavari opened this issue Feb 9, 2015 · 10 comments
Assignees

Comments

@jbavari
Copy link

jbavari commented Feb 9, 2015

From @mifama on February 6, 2015 23:16

Type: perf

Platform: desktop browser

I updated the ionic version to last version, and now when I do 'ionic setup sass' it's return
npm install

Copied from original issue: ionic-team/ionic-framework#3049

@jbavari
Copy link
Author

jbavari commented Feb 20, 2015

Could you paste the contents from ionic info?

Scanning the node-sass issues, it looks like theres an issue filed about this and Node v0.12

@toby1kenobi
Copy link

I have this issue too, ionic info shows:

Your system information:

OS: Windows 8.1
Node Version: v0.12.0
Cordova CLI: 4.3.0
Ionic Version: 1.0.0-rc.0
Ionic CLI Version: 1.3.14

Is there a work around, or fix, do you know?

@jbavari
Copy link
Author

jbavari commented Mar 11, 2015

@toby1kenobi can you post some of the error log as you saw them? It'd help to see that.

Or, did you have the same output as the original poster?

@jbavari
Copy link
Author

jbavari commented Mar 12, 2015

@toby1kenobi and @mifama - Try updating your package.json file - change gulp-sass to be this:

"gulp-sass": "^1.3.3",

This should bump gulp-sass to use node-sass 2.x, which should resolve that issue.

@jbavari
Copy link
Author

jbavari commented Mar 12, 2015

Closing - since this is more of a node-sass and gulp-sass issue.

@toby1kenobi
Copy link

Sorry for delay, will try your suggestion

@jbavari
Copy link
Author

jbavari commented Mar 12, 2015

Please do. I was able to recreate it last night on my Windows machine like you had, and bumping that version solved the issue.

One other thing to note - at first I had trouble since Python is required, I installed 3.5, that had some issues. I found a stackoverflow post that specified using Python 2.7, which also helped.

Not sure if that is absolutely required though.

@toby1kenobi
Copy link

Brilliant, that did it - thanks!

@jbavari
Copy link
Author

jbavari commented Mar 12, 2015

Yep. Were you running python 2.7 or 3.5?

@toby1kenobi
Copy link

2.7 - I was anyway, but as a result of some previous node-related situation

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants