Issue with Pipedream using the newest published version of an npm package

Help
, , ,
21

TJ Koblentz : @nachocab/pipedream-global - npm

22

Nacho Caballero : Oh, sorry. I meant 2.0.4

23

TJ Koblentz : that should work right? i’m still trying to figure out the issue with @latest — but hopefully specific versions should not error anymore?

24

Nacho Caballero : No, if you check the screenshot you’ll see I used 2.0. 4

25

Nacho Caballero : It was a typo in slack

26

TJ Koblentz : yes but now it should work

27

Nacho Caballero : Thanks. I’ll test it tomorrow :+1::skin-tone-3:

28

Nacho Caballero : Hi I just published 2.0.5 and tested require('@nachocab/pipedream-global'), which logged 2.0.3 and require('@nachocab/pipedream-global@2.0.5'), which logged undefined

image.png
image.png1106×614 47.8 KB

29

TJ Koblentz : can you make changes in other parts of the code

30

TJ Koblentz : i want to see if it’s just a problem with the caching strategy

31

TJ Koblentz : like if you make a line with a comment and just put random stuff in that comment between saves as well

32

Nacho Caballero : Like this?

image.png
image.png1850×1604 268 KB

33

Nacho Caballero : still undefined

image.png
image.png1484×310 26.5 KB

34

TJ Koblentz : oh wait what does that scopedPackageVersion line say?

35

TJ Koblentz : i think it’s working just there is a little magic going on — so it’s not at that spot in the object

36

TJ Koblentz : ```
‘@nachocab/pipedream-global_QDIuMC41’: ‘npm:@nachocab/pipedream-global@2.0.5’,

37

TJ Koblentz : the suffix is there to support multiple versions of packages at once :slightly_smiling_face:

38

TJ Koblentz : and it’s base64 encoded because npm doesn’t allow @s, etc. in there

39

Nacho Caballero : const scopedPackageVersion = require(‘root-require’)(‘package.json’).dependencies[’@nachocab/pipedream-global’]

40

TJ Koblentz : just print out .dependencies and you will see what i mean — the dependency is being named differently