[
https://issues.apache.org/jira/browse/CB-13719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacob Weber updated CB-13719:
-----------------------------
Description:
If you don't include a package.json in your project, my understanding (from
[here|https://cordova.apache.org/news/2017/05/04/cordova-7.html]) was that
running "cordova prepare" should create it, based on your config.xml.
This normally works fine. But if I include a plugin with a local path in
config.xml, e.g.
{code}
<plugin name="cordova-plugin-test" spec="custom_plugins/cordova-plugin-test" />
{code}
and then run "cordova prepare" using cordova-cli 8.0.0, it will no longer
download all the plugins' dependencies to node_modules. It only puts the
platform and plugins that I specified in config.xml there, not any of their
dependencies. And the package.json that it generates doesn't include the local
plugin. As a result, it can cause
[errors|https://github.com/dpa99c/cordova-custom-config/issues/138] with other
plugins later on.
This wasn't the case with cordova-cli 7.x. Is it now a requirement that we
include a package.json as well as a config.xml? This seems to mean that we need
to maintain a duplicate list of plugin versions.
For an example, run "cordova prepare" on the attached project, using
cordova-cli 8.0.0.
was:
If you don't include a package.json in your project, my understanding (from
[here|https://cordova.apache.org/news/2017/05/04/cordova-7.html]) was that
running "cordova prepare" should create it, based on your config.xml.
This normally works fine. But if I include a plugin with a local path in
config.xml, e.g.
{code}
<plugin name="cordova-plugin-test" spec="custom_plugins/cordova-plugin-test" />
{code}
and then run "cordova prepare" using cordova-cli 8.0.0, it will no longer
download all the necessary files to node_modules. It only puts the platform and
plugins that I specified in config.xml there, not any of their dependencies.
And the package.json that it generates doesn't include the local plugin. As a
result, it can cause
[errors|https://github.com/dpa99c/cordova-custom-config/issues/138] with other
plugins later on.
This wasn't the case with cordova-cli 7.x. Is it now a requirement that we
include a package.json as well as a config.xml? This seems to mean that we need
to maintain a duplicate list of plugin versions.
For an example, run "cordova prepare" on the attached project, using
cordova-cli 8.0.0.
> When "cordova prepare" creates package.json, it doesn't include all node
> modules
> --------------------------------------------------------------------------------
>
> Key: CB-13719
> URL: https://issues.apache.org/jira/browse/CB-13719
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-cli
> Environment: Mac OS 10.13.2, cordova-cli 8.0.0.
> Reporter: Jacob Weber
>
> If you don't include a package.json in your project, my understanding (from
> [here|https://cordova.apache.org/news/2017/05/04/cordova-7.html]) was that
> running "cordova prepare" should create it, based on your config.xml.
> This normally works fine. But if I include a plugin with a local path in
> config.xml, e.g.
> {code}
> <plugin name="cordova-plugin-test" spec="custom_plugins/cordova-plugin-test"
> />
> {code}
> and then run "cordova prepare" using cordova-cli 8.0.0, it will no longer
> download all the plugins' dependencies to node_modules. It only puts the
> platform and plugins that I specified in config.xml there, not any of their
> dependencies. And the package.json that it generates doesn't include the
> local plugin. As a result, it can cause
> [errors|https://github.com/dpa99c/cordova-custom-config/issues/138] with
> other plugins later on.
> This wasn't the case with cordova-cli 7.x. Is it now a requirement that we
> include a package.json as well as a config.xml? This seems to mean that we
> need to maintain a duplicate list of plugin versions.
> For an example, run "cordova prepare" on the attached project, using
> cordova-cli 8.0.0.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
