Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More →
typescript-to-lua
Advanced tools
typescript-to-lua - npm Package Versions
Changelog
1.13.0
- Fixed alternate file extensions (other than .lua, if configured) breaking module resolution and emitted require statements.
- Added experimental support for
"luaLibImport": "require-minimal"configuration option. This will output a lualib bundle containing only the lualib functions used by your code. This might not work if you are including external tstl-generated Lua, for example from a npm package. - Added support for the "exports" field in package.json.
- Fixed some exceptions resulting from invalid language-extensions use.
- Fixed an exception when using compound assignment (like
+=) with array length.
Changelog
1.12.0
- Reworked how tstl detects and rewrites
requirestatements during dependency resolution. This should reduce the amount of false-positive matches of require statements: require statements in string literals or comments should no longer be detected by tstl. This means require statements in string literals or comments can survive the transpiler without causing a 'could not resolve lua sources' error or getting rewritten into nonsense. - Now using
math.modfor Lua 5.0 modulo operations.
Changelog
1.11.0
- [Breaking] Upgraded TypeScript to 4.9.
--tstlVerbosenow prints more resolver output when failing to resolve Lua sources.- Fixed a bug breaking default exported classes with unicode names
- Relaxed conditions for the always-true warning to false positives.
Changelog
1.10.0
- [Breaking] Upgraded TypeScript to 4.8.
- [Breaking] Changed how language-extensions are distributed, you should now put
"types": ["@typescript-to-lua/language-extensions"]in your tsconfig.json (instead of "typescript-to-lua/..."). - Added support for Lua 5.0, thanks for the effort @YoRyan!
- Added support for TypeScript 4.7 instantiation expressions.
- Fixed a bug causing some
requireuses not being recognized my module resolution, leading to missing files in the output.
Changelog
1.9.0
- Added a warning when trying to use a type in a condition that can never be false in Lua, such as numbers or strings. (Only when
strictNullChecksis enabled.) - Fixed some missing and misplaced errors when trying to reference LuaTable/LuaMap/LuaSet functions without calling them.
- Fixed a bug in the
get()type ofReadOnlyLuaMap. It is now typed the same asLuaMap, i.e. it can returnundefined. - Fixed an issue in bundling that could sometimes lead to invalid bundle entry requires.
- Added a warning when using
pathswithout specifyingbaseUrl. - Fixed exception while checking for standard library types.