re-create package-lock for storybook

[johannesleite]

This needs confirmation if it should be done or not. It adds resolved and integrity to all entries in package-lock and updating a bunch of the packages in there.

[johannesleite]

@fbosquet-azpn any opinion on this?

[fbosquet-azpn]

@fbosquet-azpn any opinion on this?

I usually try to avoid directly modifying the package-lock.json unless it's necessary to fix a critical security issue that can't be resolved by simply upgrading a version in the package.json file first.

How was this package-lock updated? Do you know if it resulted from running npm audit fix or something else?

[johannesleite]

I usually try to avoid directly modifying the package-lock.json unless it's necessary to fix a critical security issue that can't be resolved by simply upgrading a version in the package.json file first.

How was this package-lock updated? Do you know if it resulted from running npm audit fix or something else?

@fbosquet-azpn It was updated by deleting it, deleting node modules and installing packages again.

It resolves some vulnerabilities that Snyk reported: #244 and #242