Simplify importing dependencies witin node_modules

[lrettig]

AS won't let me import from an external module. This does not work:

import { Foo } from "bar"

But this relative import does work:

import { Foo } from "./node_modules/bar"

[dcodeIO]

Yeah, there is no concept of external modules yet. When you import from "bar", that file is looked up within stdlib paths. You should be able to do this if you specify --lib someDir on compilation, with a bar.ts inside.

[lrettig]

Thanks, makes sense. Is there any plan to add module resolution? I want to offer an ewasm module on npm that people can simply npm install into their project. I suppose I can work around this using --lib for now.

[dcodeIO]

I fear that doing module resolution the same way as node will lead to issues with TS/AS dependencies becoming mixed up. One idea on Slack recently was to use a special asMain property in package.json, and if that's not present fall back to assembly/index.ts as the entry file. Wdyt?

[fcrick]

I'd really love to see this working. I feel like this is the missing piece that would let folks run wild. It would also make it possible to move implementations in std/assembly all out to external modules, where it belongs.

[DieMyst]

It is not possible for now to import library that has import another AS library.
As an example, I had to add one of node_modules dir to github project:
https://github.com/fluencelabs/signature-connector
And only after this, I could import this project to another properly.

Why this is important: there is no ecosystem and simple ways to create libs around AS language.
So, on every project developers cannot reuse another code.

[MaxGraey]

Already support

[9oelM]

It's not yet supported, right?

[MaxGraey]

It's already supported. Are you have any problem with that?

[9oelM]

Umm... yeah. you can refer to this issue: as2d/as2d#5
I think it's related to --lib or --path flag. Can you give me an example of how to use it?