How workflowbuildersdk/workflowbuilder works
Project type and purpose
• It contains four workspace packages:
• apps/frontend – a React + TypeScript SPA (exposed even as a Web Component).
• apps/frontend-e2e – end-to-end tests.
• apps/types – shared TypeScript definitions.
File structure
• Top-level config files (package.json, tsconfig.base.json, pnpm-workspace.yaml, CI/linters).
• apps/ directory with the four packages above.
• In apps/frontend:
• src/app/hooks – custom React hooks for layout, commands, theming, persistence.
• src/app/providers – React context providers (undo/redo, zoom, mouse, translation).
• src/app/i18n – i18next integration and locale files.
• src/app/plugins – plugin adapter code.
• public assets, global.css, Vite config, Dockerfile.
• apps/frontend-e2e uses a test framework (likely Playwright or Cypress) to drive the built frontend.
README for additional insights
• The Technical Overview confirms the four-package split and calls out the React frontend as the core.