NativeScript iOS Daily: Runtime Internals Get an Overhaul
Three merged or in-progress pull requests this cycle push the runtime toward better error visibility and a more maintainable core, led by a major libffi upgrade and a move to real JavaScript source files for built-in runtime code.
Duration: PT2M13S
Episode overview
This episode is a short developer briefing from NativeScript iOS Daily.
It explains recent repository work in plain language.
- Show: NativeScript iOS Daily
- Published: 2026-07-24T13:13:32Z
- Audio duration: PT2M13S
Transcript excerpt
This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.
Good day, and welcome to NativeScript iOS Daily for July 24th, 2026.
The clearest signal today: this is a maintainability and diagnostics cycle. The team is paying down long-standing technical debt in two of the runtime's oldest, hardest-to-touch corners.
First, foreign function interface handling. PR 408 replaces a 2019-era libffi fork with a current upstream version, adding support for vector types. Author Edusperoni notes this allows Objective-C exceptions to unwind properly through FFI closure trampolines into native try-catch blocks — closing out three linked…
Second, PR 411 tackles the embedded runtime JavaScript — roughly 26 kilobytes of logic that's lived as C++ string literals. It's being extracted into real, version-controlled JavaScript files, compiled at build time through a new js2c tool. That means readable diffs, real syntax highlighting, and easier review going…
The third theme is error clarity. PR 410, merged and captured in commit 164e752, fixes a case where a failing ES module — say, a reference error at module scope — used to surface as an opaque, multi-layered crash with no real message. Now the actual rejection reason and stack trace are reported instead of…
What…