Some Lua / CC projects makes use TypeScript rather then regular Lua but it gets traspiled to regular Lua using TypeScriptToLua. They do this for a better IDE experience and to use advance fetures like classes (which Lua does not nativly support without hacks).
It is possibile to import regular Lua files in such an envrionment however the IDE will complain about missing type definitions.
Whilst it is possible for the project to make their own type defitions for Basalt - it would be better if Basalt came with their own.
Furthermore, you can publish Basalt to NPM (which publishing Lua scripts is allowed) to make it easier for TSTL based projects to use.
You don't have to replace your existing Lua files with TypeScript - we just need type declaration files - actually you just need one basalt.d.ts file inside your release folder.
Some Lua / CC projects makes use TypeScript rather then regular Lua but it gets traspiled to regular Lua using TypeScriptToLua. They do this for a better IDE experience and to use advance fetures like classes (which Lua does not nativly support without hacks).
It is possibile to import regular Lua files in such an envrionment however the IDE will complain about missing type definitions.
Whilst it is possible for the project to make their own type defitions for Basalt - it would be better if Basalt came with their own.
Furthermore, you can publish Basalt to NPM (which publishing Lua scripts is allowed) to make it easier for TSTL based projects to use.
You don't have to replace your existing Lua files with TypeScript - we just need type declaration files - actually you just need one
basalt.d.tsfile inside yourreleasefolder.