Script Library System
Developers can import reusable `.wslib` modules directly into scripts.
A dedicated `LibraryLoader` resolves imports from local paths and standard APPDATA locations, while enforcing that library files only expose reusable function definitions with no dangerous top-level execution.
WinScript now supports real code sharing without giving up runtime safety.
Installable Command-Line Interface
WinScript now ships as a standard CLI package for execution, validation, and discovery.
Running `winscript script.ws` executes a file, while flags like `--validate`, `--apps`, and `--commands Chrome` make the runtime inspectable. CLI arguments also flow into scripts dynamically as `$1`, `$2`, and onward.
The language can now plug into local workflows, demos, and automation pipelines cleanly.
Interactive REPL Shell
A colorful, stateful terminal interface now supports live-coding WinScript.
Invoking `winscript` with no file opens a REPL with multi-line awareness, persistent variables and functions, history, and environment commands such as `:vars`, `:funcs`, `:clear`, and `:load <file>`.
Learning, debugging, and iterating on scripts is dramatically faster.
Microsoft Excel COM Integration
WinScript now includes the official v2-style COM path for Excel automation.
Natural commands like setting a cell value map directly onto `pywin32` COM methods, and the upgraded backend uses nested context routing so `tell Excel` and nested sheet scopes track the correct COM object stack under the hood.
Excel automation feels natural in the language while still routing correctly through COM internals.
VS Code Extension and Language Server
WinScript now has editor-grade tooling for writing and inspecting scripts.
The TypeScript extension and Python `pygls` server add syntax highlighting, live diagnostics, app-aware autocomplete after `tell`, and hover documentation pulled dynamically from `.wsdict` files.
WinScript now behaves like a serious language inside the editor, not just a script format.