NOTE: The project is currently in preview and it will change its name. You can give your suggestions about the name change here: https://github.com/warpy-ai/script/discussions/20

NOTE2: Most of the code in this project is written by a human, me. AI is used selectively to speed up repetitive tasks, generate initial drafts, and it wrote most of the documentation ( which will be reviewed and edited by a human more the project advances). Architecture, system design, and implementation decisions were hand-written, even more on wrong implementation/bugs. If you're against "AI Slop", consider move away from this project.

This week marks a major milestone for Script: we've officially begun Phase 4 - Self-Hosting Compiler. After completing Phase 3 (Language Completion), we're now taking the next step toward making Script a truly self-contained language that can compile itself. This post explores what self-hosting means, why it matters, and how we're building toward it.

This week, we added 10 standard library modules to Script in just 7 days. From path to math, from date to fs, we went from a minimal runtime to a production-ready standard library. This post shares the lessons we learned, the patterns we established, and the decisions we made along the way.

Script now has full async/await support, built on top of Tokio—Rust's production-grade async runtime. This post dives into how we implemented Promises, the await opcode, and bridged Rust's async world with Script's VM.

Script now has full ES module support with import and export statements, file-based resolution, SHA256 caching, and cross-module function calls. This post explains how we built it, the decisions we made, and what's coming next.