You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The source mapping feature works well when each lua file has its own .lua.map file. However, when using the luaBundle feature of TypeScriptToLua or other tools that generate a single lua file with one .lua.map which points to many source files, the debugger seems to get breakpoints across different files mixed up, and often skips them. For example, if you have a breakpoint in a file like foo.ts in the love-ts test, but no breakpoint in main.ts, then the debugger will ignore the breakpoint in foo.ts and never break.
The text was updated successfully, but these errors were encountered:
The source mapping feature works well when each
lua
file has its own.lua.map
file. However, when using theluaBundle
feature of TypeScriptToLua or other tools that generate a single lua file with one.lua.map
which points to many source files, the debugger seems to get breakpoints across different files mixed up, and often skips them. For example, if you have a breakpoint in a file likefoo.ts
in thelove-ts
test, but no breakpoint inmain.ts
, then the debugger will ignore the breakpoint infoo.ts
and never break.The text was updated successfully, but these errors were encountered: