Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#54406 - [nodejs] yarn init hang at the version input step
Attached to Project:
Community Packages
Opened by colo D.F. (colo9) - Sunday, 11 June 2017, 11:02 GMT
Last edited by Felix Yan (felixonmars) - Thursday, 15 June 2017, 14:36 GMT
Opened by colo D.F. (colo9) - Sunday, 11 June 2017, 11:02 GMT
Last edited by Felix Yan (felixonmars) - Thursday, 15 June 2017, 14:36 GMT
|
DetailsDescription:
when i try to init a project using yarn init, it just hang at the version input step, strangly nothing being output. i have to use kill -9 to get out. i also tried npm, this happens again. When i rollback my nodejs package from 8.1.0 to 8.0.0, everything works ok. May not bugs of yarn or npm, but hope this helps. Additional info: * package version(s) nodejs 8.1.0 yarn 0.24.6 * config and/or log files etc. no config file being changed or add. no error output... Steps to reproduce: ..have no idea. Just install nodejs & yarn (with the specific version), it should be there. |
This task depends upon
Closed by Felix Yan (felixonmars)
Thursday, 15 June 2017, 14:36 GMT
Reason for closing: Fixed
Additional comments about closing: nodejs 8.1.1-1
Thursday, 15 June 2017, 14:36 GMT
Reason for closing: Fixed
Additional comments about closing: nodejs 8.1.1-1
Comment by colo D.F. (colo9) -
Wednesday, 14 June 2017, 06:09 GMT
This is nodejs bug in version 8.1.0, and found would be fixed in next version, refer to: https://github.com/nodejs/node/issues/13557
Comment by Felix Yan (felixonmars) -
Wednesday, 14 June 2017, 15:36 GMT
nodejs 8.1.1 is now in the repos. Still a problem?
Comment by colo D.F. (colo9) -
Thursday, 15 June 2017, 13:46 GMT
it's now ok when nodejs updated to 8.1.1~~