Question 1

How to ignore node_modules in rerun?

Accepted Answer

Use the '-i' flag or JSON config to add 'node_modules' to the ignore list. For example, run 'rerun -i node_modules' or set 'ignore': ["node_modules"] in your JSON file to prevent restarts on changes in that directory.

Question 2

Rerun vs air: which is better for Go development?

Accepted Answer

Rerun offers more configuration granularity and Vagrant support, while air has a larger community and more built-in features. Choose Rerun if you need precise control or work with Vagrant; otherwise, air might offer better out-of-the-box experience.

Question 3

Can rerun watch .html files for template changes?

Accepted Answer

Yes, configure the 'suffixes' option to include '.html' or other extensions. In JSON, set 'suffixes': [".go", ".html"] to trigger restarts when HTML files are modified, as shown in the config examples.

Question 4

How to set up rerun with a JSON config file?

Accepted Answer

Create a JSON file with keys like 'ignore', 'args', and 'suffixes', then run 'rerun -c config.json'. Rerun also auto-loads '.rerun.json' in the project root, so you can skip the '-c' flag for default configs.

Question 5

Does rerun work on macOS?

Accepted Answer

Yes, Rerun has cross-platform support and works on macOS. Use environment variables in configs with '$VAR' syntax, as documented in the README for seamless integration on Unix-based systems.

Question 6

Why isn't rerun detecting my file changes?

Accepted Answer

Enable verbose mode with '-v' to see detailed logs and troubleshoot. If using Vagrant, install the notify-forwarder plugin and use '--attrib', as Rerun might not detect changes without it in virtualized environments.

rerun

What is rerun?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions