Dylan Sather (Pipedream) : sorry to hear that and I’m happy to take a look. Would you mind clicking the Share button in the top-right of your workflow and share it with dylan@pipedream.com?
Dylan Sather (Pipedream) : Thanks. 9 days ago, tiktok-scraper added canvas as a dependency (see commit). The canvas package unfortunately fails to work on Pipedream out of the box because of this issue (the error you’re seeing here).
I’m publishing a version of tiktok-scraper v 1.4.21 (pre-canvas) to my own npm namespace to see if that works. Then hopefully you can require that and your workflow should work . I’ll get back to you once I’ve published and tested that
Dylan Sather (Pipedream) : Good to hear. You may want to read the release notes on the tiktok-scraper package to see what’s been added since 1.4.21, just to make sure there aren’t security or other issues using the older version of the package.
Dylan Sather (Pipedream) : for workflows, the package.json file is generated at runtime. We parse the require statements present in all the workflow’s code steps and download the latest versions of each package. So in this particular flow, GitHub actions isn’t involved.
Jay Vercellone : It helps, because I was going to suggest forcing the version via that file, but if it’s overridden during deployment then it wouldn’t work
Dylan Sather (Pipedream) : I think in the future we’ll either provide a way for user to pass the version directly via the require statement (e.g. require("axios@0.21.0") — we do this for event sources), or give you access to the package.json for editing.
@hanshansenrl are you trying to run specific code? If you’re seeing an error, please post the code you’re trying to run and the error you’re seeing, and we can take a deeper look.