See npm package version

Reply to See npm package version on Sun, 19 Jul 2020 06:13:02 GMT

Joseph Benguira — Sun, 19 Jul 2020 06:13:02 GMT

@Daniel-Mulroy In fact not, each time you add/remove a dependency it will redownload/reinstall all the NPM deps ...
It's only if you do NO changes at all (no add, no remove of package, so in fact nothing ...) that the deps are not rebuilt

About updating package across all functions, this is clearly an Anti-Pattern in Serverless!
each micro service must be completely independant and not affected by changes of other functions

Reply to See npm package version on Sat, 18 Jul 2020 16:42:59 GMT

ThomasD — Sat, 18 Jul 2020 16:42:59 GMT

@Daniel-Mulroy If that's the case, that's very bad for security...

Reply to See npm package version on Sat, 18 Jul 2020 11:48:46 GMT

Daniel Mulroy — Sat, 18 Jul 2020 11:48:46 GMT

@ThomasD said in See npm package version:

I'm guessing they always default to latest, which can be breaking stuff for packages that become unmaintained...

From a previous conversation with support, I understood that they cache the copy of the npm package when you hit 'Save'. Thus, the version is NOT updated unless you uncheck the package, hit 'save', then re-open the library manager, re-add the package, and hit 'Save' one last time. @wassim can you confirm?

I'd like to extend it to be able to pin package versions.
I think this is the current behavior (again I hope @wassim can confirm).

I would really like the ability to update a certain package across all functions.

Reply to See npm package version on Fri, 17 Jul 2020 08:24:39 GMT

Wassim — Fri, 17 Jul 2020 08:24:39 GMT

You're both right, it would be great! Added to the list

Reply to See npm package version on Fri, 17 Jul 2020 07:57:59 GMT

ThomasD — Fri, 17 Jul 2020 07:57:59 GMT

I'm guessing they always default to latest, which can be breaking stuff for packages that become unmaintained...

I'd like to extend it to be able to pin package versions.