Uploaded image for project: 'Magnolia CLI'
  1. Magnolia CLI
  2. NPMCLI-109

Best practice or command to process local light module build

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Neutral Neutral
    • None
    • None
    • None
    • Basel 87
    • 0.5

      Based on other work we recommend the source control project for a sharable light module to be buildable with 'npm run build'. Additionally we recommend using .npmignore to remove all of the files not required for the production light module - such as the _dev directory and various config files.

      This works great for packages a developer gets directly from npm - but how should a developer work which has the source control project locally - how can they easily get their built version without the dev specific files. Of course they can run 'npm run build' locally - but how to get rid of the .npmignore files?

      They could build the tar.gzip locally and then unpack that.
      Is there something more handy? could we provide a CLI command to do this?

        Acceptance criteria

              czimmermann Christopher Zimmermann
              czimmermann Christopher Zimmermann
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: