Cached package version doesn’t match the one requested

[AkimaLunar]

Hey, all 👋 I am porting an app from Webpack to Snowball and getting these errors in the dev server on page request.

Question: Does anyone know what could be a reason for Snowball to request a version of a package that differs from a cached version? These packages are higher in the dep tree, not direct dependencies, if that matters. Could this be related to ESM support in those packages in some way?

There are also unscannable packages warnings that correspond to these package mismatches.

[17:47:54] [snowpack] @fluentui/react-window-provider: Unscannable package import found.
Snowpack scans source files for package imports at startup, and on every change.
But, sometimes an import gets added during the build process, invisible to our file scanner.
We'll prepare this package for you now, but should add "@fluentui/react-window-provider" to "knownEntrypoints"

[17:47:54] [snowpack] @fluentui/react-window-provider: Unscannable package import found.tup.
Snowpack scans source files for package imports at startup, and on every change.
But, sometimes an import gets added during the build process, invisible to our file scanner.
We'll prepare this package for you now, but should add "@fluentui/react-window-provider" to "knownEntrypoints"
in your config file so that this gets prepared with the rest of your imports during startup. (x2)

The (x2) makes me think that maybe there were supposed to be two versions of the same package? My guess.

---

Update:

Upon further inspection, it definitely seems like there should have been two versions of that package. I can find both "@fluentui/react-window-provider": "^2.1.6" and "@fluentui/react-window-provider": "^1.0.2" in package-lock.json.