Issue with Library in Pipedream on Slack Node: What Changed and How to Fix?

Help
1

This topic was automatically generated from Slack. You can find the original thread here.

Hey guys. I’m having a problem using a library of mine in pipedream on the slack node. Before everything was fine, running without errors, we did not change any version of our SDK and began to present this error:

What could he be doing wrong? Or what’s changed so that I can start running my SDK properly again?

image.png
image.png1126×113 1.64 KB

2

Hi Danilo, what’s the library that you’re attempting to import into a Node.js step

3 
import { MySDK } from '@mysdk/hub@0.0.1';

export default defineComponent({
  props: {
    slack: {
      type: "app",
      app: "slack",
    }
  },
  async run({steps, $}) {
    ...
  }
})
4

A library of mine that is hosted on npm

5

Need the name of the library?

6

Yes that would be very helpful, I suspect there’s some kind of collision or incompatibility in the code itself.

7

I sent you in private

8

Did you see it?

9

I did thanks Danilo, but it may be problematic to report this upstream since you want to keep this NPM package location private. Our bug tracker is public.

10

I understand. The name of the npm library I’m wanting to use is @pilla/hub

11

Thanks Danilo,

Some other rhyming issues on our public issue tracker:

I believe these all have the same underlying issue. I will catalog them into one, and mention this one as another case.

12

Ok, thanks

13

I noticed that the date of the last interaction on these issues is in April, and the problem only occurred this last week, so there may be some changes, can you tell me if you are working on this problem?

14

This issue on our backlog but the cause is currently not known. Just that it’s caused my a small subset of NPM packages. The current theory is there’s some kind of conflict in dependent packages or some code level collision during environment bootstrapping.