This topic was automatically generated from Slack. You can find the original thread here.
Rodrigo Zuini : Hey guys. I just found out that an npm package (mssql/tedious) that I use was released a new buggy version but still has no deadline for resolution. Is there any way to use a specific version in my requires?
Rodrigo Zuini : Yes, the problem is in dependence on this package (tedious). Version 11.0.10 works on my local machine, but for that I need to remove the tedious folder and install again with npm install tedious@11.0.10. I don’t know how to solve it that way on the Pipedream platform so I plan to roll back the mssql version to the point where the tedious works.
Dylan Sather (Pipedream) : Thanks. We don’t yet have a way to require a specific version of a package in a workflow (tracking here, if you’d like to follow), but here’s what I do when I need to do this:
Clone the repo for the package on your local machine
Checkout the commit pointing to the version I’d like to use. Since they use Git tags in this repo, you should be able to git checkout <version> .
Change the name in the package.json to reference a scoped package name under my npm namespace. For example, I’d change the name to @dylburger/mssql , where dylburger is my npm username.
In my workflow, I require("@dylburger/mssql") to reference my scoped package, which now points to the version I originally checked out in step 2.
Let me know if that makes sense.