boltpkg / boltpkg/bolt

`bolt run` is not the same as `yarn run`

Open
#183 3 comments 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
2.4k
Forks
97
PR merge metrics
No merged PRs in 30d

Description

| Title | Description
| --------------------|------------
| Version | v0.20.7
| Type | Issue
| node | 10.7.0 (but also happened on Node 8)
| Operating System | macOS
| Short Description | `bolt run` is not equivalent to `yarn run`
| Detailed description|

We have a 'dev' script defined as `"dev": "node scripts/dev/index.js"`, and scripts like `"lint:css": "yarn dev lint:css",`. Running `yarn lint:css --bamboo` passes the `--bamboo` option all the way to the dev script, running `bolt lint:css --bamboo` loses this option somewhere.

```
› yarn run lint:css --bamboo
yarn run v1.9.2
$ yarn dev lint:css --bamboo
$ node scripts/dev/index.js lint:css --bamboo
Running stylelint --custom-formatter ./node_modules/stylelint-junit-formatter "./src/**/*.js" >test-reports/stylelint-css.xml
```

```
› bolt run lint:css --bamboo
⚡️ bolt v0.20.7 (node v10.7.0)
$ yarn dev lint:css
$ node scripts/dev/index.js lint:css
Running stylelint "./src/**/*.js"
```

It would be good if both commands were equivalent so that our users would need to know when to use `bolt` and when to use `yarn` and could just always use `bolt`.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.