jnc run
Runs a task or shell command inside the activated workspace environment. The command can be a predefined task from the manifest or an arbitrary executable found in the environment’sPATH.
The environment is automatically installed and updated before execution if needed. Tasks defined in the manifest can depend on other tasks and will be executed in the correct topological order.
If no task is provided, jnc run prints a list of all available tasks.
Alias: r
Usage
Arguments
| Argument | Description |
|---|---|
TASK | The task name(s) or shell command to run. Multiple tasks can be chained. |
Options
| Option | Description |
|---|---|
-e, --environment <ENV> | The environment to run the task in. |
-x, --executable | Execute the command as a raw executable, bypassing task resolution. Useful when a task name and an executable share the same name. |
--clean-env | Run with a clean environment, ignoring variables from the current shell. |
--skip-deps | Do not run the task’s depends-on dependencies. |
--templated | Enable template rendering for command arguments (e.g., {{ pixi.platform }}). |
-n, --dry-run | Print the command that would be run without executing it. |
Update Options
| Option | Description |
|---|---|
--frozen | Use the lockfile as-is, do not update it. |
--locked | Require the lockfile to be up-to-date, abort if not. |
--no-install | Do not install the environment before running. |
--as-is | Shorthand for --frozen --no-install. |
Global Options
| Option | Description |
|---|---|
-m, --manifest-path <PATH> | Path to pixi.toml, pyproject.toml, or the workspace directory. |