Unscannable package import found

[jfrancos]

Getting this warning, re: dependencies of a linked (npm link) npm module.

clsx: 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 "clsx" to "knownEntrypoints"
in your config file so that this gets prepared with the rest of your imports during startup.

I'd initially gotten a different warning, suggesting that I set a workspaceRoot, which I have done. Now I'm getting this new (above) warning, but the webpage seems to be functioning correctly.

If I publish the linked npm and install it normally, I don't see the above warnings.

Question: To test out my own dependencies via npm link, do I really need to set workspaceRoot plus add each of my linked dependency's dependencies to knownEntryPoints? Or is there something else that I'm doing wrong, perhaps in the rollup config or package.json of the linked dependency?

[motzyball]

Did you have any luck resolving this? What version of Snowpack are you using? We are running into the same issue, and it's blocking us from upgrading from 3.0.13 to 3.6.2.

[cmditch]

Seeing this same issue as well on v3.3.6.

I'm using yarn workspaces fwiw.

Update: The issue seems to come about in v3.3.0 as v3.2.2 does not produce this error.

[leesiongchan]

Having the same issue, do we have a solution yet?

[jithyan]

Having the same issue when I installed styled-components to my Snowpack React project. Downgrading to 3.2.2 fixed the issue.
Using Yarn 3 workspaces with pnp.

[rondonjon]

Same problem here.
Error vanished after downgrade; thanks for pointing this out @cmditch

[philip-peterson]

It looks as though this issue may have been introduced in "Streaming Package Imports v2" by @FredKSchott