2 action build modes are supported for now:
a. in manifest.yml point to action file: Minifies action and action's dependencies using parcel
b. in manifest.yml point to the action's directory + package.json file in action's folder: Installs dependencies and zips the action
But if we point to an action file + have a package.json file in the folder, parcel installs unnecessary dev dependencies such as @babel/core which pollutes the action folder with a package-lock.json and node_modules/ and modifies the package.json file.
Expected Behaviour
Best: bundle action with parcel without polluting folder
Middle: don't bundle with parcel, create a zip action instead if there is a package.json file
at least: show an error
Actual Behaviour
Unnecessary installed dependencies in developer's action folder
2 action build modes are supported for now: a. in manifest.yml point to action file: Minifies action and action's dependencies using parcel b. in manifest.yml point to the action's directory + package.json file in action's folder: Installs dependencies and zips the action
But if we point to an action file + have a package.json file in the folder, parcel installs unnecessary dev dependencies such as
@babel/core
which pollutes the action folder with apackage-lock.json
andnode_modules/
and modifies thepackage.json
file.Expected Behaviour
Best: bundle action with parcel without polluting folder Middle: don't bundle with parcel, create a zip action instead if there is a package.json file at least: show an error
Actual Behaviour
Unnecessary installed dependencies in developer's action folder
Steps to Reproduce
cd actions/hello
npm init
cd ../../
npm run build:actions