NativeScript iOS Daily: Web Standards Land, Memory Safety Follows
Two major WHATWG APIs — structured clone and the performance timeline — merged into the runtime, and both immediately surfaced a native memory-safety bug that's now fixed, alongside new guardrails to catch similar issues earlier.
Duration: PT2M20S
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-08-11T13:16:02Z
- Audio duration: PT2M20S
Transcript excerpt
This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.
Good morning. It's August 11th, and today's story is about closing the gap between NativeScript's runtime and modern web standards — and the cleanup that came with it.
The headline is two spec-shaped APIs landing back to back. PR 431 brings structuredClone to both main and worker isolates, using V8's value serializer under the hood to support real HTML structured clone semantics, including ArrayBuffer transfer. PR 430 replaces the old bare performance object with a full…
That care paid off. Exercising these new APIs exposed a latent use-after-free: constructing an object from a raw pointer was over-releasing memory it never owned. PR 432 fixes it, and a same-day follow-up commit goes further, adding a configurable policy for touching released native objects. Instead of silent…
Supporting this, a new ns:runtime builtin module ships with TypeScript declarations, so setConfig and getConfig for this policy are typed and documented alongside the runtime's other ambient modules.
Two smaller but practical items: PR 433 fixes metadata generation for Mac Catalyst builds, addressing a missing deployment target crash. And three commits tightened the git hooks — lint-staged failures no longer…
Wha…