A visual REPL-like interface for ClojureScript that lets developers interactively test and display code examples in a browser.
Devcards is a ClojureScript library that provides a visual, REPL-like interface for interactively developing and testing code examples in a browser. It allows developers to create and edit *cards*—visual representations of code—that update live, offering a meta-application space separate from the main app to improve feedback and component design.
ClojureScript developers working on frontend applications who want an interactive, visual way to test components and code examples during development.
Developers choose Devcards because it offers a unique visual REPL experience that decouples component development from the main application, enabling faster iteration, better state management, and improved component independence through live editing and card-based organization.
Devcards aims to provide a visual REPL experience for ClojureScript
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Integrates seamlessly with lein-figwheel to enable real-time code changes and updates in the browser, providing immediate feedback on UI components as shown in the Sablono template example.
Encourages developing components in a meta-application separate from the main app, which starkly reveals environmental coupling and fosters more independent design, as detailed in the philosophy section.
Cards can be deployed as a standalone website, serving as a lasting lab for testing states and a reference for onboarding, QA, and future development, per the hosting instructions.
Configuring Devcards without lein-figwheel requires manual build options and UI startup, adding overhead compared to the integrated setup, as admitted in the 'Usage without Figwheel' section.
It only works with ClojureScript and relies on tools like Leiningen, making it unsuitable for projects using other languages or build systems, limiting its applicability.
Primarily a development tool, not designed for production use, which necessitates separate builds and configurations, potentially complicating deployment workflows.