-
Notifications
You must be signed in to change notification settings - Fork 669
NodeJS 6 support #960
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
Comments
Hey! Thanks for opening an issue with us! Since this issue is more related to the CLI than the framework I will be moving this issue over to that repo. Thanks! |
Thanks for the issue, we'll need to take a look at our dependencies and make sure they are Node 6 compatible. |
Same problem |
+1. I also have the same problem. |
+1 |
This might be related to the fact that node-sass doesn't yet support Node 6 sass/node-sass#1484 Downgrade Node to v5.11.0 and you should be fine. |
try check your graceful-fs version with
found package that depends on old version of graceful-fs. Update it and start your apps again. It works for me. hopefully it can help :) |
I have a couple packages indeed who depend on version 3 (one even depends on version 1.2.3) but I don't think I can update the dependencies of a specific package? |
If you won't to update it, try search modules/package on folder |
Same problem!!! |
me to - same problem |
Same problem!!! |
Same problem here! |
I have the same problem |
I would suggest to everyone using Node v6 to downgrade to the latest Node v5 release. For more details read the following topic: DON’T rush to upgrade to Node v6. There are 89!!! breaking changes in Node v6 and I guess that it will take some time until all packages catch up. |
@iignatov I agree. Package maintainers have to have a chance to update their modules to work with node 6. Node 6 is great! But, it is just gonna take a little while for modules to support it. We are currently working on this, and hope to have the ionic cli working with Node 6 soon, but for now the best solution is too probably downgrade to the latest Node 5 release. |
As I see it the main failing package is graceful-fs and I have been getting deprecation messages for that package for ages now. Any package maintainer got more than the chance to upgrade their dependencies long ago when they started spamming everyone with deprecation messages when installing their packages |
Perhaps someone find it useful - not a solution, but a temporary walk-around for graceful-fs and alike modules: https://gist.github.com/bondden/2d2e07d18d94d1f4dc23b7dcf9b0e350 |
I don't know if it was mentioned, but I got pointed here. There is another issue with v6: Run Ref: yargs/yargs#497, nodejs/node#6456 Possible fix not using process.exit() and respective handlers. yargs/yargs#498 |
Thanks @eljefedelrodeodeljefe ! |
@jgw96 (don't know if it's new) concerning
|
Hey, yeah we are already aware of the package version issues. We are currently being held back by the fact that some of our dependencies have yet to update to work with node 6. The cli team hopes to have full node 6 support within the next couple of beta cli releases (: |
I downgraded to node 5 and it works fine:
|
@kienpham2000 I'm aware it runs just fine under NodeJS5 but this issue is related to the support for version 6. Downgrading has already been suggested multiple times |
vinyl-fs is using the old version of graceful-fs ([email protected]), which itself depends on [email protected] |
Correct me if I'm wrong but their package.json doesn't seem to reference ionic |
@nunoarruda, @iignatov Downgrading the node version to v5.11.1 resolved my problem. Thanks a lot for sharing the issue with latest node version 6. |
Any news regarding this issue? when we will be able to use node v6? |
Same problem!!! |
FWIW: samesies. |
@ahmed-abdulmoniem And were you able to build a working ionic app? |
@gurisko Yeah I have built my application debug/release and the apk file has been generated. |
@gurisko Could you let me know if you are still experiencing issues. Could you also paste the results of running |
Sorry for the late answer - it took me some time to debug the problem properly. |
Note that 1.2.3 does not cause the runtime warning. Only Tracking: nodejs/node#5213.
|
Other things to note:
|
Also:
There might be more, I just mentioned the ones that I spotted. |
Thought I had this issue but it turned out to be something else. I am able to to use the cli as expected with node 6.6.0 In case it helps someone else, here is what I'm running:
|
Problem is not yet fixed. graceful-fs is still getting installed with version 1.2.3 on node 6.9.3.
Yet NodeJS 6 is what is documented in: http://ionicframework.com/docs/v2/getting-started/installation/ |
After update gitbook to latest version, it works well. node: 6.2.0
npm: 3.8.9
gitbook: 3.2.2 |
#ionic info then info shows but i am unable to make android app. plz help me ? |
In my case uninstall gulp in global and i can run ionic run android withour problem. |
From @dealloc on April 27, 2016 12:30
Short description of the problem:
Ionic currently uses a deprecated version of graceful-fs which generates an enormous amount of stack traces when serving, or any other action for that matter
Steps to reproduce:
ionic serve
Which Ionic Version? 1.x or 2.x
Ionic 2.0.0-beta.25
Run
ionic info
from terminal/cmd prompt: (paste output below)Copied from original issue: ionic-team/ionic-framework#6340
The text was updated successfully, but these errors were encountered: