EDITOR: Cannot resolve import paths in some cases

[catloversg]

TypeScript support will be available on the stable version via #1216. In some cases, monaco cannot resolve the import paths. This is just a problem with the script editor UI. It does not affect anything else. It may be fixed by #1477, but I don't think that fix can be merged easily.

MRE:
lib.ts

export const multiply = (a: number, b: number) => a * b;

test.ts

import { multiply } from "/lib";

export async function main(ns: NS) {
  ns.print(`multiply: ${multiply(2, 3)}`);
}

Screenshot:

With this case (use an absolute path), the player can work around by using a relative path (./lib instead of /lib).

I'll use this issue to keep track of the problem and potential fixes. Other reports can be marked "duplicate" and linked back to here.

[d0sboots]

Yes, we should assume #1477 is dead in the water and steal pieces from it that are useful or mergeable.

[lucebac]

I've seen this error in the past as well when I updated the import resolution. However, I believe I wasn't able to fix this because from what I understand this is an edge case of the way we interact with and provide model data to monaco.