google / google/wireit

[FR] A couple of QoL Feature Requests

Open
#1,029 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
6.4k
Forks
128
Avg merge
4d 10h
Merged PRs (30d)
4

Description

I am putting them in one issue for cleanliness because some of them might not be worthwhile/feasible/within scope.
These are sleepless 04:00 thoughts, so I will tidy up and give examples later.

1. Allow configuration of the WireIt env vars in the package.json configuration, both package-wide and per script \
Maybe also via somewhere like `./.wireitrc.json`, `~/.wireitrc`
3. Also config of general env vars as above
4. Generate visualisation of graph for WireIt scripts
5. WireIt script aliases \
e.g. `push` as an alias for `deploy`
7. In VSCoode, when triggering `refactor` prompt, add wireit to dev-dependencies
8. `wireit cli` \
WireIt as a global install and `npx` command with CLI bin for commands such as:
1. `wireit init`: \
adds wireit as dev dependency to current package and creates an empty wireit config directive in the `package.json`
3. `wireit refactor` \
same as above but also converts all current scripts. possibly also parse npm `beforeX` and `afterX` lifecycle scripts.
5. `wireit deintegrate` \
:( opposite of above.
9. General detection of `npm` lifecycle scripts when calling refactor in vscode
10. When refactoring a script that is already just a `wireit` command where there is no wireit config for it, do not set `command` to `"wireit"`
- e.g.
- current:
- before:
```json
{
"scripts": {
"foo": "wireit"
}
}
```
- after:
```json
{
"scripts": {
"foo": "wireit"
},
"wireit": {
"foo": {
"command": "wireit"
}
}
```
- proposed:
- after:
```json
{
"scripts": {
"foo": "wireit"
},
"wireit": {
"foo": {
}
}
```

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.