plugin-sass resolves imports differently in dev and build, making dev fail

[Snugug]

Found this problem while trying to troubleshoot #2090. It appears that @snowpack/plugin-sass, when doing a build, is able to correctly find relative files (@import 'components/foo' instead of @import './components/foo') and is able to make use of Sass Load Paths to find files in other places, but during dev, both fail inside of esinstall(esinstall/lib/index.js:159:15). My assumption is that it's attempting to look up the an installed Node module components and the file foo within there instead of handling the import through Sass, and thus failing. I think my other discussion topic, supporting aliases in Sass files, may solve this, but I'm not sure if it'll solve it for both dev and build, or only fix it for dev and then break build because it does seem like there are two different paths happening.

[segovia94]

I found that in dev only @import './components/foo' will work. @import 'components/foo' fails for me. Both seem to work when doing a build.