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

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

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

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

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

Nacho Caballero : Like this?

Nacho Caballero : still undefined

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

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

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

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

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

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

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

TJ Koblentz : or change that line to:

TJ Koblentz : ```
const scopedPackageVersion = require(‘root-require’)(‘package.json’).dependencies[’@nachocab/pipedream-global_QDIuMC41’]

Nacho Caballero : got it. So this wasn’t working before, right? You fixed it yesterday?

TJ Koblentz : yes i think it should work now

Nacho Caballero : Great, thanks. I’ll let you know if I run into any trouble going forward :+1:

TJ Koblentz : awesome! thank you