Add support for emitting .luau files
#2
Conversation
src/PathTranslator.ts
Outdated
| @@ -193,7 +209,7 @@ export class PathTranslator { | |||
| pathInfo.fileName = INIT_NAME; | |||
| } | |||
|
|
|||
| pathInfo.exts.push(LUA_EXT); // push .lua | |||
| pathInfo.exts.push(this.getLuauExt()); // push .luau | |||
There was a problem hiding this comment.
This is not backwards compatible. Packages that still use .lua would not be resolved correctly.
There was a problem hiding this comment.
I believe it is.
getImportPath() is only ever used "virtually". This is because it needs to understand files which don't exist yet (i.e. outDir hasn't been created).
The result is passed into RojoResolver to figure out the RbxPath of the file without ever looking at the filesystem itself.
There was a problem hiding this comment.
A realization I had while writing this:
RojoResolver stores references to .lua file paths exactly if a $path points to a .lua file. Will need to find a solution here.
I don't think we should. This feels a bit too magic. The compiler should just copy your non-compiled files as-is. |
Depends on: - roblox-ts/path-translator#2 - roblox-ts/rojo-resolver#496 Allows for both emitting .luau files to `outDir` and importing packages contain `.luau` files (or `.lua` for backwards compatibility). Unit tests pass with the above two PR branches installed locally.
Temporarily behind a flag because the compiler will have a
--luauflag which defaults to true. Users will be able to do--luau=falseif emitting.luaufiles breaks their workflows.Fixes #1