Feedback about the solution and its configuration

[eytienne]

For the context, I was testing the fix that put in use user rollup plugins: #3123

Snowpack behaviour can be tricky, I seeked to only test config on one file to speed up reloads, and I tried everything I could think of but none worked. By example, excluding all then mouting my the file dirname and I got that:

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

Following the "knowEntrypoints" advice, I saw this:

[snowpack] + font-awesome/css/[email protected]
[snowpack] Successfully ran esinstall.
[snowpack] + font-awesome/css/[email protected] DONE
[snowpack] Ready!

...BUT it was NOT applying rollup plugins as with a package resulting from scanned non-excluded files.

I don't even tell you the pain with testOptions.files: https://www.snowpack.dev/reference/configuration#testoptions.files where I don't know if it is conditioned by config.mode == "test" or NODE_ENV so I try both then as none worked, I read the code ─ twice :'( ─ (https://github.com/snowpackjs/snowpack/blob/main/snowpack/src/scan-imports.ts#L285) to finally find out it was not that "Snowpack includes these files" but just avoids excluding them.

Finally, I was just looking for a common "include" option to test my config on a small perimeter. However, they are too much code paths resulting in confusing thoughts for users I would say.