@repokit/core 2.0.4 → 2.0.6

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/Cargo.lock CHANGED
@@ -169,7 +169,7 @@ checksum = "a96887878f22d7bad8a3b6dc5b7440e0ada9a245242924394987b21cf2210a4c"
169
169
 
170
170
  [[package]]
171
171
  name = "repokit"
172
- version = "2.0.4"
172
+ version = "2.0.6"
173
173
  dependencies = [
174
174
  "alphanumeric-sort",
175
175
  "colored",
package/Cargo.toml CHANGED
@@ -1,6 +1,6 @@
1
1
  [package]
2
2
  name = "repokit"
3
- version = "2.0.4"
3
+ version = "2.0.6"
4
4
  edition = "2024"
5
5
 
6
6
  [[bin]]
package/README.md CHANGED
@@ -81,7 +81,7 @@ repokit
81
81
 
82
82
  The CLI will list out its internal commands as well as any commands you registered in your config file.
83
83
 
84
- <img src="media/post-init.webp" alt="Help screen after initialization" />
84
+ <img src="media/post-init.webp" alt="Help screen after initialization" width="100%" />
85
85
 
86
86
  Next run:
87
87
 
@@ -134,7 +134,7 @@ repokit user-interface
134
134
  ```
135
135
 
136
136
  The CLI will list out your new tool's API's:
137
- <img src="media/new-command.webp" alt="Command definition" />
137
+ <img src="media/new-command.webp" alt="Command definition" width="100%" />
138
138
 
139
139
  To invoke any of them, run:
140
140
 
@@ -232,7 +232,7 @@ If your command needs to reason about the file system, keep this in mind.
232
232
 
233
233
  I worked in a codebase at Google that used just about every programming language in existence. Each team had their own methodology for exposing commands, scripts, and API's for their team's day-to-day development needs.
234
234
 
235
- Some teams used shell scripts, some used a tool called `bazel`, and some relied on good old `python ./path/to/my-script.py` or something similar.
235
+ Some teams used shell scripts, some used a tool called `bazel`, and some relied on good old `python ./path/to/my-script.py` (or something similar).
236
236
 
237
237
  For engineers new and old to onboard to new features, they were often left stuck combing through these undocumented scripts and tools - tracking down environment variables, positionals, and flags to get necessary commands to succeed.
238
238
 
@@ -1,4 +1,4 @@
1
- CURRENT_VERSION="2.0.4"
1
+ CURRENT_VERSION="2.0.6"
2
2
  CWD=$(pwd)
3
3
 
4
4
  REPLACEMENT="/node_modules"
@@ -120,7 +120,7 @@ impl Help {
120
120
  "{}{}{}",
121
121
  Logger::indent(Some(indentation.unwrap_or(6))),
122
122
  Logger::green(name.as_str()),
123
- Logger::gray(format!(": {}", description).as_str()),
123
+ Logger::gray(format!(" {}", description).as_str()),
124
124
  );
125
125
  }
126
126
  }
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@repokit/core",
3
- "version": "2.0.4",
3
+ "version": "2.0.6",
4
4
  "description": "A knowledgebase for your repository - wrapped in a CLI",
5
5
  "keywords": [
6
6
  "cli",
@@ -37,6 +37,7 @@
37
37
  "clean:ts": "tsx devserver/run.ts -c",
38
38
  "grant:exec": "chmod -R +x ./installation",
39
39
  "install:rust": "yarn build:rust && cargo install --path .",
40
+ "lint:all": "yarn lint:ts && yarn lint:rust",
40
41
  "lint:rust": "cargo clippy --fix --allow-dirty",
41
42
  "lint:ts": "yarn oxlint --type-aware --type-check --report-unused-disable-directives --fix && yarn oxfmt",
42
43
  "package:ts": "yarn lint:ts && yarn lint:rust && yarn build:ts",