A customizable, dependency-free sequential workflow designer component for building flow-based programming and automation applications.
Sequential Workflow Designer is a pure TypeScript library that provides a generic, configurable component for creating visual workflow builders and graphical programming interfaces. It uses SVG for rendering and stores definitions as JSON, making it suitable for a wide range of applications from automation tools to no-code platforms.
Web developers building visual workflow editors, automation tools, or no-code/low-code platforms who need a customizable, engine-agnostic component. It specifically targets those using Angular, React, or Svelte frameworks.
Developers choose this library because it has no external dependencies, is fully generic and not tied to any specific workflow engine, and offers extensive customization options for toolboxes, editors, and step behavior. Its pure TypeScript implementation and framework integrations provide flexibility and ease of integration.
Customizable no-code component for building flow-based programming applications or workflow automation. 0 external dependencies. Check out https://nocode-js.com
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Pure TypeScript implementation with zero external libraries reduces bundle size and avoids compatibility issues, as highlighted in the README's 'No External Dependencies' feature.
Not tied to any workflow engine, allowing adaptation for various use cases from automation tools to no-code platforms, with definitions stored as JSON for easy integration.
Includes official integrations for Angular, React, and Svelte, demonstrated through live demos, easing adoption in modern web development stacks.
Highly configurable with providers for toolboxes, editors, and step behaviors, as shown in the configuration example for drag-and-drop rules and validation.
Advanced functionality like copy-paste, folders, and grid view is only available in the pro version, creating a feature gap that may require upgrading for complex use cases.
Setting up requires significant custom code for step editors and validators, as evidenced by the need to implement providers like stepEditorProvider and validator in the configuration.
Purely a visual designer; users must integrate it with a separate engine like Sequential Workflow Machine for workflow runtime, adding development effort.