ahmido
1fec9c6f9d
Some checks failed
Main Confidence / confidence (push) Failing after 45s
## Summary - introduce surface-aware compressed governance outcomes and reuse the shared truth/explanation seams for operator-first summaries - apply the compressed outcome hierarchy across baseline, evidence, review, review-pack, canonical review/evidence, and artifact-oriented operation-run surfaces - expand spec 214 fixtures and Pest coverage, and fix tenant-panel route assertions by generating explicit tenant-panel URLs in the affected Filament tests ## Validation - `cd apps/platform && ./vendor/bin/sail bin pint --dirty --format agent` - focused governance compression suite from `specs/214-governance-outcome-compression/quickstart.md` passed (`68` tests, `445` assertions) - `cd apps/platform && ./vendor/bin/sail artisan test --compact tests/Feature/Filament/InventoryItemResourceTest.php tests/Feature/Filament/BackupSetUiEnforcementTest.php tests/Feature/Filament/RestoreRunUiEnforcementTest.php` passed (`18` tests, `81` assertions) Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de> Reviewed-on: #253
74 lines
2.2 KiB
Plaintext
74 lines
2.2 KiB
Plaintext
# Command Shortcuts
|
|
|
|
Package managers that execute scripts from a `package.json` or `deno.(json|jsonc)` file can be shortened when in concurrently.<br/>
|
|
The following are supported:
|
|
|
|
| Syntax | Expands to |
|
|
| --------------- | --------------------- |
|
|
| `npm:<script>` | `npm run <script>` |
|
|
| `pnpm:<script>` | `pnpm run <script>` |
|
|
| `yarn:<script>` | `yarn run <script>` |
|
|
| `bun:<script>` | `bun run <script>` |
|
|
| `node:<script>` | `node --run <script>` |
|
|
| `deno:<script>` | `deno task <script>` |
|
|
|
|
> [!NOTE]
|
|
>
|
|
> `node --run` is only available from [Node 22 onwards](https://nodejs.org/en/blog/announcements/v22-release-announce#running-packagejson-scripts).
|
|
|
|
For example, given the following `package.json` contents:
|
|
|
|
```jsonc
|
|
{
|
|
// ...
|
|
"scripts": {
|
|
"lint:js": "...",
|
|
"lint:ts": "...",
|
|
"lint:fix:js": "...",
|
|
"lint:fix:ts": "...",
|
|
// ...
|
|
},
|
|
// ...
|
|
}
|
|
```
|
|
|
|
It's possible to run some of these with the following command line:
|
|
|
|
```bash
|
|
$ concurrently 'pnpm:lint:js'
|
|
# Is equivalent to
|
|
$ concurrently -n lint:js 'pnpm run lint:js'
|
|
```
|
|
|
|
Note that the command automatically receives a name equal to the script name.
|
|
|
|
If you have several scripts with similar name patterns, you can use the `*` wildcard to run all of them at once.<br/>
|
|
The spawned commands will receive names set to whatever the `*` wildcard matched.
|
|
|
|
```bash
|
|
$ concurrently 'npm:lint:fix:*'
|
|
# is equivalent to
|
|
$ concurrently -n js,ts 'npm run lint:fix:js' 'npm run lint:fix:ts'
|
|
```
|
|
|
|
If you specify a command name when using wildcards, it'll be a prefix of what the `*` wildcard matched:
|
|
|
|
```bash
|
|
$ concurrently -n fix: 'npm:lint:fix:*'
|
|
# is equivalent to
|
|
$ concurrently -n fix:js,fix:ts 'npm run lint:fix:js' 'npm run lint:fix:ts'
|
|
```
|
|
|
|
Filtering out commands matched by wildcard is also possible. Do this with by including `(!<some pattern>)` in the command line:
|
|
|
|
```bash
|
|
$ concurrently 'yarn:lint:*(!fix)'
|
|
# is equivalent to
|
|
$ concurrently -n js,ts 'yarn run lint:js' 'yarn run lint:ts'
|
|
```
|
|
|
|
> [!NOTE]
|
|
> If you use this syntax with double quotes (`"`), bash and other shells might fail
|
|
> parsing it. You'll need to escape the `!`, or use single quote (`'`) instead.<br/>
|
|
> See [here](https://serverfault.com/a/208266/160539) for more information.
|