Support third party framework import statements

In frameworks like RoStrap, there is a custom “LoadLibrary” function. In RoStrap’s case, it eliminates the need for absolute paths between your code and handles replication of shared code in the background.

In a perfect world, it would be nice for import { something } from "Aurora" to compile to Resources:LoadLibrary("Aurora"), where “Aurora.ts” is the name of one of your own files.

Even if a compromise is required, it would be nice to support emitting import statements that are compatible with frameworks while not losing type information about the module.

In RoStrap’s case, relative file-based import statements should still use require, only the named module syntax should use Resources:LoadLibrary.

[evaera]

We decided that support for third party frameworks should live in modules, not the compiler. Adding support for each and every framework into the compiler would be a futile effort, but modules can and should be able to do everything that is necessary, such as dynamically generated imports via metatables + a .d.ts file.

[osyrisrblx]

@Dog2puppy This would be done by creating an npm module. I’ll post a guide for how to make these soon.