Package "base/*" not found.

[winkler1]

[snowpack] Package "base/*" not found. Have you installed it? 

Getting hung up on installing deps. The only usage of "base/*" I can find is in a .scss file. But it does not show up in the list of scanned files.

I've tried:

• I've got the snowpack-plugin-sass plugin
• clearing cache with snowpack dev --reload --verbose
• Renaming the .scss file to .txt
• 2.18.1 and @next

Where could this be coming from? Any ideas how to get past it?

[winkler1]

Found it, via this very high-tech method :) - in a compiled public/assets .scss file.

[FredKSchott]

See this comment: #1750 (comment)

This is expected behavior in Snowpack, where we treat @import 'foo' as a package import, and @import './foo' as a relative import. We're keeping an eye out for how much confusion this causes in apps, and may want to add an "opt-out" flag to support @import 'foo' as a relative import.

[segovia94]

I spent several frustrating hours trying to figure out why a similar error Package "variables" not found. Have you installed it? was happening (ironically it worked in "build" but not "dev"). It never occurred to me that I needed to change @import 'variables' to @import './variables' in a scss file. Although it was a super simple change for me to make, realizing that was the problem was very unintuitive since that format has been the standard for writing scss for over a decade. I would recommend considering allowing this simply to help avoid a ton of confusion for people trying to move over from other platforms or who look to official Sass documentation which would give them the assumption it is possible.

[segovia94]

In my case I'm not doing the import from a JS file. It is being done from another sass file. I'm not doing any JS stuff. Perhaps this limitation could be documented on the main @snowpack/plugin-sass page? That's the first place I looked when I kept getting errors.