Relative imports in SimpleModuleLoader fail to resolve about boa

[jedel1043]

Ah, that's easy to fix! We just need to add a path property to the Module struct (or possibly only to SourceTextModule, but I could see it being useful to set a synthetic module to a fake path), and have it being set at creation time.

Should probably be a good idea to also add this to Source, since it should be a pretty straightforward change. Then, we could expose a Referrer::path() -> Option<&Path> method for ease of use.

[jedel1043]

To clarify, the exact implementation steps would be:

1. Expose the path property of the Source type with a getter.
2. Modify ModuleRepr and source::Inner to have a path: PathBuf property, and set it on their respective parse methods from the path property of Source.
3. Add a new path method to Referrer that gets a reference to the path property of Source and Module.

[hansl]

So it would be the responsibility of the ModuleLoader to implement (or not) resolution of specifiers?

[jedel1043]

Yes, simply because the core engine shouldn't have a notion of a "filesystem", since that would break the sandboxing we have in place for it. Implementors of ModuleLoader can decide if they want to preserve the sandbox or if they want to allow filesystem calls.