chore: bump the ts and csharp wasm parsers to 1.880.1
Merged
RU
1d ago+16+16+01234567890123456789-16-16-01234567890123456789
Summary
Pins the newly published windmill-parser-wasm-ts and windmill-parser-wasm-csharp 1.880.1 in the frontend and the CLI, so two merged parser changes reach users:
- #12515: a TypeScript JSDoc
@paramfills an empty argument description, in the editor and inwmill generate-metadata. - #10185: a C# parameter with a default value is optional.
Both packages were built from main at 1.880.1 and published to npm.
Changes
frontend/package.jsonandfrontend/package-lock.json:windmill-parser-wasm-ts1.695.0 ā 1.880.1,windmill-parser-wasm-csharp1.510.1 ā 1.880.1. The lockfile changes only those two entries (version, tarball URL and the integrity npm serves).cli/package.jsonandcli/bun.lock: the same two bumps.
Test plan
-
npm ciinfrontend/installs 1.880.1 from the lockfile, andbun install --frozen-lockfiledoes the same incli/. - Script editor, frontend from this branch against a local backend: a Bun script with
@param name Who to greetand@param {number} times - How many timesshows both descriptions in the run form (screenshot below). -
wmill generate-metadatafrom this branch's CLI:- the same TS script gets
description: Who to greetanddescription: How many times; - a C#
Main(int a, int b = 3)getsbwith default 3 and onlyarequired.
- the same TS script gets
Screenshots
The editor with the new TS parser: the JSDoc @param text shows as each argument's description.

š¤ Generated with Claude Code
Summary by cubic
Bumps windmill-parser-wasm-ts and windmill-parser-wasm-csharp to 1.880.1 in the frontend and CLI so two parser fixes reach users.
- A TypeScript JSDoc
@paramnow fills an empty argument description in the editor and inwmill generate-metadata. - A C# parameter with a default value is now treated as optional.