You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using local triggers, the trigger's dependencies (defined in triggers/<trigger-name>/package.json) aren't installed when running Actionsflow as an action.
As a workaround, it looks like adding the dependency to the root NPM module (package.json instead of triggers/<trigger-name>/package.json) and setting using: "local" resolves this, seeing as actionsflow-action runs npm install when using === "local".
This of course breaks with the contained nature of packages, and requires using: "local", so it isn't a long-term solution.
Description
When using local triggers, the trigger's dependencies (defined in
triggers/<trigger-name>/package.json
) aren't installed when running Actionsflow as an action.As a result the "Run Actionsflow" step fails with
Steps to reproduce
See my demo repo.
Alternatively, create a local trigger yourself:
triggers/foobar/
directorynpm init && npm install cheerio
index.js
file containingconst { load } = require("cheerio");
foobar
trigger to one of your workflowsExpected result
The trigger dependencies should be installed, and the trigger should execute.
Actual result
The trigger dependencies were not installed, so the trigger failed with
Error: Cannot find module '<dependency-name>'
The text was updated successfully, but these errors were encountered: