1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87

//! # Hammer
//! 
//! Hammer is a no-config cli tool for running concurrent tasks with monorepo support.
//! Monorepo tooling *should* be as simple as it can. Unfortunately, the current tooling is overly 
//! complex and can lead to a lot of time spent configuring and debugging, when you should be 
//! worried about writing your code.
//! 
//! You can think of Hammer as a lightweight alternative for turborepo. Currently, it only
//! supports JS/TS projects. In the future it could expand and have a larger number of languages
//! supported.
//! 
//! ### The `hammer` bin
//! 
//! The `hammer` binary is hammer's CLI. It aims to be as simple as it can get.
//! 
//! Syntax:
//! ```bash
//! hammer <SCRIPT> [OPTS]
//! ```
//! 
//! Example:
//! 
//! ```bash
//! hammer dev
//! ```
//! *Runs all the workspaces projects "hammer:dev" scripts.*
//! 
//! #### Disabling the prefix
//! 
//! By default, hammer will look up for all the scripts containing the prefix `hammer:` in package.json,
//! thus making it easy to gradually adopt the tool and run only the scripts you want using it.
//! If you don't want this, just use the `--no-prefix` flag and hammer will look for the `dev` script directly:
//! 
//! ```bash
//! hammer dev --no-prefix
//! ``` 
//! *Runs all workspace projects "dev" scripts.*
//! 
//! **alias**: -n
//! 
//! #### Filtering
//! 
//! You can filter which projects should be targeted by hammer:
//! 
//! ```bash
//! hammer dev --filter web
//! ```
//! *Will only run the dev script of the project that contains a package.json with the "name" being "web"* 
//! 
//! **alias**: -f
//! 
//! #### Environment variables
//! 
//! By default, hammer will load the root .env file and inject all of its variables in every child
//! process that it starts. You can also pass variables via the command line, and they will override system
//! variables or root .env variables. This is really useful for changing some environment in a testing script,
//! for example:
//! 
//! ```bash
//! hammer test --env NODE_ENV:TESTING
//! ```
//! 
//! *Will run all workspaces "hammer:test" scripts and inject a environment variable NODE_ENV=TESTING*
//! 
//! **alias**: -e
//! 
//! I recommend setting up some scripts in the root package.json so it becomes easy to have these separate
//! environments:
//! 
//! ```json
//! {
//!     ...
//!     "scripts": {
//!         "dev": "hammer dev",
//!         "test": "hammer test -e NODE_ENV:TESTING"
//!     },
//!     ...
//! }
//! ```
//! *Easy to run with `pnpm dev`, `pnpm test`*

pub mod fs_checks;
pub mod npm_process;
pub mod package_json;
pub mod tasks;
pub mod errors;
pub mod args;