> Shouldn't we consider dropping support for
> `requireCordovaModule('cordova-lib')` or
> `requireCordovaModule('*/cordova-lib')` altogether?
I'm not sure what you mean by `requireCordovaModule('*/cordova-lib')`. After
#709, The argument for `requireCordovaModule` must be either the name of a
Cordova package (`cordova-*`) or a path to a module in a Cordova package
(`cordova-*/**`).
In case you meant we should drop the method altogether: I actually considered
that. But as long as the predominant usage of `cordova-lib` & Co. is through a
globally installed package `cordova` I think we need a means for people to
require modules from the _currently executing_ version of Cordova. Which is
exactly what `requireCordovaModule` provides.
---
That being said, I would prefer that people require `cordova-lib` or `cordova`
as a dependency in their projects and use only that to build them. That way
regular `require` would pick up the right versions of everything and it would
be perfectly clear which version of Cordova is required to build a project.
[ Full content available at: https://github.com/apache/cordova-lib/issues/689 ]
This message was relayed via gitbox.apache.org for [email protected]
