A build tool for PureScript projects that automates compilation, bundling, testing, and development workflows.
Pulp is a build tool and task runner for PureScript projects. It provides a command-line interface to automate common development workflows such as compiling PureScript code, running tests, generating documentation, and bundling JavaScript for browsers. It acts as a frontend to the PureScript compiler (purs) and integrates with tools like Browserify for dependency management.
PureScript developers who want a streamlined, convention-based tool for building, testing, and managing PureScript applications and libraries without manual configuration.
Pulp reduces the complexity of PureScript project setup and maintenance by offering a unified, intuitive CLI for all major development tasks, with sensible defaults and support for both Bower and psc-package dependency managers.
A build tool for PureScript projects
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Pulp's `pulp init` command instantly sets up a standard PureScript project with src/ and test/ directories, as shown in the README's getting started example.
It provides a single CLI for compiling, testing, and bundling PureScript code, seamlessly integrating with the PureScript compiler and tools like Browserify for CommonJS dependencies.
Includes a REPL launcher (`pulp repl`) and a basic development server with live recompilation (`pulp server`), streamlining workflows for web app development.
Supports both Bower and psc-package for dependencies, allowing developers to choose based on project needs, as detailed in the Dependency Management section.
The built-in development server is minimal and lacks advanced features like hot module replacement, prompting the README to recommend Webpack with purs-loader for more complex needs.
Pulp is tied to Bower or psc-package, which may not align with npm-centric workflows, and publishing packages requires additional setup with spago, as noted in the Releasing Packages section.
For non-standard or highly customized build processes, the README admits that generic tools like webpack or gulp are better suited, indicating Pulp's convention-over-configuration approach can be restrictive.