typescript-to-lua
Advanced tools
Changelog
1.2.0
myArray?.forEach()
.delete
behavior that was different in Lua compared to JS.Under the hood:
Changelog
1.1.0
React.createElement
now requires a self parameter, so remove @noSelf
, this: void
if necessary.switch
statement in all versions! (Before they were not supported in 5.1 and universal).string.prototype.replaceAll
and improved string.prototype.replace
implementation.noResolvePaths
tsconfig option to disable module resolution for environment-provided modules.void(0)
or void(ignoreThisReturnValue())
.$vararg
language extension can be used to access CLI arguments, now also in bundles.baseUrl
and relative imports.sourceMapTraceback: true
not working correctly for bundles..then
calls on already-resolved or already-rejected promises would cause some callbacks to not fire while they should.Changelog
1.0.0
/* @tupleReturn */
has been removed and will no longer have any effect. You will get an error if you try ot use it or if you use declarations that use it.Promise
class.async
and await
using coroutines.<directory>/init.lua
files for require("<directory>")
.Changelog
0.42.0
/** @tupleReturn */
is now deprecated, and will be removed next release. If you are still using it, please upgrade to the LuaMultiReturn language extension.baseUrl
configuration key for module resolution.A large list of bugfixes:
@noResolution
in library packages losing their NoResolution tag, causing attempts to resolve them for package users.myObject.require()
or my_custom_require()
.Changelog
0.41.0
a?.b
, a?.[b]
and a?.()
."buildmode": "library"
) project.--tstlVerbose
CLI flag to help with diagnosing problems....
) was not correctly optimized.outDir
was specified.