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#58397 - [npm] Legacy Version for npm?
Attached to Project:
Community Packages
Opened by Christian Rebischke (Shibumi) - Monday, 30 April 2018, 00:52 GMT
Last edited by Christian Rebischke (Shibumi) - Tuesday, 01 May 2018, 15:16 GMT
Opened by Christian Rebischke (Shibumi) - Monday, 30 April 2018, 00:52 GMT
Last edited by Christian Rebischke (Shibumi) - Tuesday, 01 May 2018, 15:16 GMT
|
DetailsHello,
I am currently building vault 0.10.1 for our repositories. The build breaks with npm 6.0. Do you plan to ship a npm legacy version or do you mind if I ship a legacy version? |
This task depends upon
Closed by Christian Rebischke (Shibumi)
Tuesday, 01 May 2018, 15:16 GMT
Reason for closing: Not a bug
Tuesday, 01 May 2018, 15:16 GMT
Reason for closing: Not a bug
Comment by Christian Rebischke (Shibumi) -
Tuesday, 01 May 2018, 15:16 GMT
There is no need for a npm-legacy version. I was a little bit too hasty. Sorry. Closing this.