[magnolia-dev] [JIRA] (NPMCLI-27) Own config for mgnl-cli instead of package.json

[JIRA (on behalf of Christopher Zimmermann)]

Title: Message Title

Christopher Zimmermann created an issue   Magnolia CLI npm module / NPMCLI-27 Own config for mgnl-cli instead of package.json Issue Type: Improvement Assignee: Unassigned Created: 14/Jul/16 4:44 PM Priority: Neutral Reporter: Christopher Zimmermann There are problems with using the package.json file to store the configuration for the CLI. When having a local mgnl configuration in your project, It is confusing to have an additional package.json which is basically unrelated to your project. Especially if you are working on an npm module, which should be a common practice with light development. In this context the local cli configuration is NOT a node package, so its incorrect to have the file there. The contents of the package.json get alphabetically re-ordered and additional meta information is added via npm processes which make the file hard to work with, plus it stores a lot of irrelevant information. Configuration for the mgnl cli should be stored in a new file. Maybe "mgnl-cli.json" or "mgnl-cli.yaml" depending on its format. Add Comment   This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) ---------------------------------------------------------------- For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <dev-list-unsubscr...@magnolia-cms.com> ----------------------------------------------------------------