Referencing local packages by bare specifier changes behaviour

[Jamesernator]

Currently one can use workspaceRoot to allow for importing files from other directories, this works fairly well when using relative paths but breaks if using local npm dependencies and referencing via bare specifiers.

I have an example repository demonstrating the issue.

Essentially this works:

import ExampleElement from "../packages/example-element/ExampleElement.js";

But when having an entry in package.json for that package:

{
    "dependencies": {
        "example-element": "file:packages/example-element/"
    }
}

We cannot do:

import ExampleElement from "example-element/ExampleElement.js";

as one would expect, instead this throws an error:

[11:54:45] [snowpack] ! building files...
[11:54:45] [snowpack] Build Result Error: There was a problem with a file build result.
[11:54:45] [snowpack] Cannot find module 'example-element/ExampleElement.js' from '/home/jamesernator/Projects/snowpack-issue'

[taylorhadden]

+1 For this. I'm experiencing a very similar issue that essentially blocks my usage of snowpack.

[geordie2020]

For me it's also only working, if the import path is relative, not when it is absolute. No package.json entry involved.