When pulling down the latest code, there were snapshot failures due to the inclusion of an absolute path for virtual dependencies and a new version of webpack being pulled in which slightly changed its runtime.
It seems that the npm:webpack@^5.0.0 does not respect the version in package-lock.json with the default install command (though it does with npm ci).
We may want to consider switching webpack5 to webpack and then add a webpack4 alias that is pinned to the current 4.x release as that's getting less updates, but this PR does not do that.
When pulling down the latest code, there were snapshot failures due to the inclusion of an absolute path for virtual dependencies and a new version of webpack being pulled in which slightly changed its runtime.
It seems that the
npm:webpack@^5.0.0does not respect the version inpackage-lock.jsonwith the default install command (though it does withnpm ci).We may want to consider switching
webpack5towebpackand then add awebpack4alias that is pinned to the current 4.x release as that's getting less updates, but this PR does not do that.