exsync
An Elixir reloader that automatically recompiles code when files change, supporting path dependencies and custom callbacks.
What is exsync?
ExSync is an Elixir reloader that automatically recompiles code when files change during development. It monitors specified directories and file extensions, triggering recompilation without manual intervention, and supports custom callbacks after reloads.
Elixir developers working on applications who want to streamline their development workflow with automatic code reloading.
Developers choose ExSync for its simplicity, support for path dependencies without extra configuration, and extensibility through reload callbacks, making it a flexible tool for enhancing productivity.
Overview
Yet another elixir reloader.
Use Cases
Best For
- Elixir projects needing automatic recompilation during development
- Applications using path dependencies that require seamless reloading
- Teams wanting to reduce manual recompilation steps in their workflow
- Developers needing customizable file monitoring with exclusion patterns
- Projects requiring post-reload callbacks for custom logic
- Umbrella applications where reloading across apps is beneficial
Not Ideal For
- Production environments or deployment pipelines requiring automatic reloading
- Projects using non-Elixir languages or build systems without mix integration
- Teams preferring manual compilation for fine-grained control over build steps
- Developers on systems lacking FileSystem dependencies (e.g., some containerized setups)
Pros & Cons
Pros
Monitors file changes and triggers recompilation automatically, eliminating manual steps during development, as highlighted in the README for streamlining workflows.
Seamlessly recompiles :path dependencies without extra configuration, a key feature that simplifies working with local dependencies.
Allows customization via extensions, exclusions with regex, and additional directories, offering flexibility for diverse project needs as shown in the config examples.
Supports MFA callbacks after recompilation, enabling custom logic integration, which enhances extensibility beyond basic reloading.
Cons
Relies on the FileSystem library with platform-specific dependencies, which can complicate setup in environments where these are not readily available.
Designed solely for dev environments (via 'only: :dev' in deps), making it unsuitable for production or testing scenarios that might benefit from similar automation.
Requires application environment configuration for basic settings like exclusions or callbacks, which might be verbose for simple use cases compared to more integrated tools.
Frequently Asked Questions
Related Projects
AtomVMTiny Erlang VM
porcelainWork with external processes like a boss
hammerAn Elixir rate-limiter with pluggable backends
cubdbElixir embedded key/value database
Found a gem we're missing?
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.