[
https://issues.apache.org/jira/browse/CB-10578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexis Kofman updated CB-10578:
-------------------------------
Summary: Be .npmignore aware when installing a plugin (was: Be npmignore
aware when installing a new plugin)
> Be .npmignore aware when installing a plugin
> --------------------------------------------
>
> Key: CB-10578
> URL: https://issues.apache.org/jira/browse/CB-10578
> Project: Apache Cordova
> Issue Type: New Feature
> Components: CLI
> Reporter: Alexis Kofman
> Priority: Minor
> Labels: cordova-cli, feature
>
> Some Cordova plugins are very well documented but sometimes this
> documentation can be too big. Sometimes they contains a lot of code samples.
> The problem is when we are installing these plugins, our projects become
> bigger and bigger.
> So far there is no way to ignore files of a Cordova plugin when installing
> it.
> In case of public npm packages, we are able to control what we want to
> publish from the .npmignore file or still from the files attribute of the
> package.son file.
> But in case of private packages, if for instance they're installed from a
> Github repository, then the `Cordova plugin add` command will ignore
> the .npmignore or package.json config. Same case if I want to use the last
> version of a plugin which is not published.
> Would that make any sense to be aware of these config (.npmignore or
> package.son) when installing a plugin ?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
