4 Commits

Author	SHA1	Message	Date
Nathan Rajlich	781d64b737	Move SWC playground to client-side WASM and add Monaco type intellisense (#1553) ... * Move SWC playground transform from server action to client-side WASM Create a new swc-playground-wasm crate that bundles swc_ecma_parser, swc_ecma_codegen, and the swc_workflow transform visitor into a single WASM binary via wasm-bindgen/wasm-pack. This runs the code transformation entirely in the browser, eliminating the server action round-trip and serverless function cold starts on every keystroke. - New packages/swc-playground-wasm Rust crate targeting wasm32-unknown-unknown - Exposes transform() and transformAll() functions via wasm-bindgen - Client loads WASM + JS glue from public/wasm/ as static assets - Removed @swc/core and @workflow/swc-plugin server-side dependencies - Removed serverExternalPackages/outputFileTracingIncludes Next.js config - Added WASM loading indicator and error state in the UI - Reduced transform debounce from 500ms to 300ms (no network latency) * Add missing extends key to swc-playground-wasm turbo.json * Fix build: ensure rustup is available for wasm32-unknown-unknown target The Vercel build environment has a system Rust without rustup, so the wasm32-unknown-unknown target can't be managed. Now the build script checks for rustup specifically (not just cargo) and installs it when missing, matching the pattern in swc-plugin-workflow/build.js. * Add workflow type definitions to Monaco editor for intellisense Auto-generate type declarations from built .d.ts files of workflow, @workflow/core, @workflow/errors, @workflow/world, and @workflow/utils packages. Register them with Monaco's TypeScript language service via addExtraLib() so imports like 'workflow' resolve with full types, eliminating red squiggles and enabling autocomplete/hover info. * Fix Monaco type resolution: register root index.d.ts for each package Monaco's NodeJs module resolution looks for index.d.ts at the package root, not just in dist/. Register the main entry .d.ts content at both paths (dist/ and root) so bare imports resolve with full type info. Also remove the 2307 diagnostic suppression so non-existent imports correctly show errors. * Fix Monaco tooltip overflow by enabling fixedOverflowWidgets * Fix hydration mismatch, Monaco type resolution paths, and WASM init warning - Fix hydration mismatch: gate Reset button disabled state on isHydrated so server and client render consistently during hydration - Fix Monaco types: use bare node_modules/ paths instead of file:/// URIs for addExtraLib, which is what Monaco's NodeJs resolver expects - Remove virtual package.json entries (Monaco doesn't use them) - Fix wasm-bindgen init deprecation: pass object { module_or_path } instead of bare string argument * Fix Monaco module resolution: set model URI to file:/// and match addExtraLib paths Monaco's TypeScript NodeJs resolver needs the editor model and the addExtraLib entries to share the same URI scheme. Set the input editor model path to file:///src/input.tsx and register all type declarations at file:///node_modules/... so resolution of bare imports like 'workflow' correctly finds the virtual node_modules. Also register a root index.d.ts for packages like @workflow/world that lack an explicit 'types' field in their package.json exports. * Use declare module ambient declarations for reliable Monaco type resolution Replace the virtual node_modules filesystem approach with declare module ambient declarations. This is the standard approach used by TypeScript Playground and StackBlitz — it works regardless of Monaco's internal URI scheme and module resolution quirks. The generation script now: - Registers all .d.ts files at file:///node_modules/<pkg>/dist/... paths - Generates a global ambient declarations file with declare module blocks that map bare import specifiers to their .d.ts entry points - Includes @workflow/serde and workflow sub-exports (api, errors, observability) - Supports configurable sub-export mappings per package * Inline types into declare module blocks for full Monaco type support Replace the export-from-file approach with fully inlined declare module blocks. The script now reads each .d.ts entry point, recursively inlines all relative imports, strips external import statements (resolved via other declare module blocks), and produces a single ambient declarations string. This correctly handles: - unique symbol exports (@workflow/serde) - cross-package re-exports (workflow re-exporting from @workflow/core) - JSDoc comments preserved for hover documentation - Sub-path exports (workflow/api, workflow/errors, workflow/observability) - Added @workflow/serde package * Add workspace packages as dependencies so Turbo builds their types The generate-monaco-types script reads .d.ts files from the built dist/ directories of workflow, @workflow/core, @workflow/errors, etc. On Vercel, Turbo only builds explicit dependencies — without these workspace references, the packages were never built and the dist/ directories didn't exist, resulting in 0 type modules generated. * Add @types/node declarations to Monaco editor Register all @types/node .d.ts files via addExtraLib so Node.js built-in modules (crypto, fs, path, etc.) are available in the playground editor with full type information. * Collect @types/node .d.ts files recursively to include subpath modules The previous non-recursive scan missed subdirectory files like fs/promises.d.ts, stream/web.d.ts, dns/promises.d.ts, etc., causing 'Cannot find module node:fs/promises' errors.	2026-03-30 18:17:53 +00:00
Nathan Rajlich	5d95abf941	fix(swc-plugin): closure variable detection for new expressions and module-level declarations (#1368) ... * fix(swc-plugin): closure variable detection for `new` expressions and module-level declarations Fix two SWC compiler plugin bugs related to closure variable detection: 1. Add Expr::New handling to ClosureVariableCollector so `new Class(...args)` properly captures both the callee and arguments as closure variables. 2. Exclude module-level declarations (functions, variables, classes) from closure variable detection, preventing over-capturing of identifiers that are already available in all bundles. This also allows DCE to properly remove step-only helpers and their imports from the workflow bundle. Fixes #1365 * fix(swc-plugin): handle additional expression/statement types in closure variable collector Expand closure variable detection to cover more AST patterns: Expressions: Seq (comma), Yield, OptChain, Prop::Shorthand, computed property keys, Prop::Assign defaults, Class (skip bodies) Statements: Throw, Try/Catch/Finally, Switch, ForIn, ForOf, DoWhile, Labeled Also fix existing Prop::Shorthand bug where object shorthand properties like { url } were not being collected as closure vars. Extend test fixture with cases for all newly handled patterns. Fix spec.md wording per review feedback. * fix(swc-plugin): preserve original step function bodies in enclosing functions In step mode, nested step functions were replaced with bare references to the hoisted copy (e.g., `return hoisted$fn;`). This broke direct calls because the hoisted copy uses `__private_getClosureVars()` which only works in workflow context. Now the original function body is preserved inline with just the directive stripped, so JavaScript's normal closure semantics work for direct calls. The hoisted copy with `__private_getClosureVars()` is still registered for workflow-driven execution. Fixes #1369 * fix(swc-plugin): restore metadata tracking for object property steps in step mode The previous commit accidentally removed the object_property_workflow_conversions tracking from the step mode path, causing __internal_workflows metadata to be stripped from step bundle output for object property step functions. * fix(swc-plugin): detect closure variables inside nested function/method bodies The closure variable collector was skipping nested function expressions, arrow functions, and method bodies entirely. This meant closure variables used deep inside inner functions (e.g., a variable used inside a ReadableStream's start() method) were not captured. Now the collector walks into nested function/arrow/method/getter/setter bodies while adding their parameters to the local var set, so only truly free variables from the outer step scope are captured. Also add ReadableStream, WritableStream, TransformStream, and other common Web API globals to the known globals list. * update changeset to include Bug 4 * fix(swc-plugin): handle TypeScript expression wrappers and class bodies in closure detection After comparing with Next.js's SWC plugin closure detection approach, identified and fixed remaining gaps: - TypeScript expression wrappers (as, satisfies, !, type assertions, const assertions, instantiation expressions) now traverse to the inner expression instead of being silently skipped - Class expressions and declarations now walk their body members (methods, properties, constructors, static blocks) to detect closure variables used inside them - Document all remaining safe-to-skip Expr variants (This, Lit, SuperProp, MetaProp, PrivateName, Invalid, JSX) * test: add fixture cases for TypeScript wrappers and class body closure detection * test: add TypeScript fixture for closure detection through TS expression wrappers Add a proper input.ts fixture that tests closure variable detection through real TypeScript syntax: `as`, `satisfies`, `!` (non-null), angle-bracket type assertions, `as const`, and generic function calls. Update test harness to support input.ts files by adding swc_ecma_parser dev-dependency and auto-detecting TypeScript syntax from file extension. Remove the incorrectly placed TypeScript-related test cases from the JS fixture (they were using plain JS syntax, not actual TS wrappers).	2026-03-16 23:04:36 +00:00
JJ Kasper	ac7997b855	Update to latest swc/core and preserve JSX (#507)	2025-12-03 11:29:27 -08:00
Gal Schlezinger	4ca9a3edbd	Introducing Workflow DevKit ... build durable, resilient, and observable workflows. Co-authored-by: Nathan Rajlich <n@n8.io> Co-authored-by: Pranay Prakash <pranay.gp@gmail.com> Co-authored-by: Adrian <me@adriandlam.com> Co-authored-by: JJ Kasper <jj@jjsweb.site> Co-authored-by: Vercel Release Bot <88769842+vercel-release-bot@users.noreply.github.com> Co-authored-by: Peter Wielander <mittgfu@gmail.com> Co-authored-by: Hayden Bleasel <hello@haydenbleasel.com> Co-authored-by: Gal Schlezinger <gal@spitfire.co.il> Co-authored-by: Manuel Muñoz Solera <mamuso@mamuso.net> Co-authored-by: Garrett <garrett.tolbert@vercel.com> Co-authored-by: Lars Grammel <lars.grammel@gmail.com> Co-authored-by: Pooya Parsa <pyapar@gmail.com> Co-authored-by: Tom Dale <tom@tomdale.net> Co-authored-by: Vishal Yathish <135551666+visyat@users.noreply.github.com> Co-authored-by: josh <144584931+dancer@users.noreply.github.com>	2025-10-23 12:07:52 +03:00