[
https://issues.apache.org/jira/browse/CB-13298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16298559#comment-16298559
]
Shad Sterling commented on CB-13298:
------------------------------------
I install Cordova as a peer for Ionic, I’m not going to bring in breaking
changes to Cordova and risk breaking Ionic. You’re saying I can’t get bugfixes
on Cordova without upgrading most of our stack, which will likely require an
expensive update to our code, which we’re trying to do on our own schedule
rather than whenever we find bugs in a dependency.
Generally speaking, your dependencies should be implementation details your
consumers don’t have to worry about. Is the reason this dependency wasn’t
hidden from your consumers documented somewhere?
> npm WARN deprecated node-uuid@1.4.8: Use uuid module instead
> ------------------------------------------------------------
>
> Key: CB-13298
> URL: https://issues.apache.org/jira/browse/CB-13298
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-common
> Affects Versions: 7.0.1
> Environment: NPM 5.4.0
> Reporter: Shad Sterling
> Priority: Minor
> Labels: beginner, dependencies, deprecation, easyfix,
> reproduced, triaged
>
> Running `npm install` with Cordova as a dependency raises this warning
> message:
> {code}
> npm WARN deprecated node-uuid@1.4.8: Use uuid module instead
> {code}
> `npm ls node-uuid` shows that Cordova depends on `node-uuid` in two places:
> {code}
> └─┬ cordova@7.0.1
> ├─┬ cordova-lib@7.0.1
> │ └─┬ npm@2.15.12
> │ └─┬ request@2.74.0
> │ └── node-uuid@1.4.7
> └─┬ insight@0.8.2
> └── node-uuid@1.4.8
> {code}
> The dependencies on `insight` and`npm` should be updated.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
