npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@magnolia/cli-create-component-plugin

v1.0.0

Published

A plugin for Magnolia CLI to create a headless or freemarker-based component

Downloads

99

Readme

CreateComponentPlugin

A plugin for Magnolia CLI to create a headless or freemarker-based component

Installation

Using add-plugin

  1. Run the following command in the project's root directory:

    npm run mgnl -- add-plugin @magnolia/cli-create-component-plugin

    The command will install the plugin, and automatically register the plugin in mgnl.config.js file:

    import CreateComponentPlugin from "@magnolia/cli-create-component-plugin";
    
    export default {
      plugins: [
        new CreateComponentPlugin()
      ]
    };
  2. To confirm that the plugin has been successfully installed, run:

    npm run mgnl -- create-component --help

Manually

  1. Run the following command in the project's root directory:
    npm install @magnolia/cli-create-component-plugin
  2. Manually add CreateComponentPlugin to mgnl.config.js file:
    import CreateComponentPlugin from "@magnolia/cli-create-component-plugin";
    
    export default {
      plugins: [
        new CreateComponentPlugin()
      ]
    };
  3. To confirm that the plugin has been successfully installed, run:
    npm run mgnl -- create-component --help

Usage

Options

| Short | Long | Description | |---------------------------------------|------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | -a [[lm-name:]page-template[@area]] | --available [[lm-name:]page-template[@area]] | specify the page to make the component available to; format: [lm-name:]page-template[@area]; defaults: [lm-name:] to 'lightModule' from mgnl.config.js, [@area] to 'main' if not specified; example: 'my-lm:basic@main' | | -lm [name] | --light-module [name] | set the light module for the component template; defaults to the directory specified in mgnl.config.js file | | -p [name] | --prototype [name] | select a prototype for component creation | | -v | --version | output the version number | | -h | --help | display help for command |

Configurable Properties in mgnl.config.js

Global Properties

| Property | Description | |----------------------------|----------------------------------------------------------------| | componentMappingFilePath | The path to the file containing the componentsMapping object | | lightModulesPath | The directory with all light modules | | lightModule | The selected light module | | type | The type for the selected prototype, e.g., ts or js |

Plugin-Specific Properties

| Property | Description | |----------------------------|------------------------------------------------------------------------------------------------| | componentsSpaPath | The path to the folder containing the front-end components | | lightModule | The selected light module | | framework | The framework prototype to use for component creation (e.g., @magnolia/cli-react-prototypes) | | prototype | The name of the prototype to be used | | templateData | A key-value object used by Handlebars for template rendering | | templateArgs | A key-value object that modifies how the prototype behaves |

Examples

Create a component

npm run mgnl -- create-component "myFooComponent" --framework "@magnolia/cli-react-prototypes" --prototype "basic"

This command creates a new component called "myFooComponent" based on "basic" prototype from "@magnolia/cli-react-prototypes" framework. If any properties (e.g., lightModulesPath, lightModule, framework, etc.) are missing from the mgnl.config.js file, the plugin will prompt you to provide them. The entered values will be saved in the mgnl.config.js file for future use.

Create a component and make it available to a specific page and area

npm run mgnl -- create-component "myFooComponent" --available "my-lm:contact@main"

This command creates a new component called "myFooComponent", and makes it available to the "contact" page in the main area. Missing properties will be prompted for and saved as described above.

Plugin Documentation

For detailed documentation of the plugin, please refer to Plugin Documentation

Magnolia CMS

This plugin is created to work with Magnolia CMS. For more information, please refer to Magnolia CMS Documentation