You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The build compiles TypeScript into the `dist/` folder and copies `package.json` there.
105
+
106
+
### Running the built CLI
107
+
108
+
You can run the built artifact directly from the `dist` folder:
109
+
110
+
```bash
111
+
node dist/content-cli.js -h
112
+
```
113
+
114
+
### Installing the local build globally
115
+
116
+
To use your local build as the global `content-cli` command:
117
+
118
+
```bash
119
+
cd dist
120
+
npm link
121
+
```
122
+
123
+
This creates a symbolic link in the global `node_modules` directory, allowing you to run `content-cli` from anywhere on your machine. To unlink later, run `npm unlink -g @celonis/content-cli`.
124
+
125
+
## Troubleshooting
126
+
127
+
### `Error: Cannot find module '...'`
128
+
129
+
If you see a `Cannot find module` error when running `content-cli`, dependencies may not be installed correctly:
130
+
131
+
-**Global install:** Try updating to the latest version: `npm install -g @celonis/content-cli@latest`.
132
+
-**Local development:** Run `yarn install` from the project root before building.
133
+
134
+
### `content-cli: command not found`
135
+
136
+
- Ensure Node.js is installed and on your `PATH` (`node -v`).
137
+
- If installed via `npm install -g`, check that npm's global `bin` directory is in your `PATH`. You can find it with `npm bin -g`.
138
+
- If using `npm link`, make sure you ran it from the `dist/` directory (not the project root).
139
+
140
+
### Node.js version errors
141
+
142
+
Content CLI requires Node.js `>=18.20.5`. If you see compatibility errors, upgrade your Node.js installation. We recommend using [nvm](https://github.com/nvm-sh/nvm) to manage Node.js versions:
0 commit comments