@magnolia/cli NPM

Magnolia Light Development CLI tool

An npm package providing a CLI tool to setup and facilitate light development with Magnolia. For a complete reference including installation and usage please visit Magnolia CLI documentation.

Fix an issue with downloading snapshot versions NPMCLI-251, NPMCLI-286
Add additional info into error message when 'unable to get local issuer certificate' occures NPMCLI-285

Downgrade the async dependency back to ^2.6.0 to fix logs in terminal when starting Magnolia

All users of Magnolia 6.2.x are recommended to upgrade to CLI 4.0.0

The create commands now generate Magnolia 6 UI definitions by default. Since these definitions are incompatible with Magnoila 5 UI, we update the CLI to new major version (4.0). https://jira.magnolia-cms.com/browse/NPMCLI-236
The dialog definitions of component and page templates and the app definition are affected by the change.
You can still generate the 5 UI definitions with the create commands by using the -P or --prototype flag to specify one of the m5 prototypes.
As a convenience, if the CLI can detect that the current location is used by a < 6.2.x version of Magnolia, then it will use the _default-m5 prototypes automatically.
- The CLI can detect the Magnolia version when the 'light-modules' directory is adjacent to an 'apache-tomcat' directory, as is the case when Magnolia is installed with mgnl jumpstart command.
If you would like the CLI to generate 5 UI definitions by default for certain projects, you can use the customize-local-config command which generates a local version of all of the prototypes used in the create commands. Then you can change the prototypes to suit your needs. (Such as renaming the_default-m5 prototypes to _default.)
Problem with jumpstart command fixed: 'ERR! Cannot read property 'status' of undefined' https://jira.magnolia-cms.com/browse/NPMCLI-239

This new release comes with full support for Magnolia 6.1 and content types. It will also seamlessly handle both the new DX Core artifacts coming with 6.1 and the old ones
- When Magnolia version is the latest (6.1 or higher), jumpstart will display the new dx-core webapps
- When Magnolia version is less than 6.1, e.g. jumpstart -m 5.7.3 it will display EE bundle and cloud webapps
Two new commands have been added (https://jira.magnolia-cms.com/browse/NPMCLI-149)
- create-app - creates a content type and an app based on it
- create-content-type - creates a content type
Fix issue with running jumpstart behind proxy https://jira.magnolia-cms.com/browse/NPMCLI-206
Update third party dependencies due to some vulnerabilities https://jira.magnolia-cms.com/browse/NPMCLI-223

Users on prior versions of the CLI are encouraged to upgrade to 3.1

Security fix related to adm-zip dependency https://jira.magnolia-cms.com/browse/NPMCLI-198
Updated to latest lodash due to moderate vulnerability revealed by npm audit

Snapshot flag is now applied to tomcat-barebone as well. https://jira.magnolia-cms.com/browse/NPMCLI-194

Solved an issue with the create-page command on Windows where the dialog and templateScript properties were incorrectly set to undefined. See details at https://jira.magnolia-cms.com/browse/NPMCLI-189

Solved an issue with the jumpstart command caused by a regression introduced by adm-zip dependency. See details at https://jira.magnolia-cms.com/browse/NPMCLI-182

A new prototype structure has been introduced, see Prototypes in CLI v3 and also Updating CLI to v3 for migration of prototypes from CLI v2 to CLI v3.
The jumpstart command has been significantly improved. It now provides a list of available webapps you can choose from.
Two new commands have been added:
- create-block - creates a block definition
- create-virtual-uri - creates a virtual uri mapping definition

(For a full list of changes please see the release history).

A new option -c (--cloud) has been added to the jumpstart command. The mgnl jumpstart --cloud will download and setup a Magnolia Cloud Enterprise bundle. It requires credentials to access Magnolia Nexus.

Two new commands have been added:
- search - to discover light modules on the npm site
- install - to easily install a light module from the registry into your light modules folder

The setup command has been replaced with customize-local-config (or its alias customise-local-config, yes with an s instead of z) because we thought it was a better name :).