Community forums
Tooling: how to build and package just 1 widget
Quote from Scott Kearney on October 29, 2019, 10:59 amYou can package a single widget via the command:
npm run package HeroBanner
Where HeroBanner is the FOLDER of the widget in the src/js/widgets folder.
This will pack that one only, and place the widget ZIP in the build location; see in the akumina.config.json file:
WidgetPackageDestinationPath
You can package a single widget via the command:
npm run package HeroBanner
Where HeroBanner is the FOLDER of the widget in the src/js/widgets folder.
This will pack that one only, and place the widget ZIP in the build location; see in the akumina.config.json file:
WidgetPackageDestinationPath
Quote from Sara Kevorkian on November 8, 2019, 1:09 pmi was talking with one of my coworkers about this, we think it would be really useful if the default behavior was to package one widget (a prompt to provide widget name if you dont provide one) and use a flag only when you want to package all of them. i keep intending to only deploy one widget and forgetting to delete the old packages and ending up wasting time 🙁
i was talking with one of my coworkers about this, we think it would be really useful if the default behavior was to package one widget (a prompt to provide widget name if you dont provide one) and use a flag only when you want to package all of them. i keep intending to only deploy one widget and forgetting to delete the old packages and ending up wasting time 🙁
Quote from Scott Kearney on November 11, 2019, 11:34 amSara,
You can actually use the command:
npm run clean
And that will clean out the widget packages, so you can then run a package of only your desired widget.
Sara,
You can actually use the command:
npm run clean
And that will clean out the widget packages, so you can then run a package of only your desired widget.
Quote from Scott Kearney on January 15, 2020, 8:46 amJust wanted to note we have a new article explaining this topic:
https://akumina.github.io/docs/Akumina-Npm-Commands
Thanks!
Just wanted to note we have a new article explaining this topic:
https://akumina.github.io/docs/Akumina-Npm-Commands
Thanks!