@difflab/difflab-cli 0.12.0 → 0.13.0
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/README.md +6 -6
- package/dist/index.js +89 -25
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -66,7 +66,7 @@ difflab-cli templates list
|
|
|
66
66
|
difflab-cli templates scaffold spec-driven-plan docs/plans first-plan.md --cwd /absolute/project/path
|
|
67
67
|
```
|
|
68
68
|
|
|
69
|
-
The CLI defaults `--cwd` to its current directory. The MCP server exposes `template_list({})` and `scaffold({"name":"spec-driven-plan","cwd":"/absolute/project/path","path":"docs/plans","filename":"first-plan.md"})`. Both interfaces take a hyphenated template name, a relative destination **directory** (`path`, or `.` for `cwd`), and a separate **filename**. MCP always requires an absolute existing `cwd`. Missing destination directories are created. Available names: `spec-driven-plan`, `software-architecture-design`, `architecture-decision-record`, `product-requirements-document`, `agents`, `code-review`, `code-review-rubric`, `planning-intent`, `ui-component-architecture`, `pull-request-description` (adapted from Diffpi's PR template), `flow-definition`, `flow-instance`, `exploration-summary`, `exploration-research`, `exploration-proposal`,
|
|
69
|
+
The CLI defaults `--cwd` to its current directory. The MCP server exposes `template_list({})` and `scaffold({"name":"spec-driven-plan","cwd":"/absolute/project/path","path":"docs/plans","filename":"first-plan.md"})`. Both interfaces take a hyphenated template name, a relative destination **directory** (`path`, or `.` for `cwd`), and a separate **filename**. MCP always requires an absolute existing `cwd`. Missing destination directories are created. Available names: `spec-driven-plan`, `software-architecture-design`, `architecture-decision-record`, `product-requirements-document`, `agents`, `code-review`, `code-review-rubric`, `planning-intent`, `ui-component-architecture`, `pull-request-description` (adapted from Diffpi's PR template), `flow-definition`, `flow-instance`, `exploration-summary`, `exploration-research`, `exploration-proposal`, `poc-readme`, `hook-definition`, and `task`.
|
|
70
70
|
|
|
71
71
|
Reviews scaffold `code-review` as `REVIEW.md` and `code-review-rubric` as `rubric.yaml` in `.difflab/reviews/YYMMDD-name`. The installed rubric is `~/.difflab/templates/code-review-rubric.yaml`. Fill its criterion results during the review. File-scoped criteria require a path-tagged result for every changed source file. Function findings can include `file:line` locations. Evidence guidance and review instructions stay in the review skill, outside the lean YAML template.
|
|
72
72
|
|
|
@@ -74,15 +74,15 @@ Use `difflab-cli templates scaffold agents . AGENTS.md --cwd /absolute/project/p
|
|
|
74
74
|
|
|
75
75
|
On first use, missing bundled templates and filled examples are copied to `~/.difflab/templates` and `~/.difflab/templates/examples`. Edit the installed templates to customize future documents. Later runs add missing files but never replace existing ones, even after an upgrade. Examples are for reference, not selectable templates. Copying is literal: prompts and placeholders are not substituted. An unknown name, missing or invalid source, unsafe path, symlink, or existing destination causes an error; destination files are never overwritten. The target directory must remain inside `cwd` and the filename must be a single file name without separators. The one symlink exception is an initialized repository's `.difflab` link to its own user project store: `templates scaffold spec-driven-plan .difflab/plans/YYMMDD-name PLAN.md --cwd /absolute/repo` works in Git worktrees as well. To restore a bundled default, move your installed copy aside before listing again.
|
|
76
76
|
|
|
77
|
-
The portable `skills/difflab-plan`, `skills/difflab-review`, `skills/difflab-flow`, `skills/difflab-explore`, `skills/difflab-adr`, and `skills/difflab-poc` directories contain natural-language agent workflows for these templates. Install each skill in your client's Agent Skills directory. The MCP-only `log_append({"path":"/absolute/physical/project-store/plans/YYMMDD-name/logs.txt","message":"Phase started"})` tool creates an append-only progress log on first use; pass the physical path, not the `.difflab` symlink. There is no log CLI command.
|
|
77
|
+
The portable `skills/difflab-plan`, `skills/difflab-review`, `skills/difflab-flow`, `skills/difflab-hooks`, `skills/difflab-bdd`, `skills/difflab-writing-style`, `skills/difflab-explore`, `skills/difflab-adr`, and `skills/difflab-poc` directories contain natural-language agent workflows for these templates. Install each skill in your client's Agent Skills directory. The MCP-only `log_append({"path":"/absolute/physical/project-store/plans/YYMMDD-name/logs.txt","message":"Phase started"})` tool creates an append-only progress log on first use; pass the physical path, not the `.difflab` symlink. There is no log CLI command.
|
|
78
78
|
|
|
79
|
-
The [plan authoring guide](../../skills/difflab-plan/references/authoring.md) requires component/process/artifact visuals, compact interfaces, and a
|
|
79
|
+
The [plan authoring guide](../../skills/difflab-plan/references/authoring.md) applies `difflab-writing-style` and `difflab-bdd`. It requires component/process/artifact visuals, compact interfaces, and a directory-grouped `[M/A/D/R]` repo tree at the start of `Consequences`. Add a `Testing` subsection with a behavior flowchart and a matching `[M/A/D/R]` BDD test tree (`given`/`when`/`then`) mapped to existing suites or clearly labeled manual acceptance checks. Keep expected commit and green-CI gates, including for `plan go --commit`. That flag permits scoped commits. Push requires separate authorization. Write `N/A.` when infrastructure stays unchanged. Source examples live in the skill's `references/examples/` and are not CLI templates.
|
|
80
80
|
|
|
81
|
-
The [review rubric](../../skills/difflab-review/references/rubric.md) follows written `AGENTS.md` rules and
|
|
81
|
+
The [review rubric](../../skills/difflab-review/references/rubric.md) follows written `AGENTS.md` rules, `difflab-writing-style`, and `difflab-bdd`. Existing patterns are context, not requirements. Flag material antipatterns even when nearby code shares them. Refactor unclear code at the scope needed. Prefer outside-in tests (`e2e` > `integration` > `unit`) with human-verifiable outputs, and scrutinize test suites against the component's behavior flowchart to propose BDD tree reorganizations (`given`/`when`/`then` with hoisted fixtures) when needed. Untested private functions alone are not findings. Keep whole reports and comments short (one sentence per comment ideally) and use simple English; prefer code snippets or diagrams over walls of text. State findings once and keep detailed coverage in YAML. Omit nitpicks and minor optimizations. Explicit security/performance focuses deepen those audits.
|
|
82
82
|
|
|
83
|
-
Reviews
|
|
83
|
+
Reviews run in the current single agent without subagents or councils, keeping the selected frontier model regardless of vendor. `--adversarial` challenges all dimensions, including Security.
|
|
84
84
|
|
|
85
|
-
PR creation through `pr new`, create, open, or draft
|
|
85
|
+
PR creation through `pr new`, create, open, or draft always scaffolds and fills the installed `pull-request-description` template before creating the request, then reads the saved body back. `pr merge` watches post-merge CI and then invokes `~/.difflab/hooks/on-merge/HOOK.md` via `difflab-hooks` when registered. `pr merge --squash` selects a native forge squash merge before the operation. These are Agent Skill requests, not CLI subcommands.
|
|
86
86
|
|
|
87
87
|
For an upgrade, reinstall changed skills and reload the client. Back up and move aside only the installed templates/examples you want refreshed, then list templates again. For these changes, inspect `~/.difflab/templates/{spec-driven-plan,code-review}.md` and `examples/{plan-feature,plan-migration,review-change}.md`. Preserve customizations in backups and merge deliberately; never reset the whole directory. Older templates still work: skills add missing subsections to generated documents while preserving human content and existing phase completion state.
|
|
88
88
|
|
package/dist/index.js
CHANGED
|
@@ -48376,11 +48376,11 @@ var spec_driven_plan_default = `# [Outcome to deliver]
|
|
|
48376
48376
|
|
|
48377
48377
|
#### Repo Changes
|
|
48378
48378
|
|
|
48379
|
-
[Start with a
|
|
48379
|
+
[Start with a directory-grouped file tree using \`[M]\` modified, \`[A]\` added, \`[D]\` deleted, and \`[R]\` renamed before changed entries, including tests. Apply \`/difflab-writing-style\`. Identify the largest edits in a short note. Use real inspected paths and label proposed files. State when nothing is removed.]
|
|
48380
48380
|
|
|
48381
48381
|
#### Testing
|
|
48382
48382
|
|
|
48383
|
-
[
|
|
48383
|
+
[Apply \`/difflab-bdd\`. First draw a Mermaid behavior flowchart showing context branches, state transitions, and converging intermediate states from the user's or caller's perspective. Then map the flowchart into a nested \`[M/A/D/R]\` BDD test tree starting with \`given <context>\` (or optional \`describe\`/\`feature\`), nesting \`when\` -> \`then\` as needed, collapsing single-outcome branches to \`when <action>, then <outcome>\`, and hoisting shared fixtures. Prioritize \`e2e\` > \`integration\` > \`unit\` and specify human-verifiable outputs (screenshots, replays, file dumps, snapshots, JSON outputs, or debug logs). Label skill checks without a harness as \`manual acceptance\`.]
|
|
48384
48384
|
|
|
48385
48385
|
#### Trade-offs
|
|
48386
48386
|
|
|
@@ -48663,9 +48663,9 @@ var code_review_default = `# Review: [change or pull request]
|
|
|
48663
48663
|
- **Revision:** [commit or diff]
|
|
48664
48664
|
- **Intent:** [stated objective and source]
|
|
48665
48665
|
- **Reviewer:** [actual model identity]
|
|
48666
|
-
- **Mode:** [normal/adversarial
|
|
48666
|
+
- **Mode:** [normal/adversarial]
|
|
48667
48667
|
|
|
48668
|
-
[Use short sentences, active voice, and familiar words throughout. Keep section assessments brief and link to findings instead of repeating them. Keep detailed criterion coverage in rubric.yaml. Apply AGENTS.md and named style guides. Informal conventions are context, not requirements. Flag material antipatterns even when existing code shares them.]
|
|
48668
|
+
[Apply \`/difflab-writing-style\` and \`/difflab-bdd\`. Use short sentences, active voice, and familiar words throughout. Keep section assessments brief and link to findings instead of repeating them. Keep detailed criterion coverage in rubric.yaml. Apply AGENTS.md and named style guides. Informal conventions are context, not requirements. Flag material antipatterns even when existing code shares them.]
|
|
48669
48669
|
|
|
48670
48670
|
## Intent Delivery
|
|
48671
48671
|
|
|
@@ -48685,11 +48685,11 @@ var code_review_default = `# Review: [change or pull request]
|
|
|
48685
48685
|
|
|
48686
48686
|
## Reliability/Testing
|
|
48687
48687
|
|
|
48688
|
-
[
|
|
48688
|
+
[Apply \`/difflab-bdd\`. Analyze tests against the component's behavior flowchart (converging state branches, \`e2e\` > \`integration\` > \`unit\`, and human-verifiable outputs such as screenshots, replays, file dumps, snapshots, JSON outputs, or debug logs). Propose a concrete \`[M/A/D/R]\` BDD test tree reorganization (\`given\` -> \`when\` -> \`then\` with hoisted fixtures) when tests are flat, repeat downstream assertions across converged states, or obscure setup. Flag tests that only verify external dependencies rather than the repository's source behavior. Report executed checks and limits honestly.]
|
|
48689
48689
|
|
|
48690
48690
|
## Documentation
|
|
48691
48691
|
|
|
48692
|
-
[Flag walls of text, complex language, and text that only restates the implementation. Require concise
|
|
48692
|
+
[Apply \`/difflab-writing-style\`. Flag walls of text, complex language, and text that only restates the implementation. Require concise \`/simple-english\` explanations, domain terminology, and Mermaid/Draw.io diagrams or \`[M/A/D/R]\` trees when visuals communicate structure or flow better than prose.]
|
|
48693
48693
|
|
|
48694
48694
|
## Performance
|
|
48695
48695
|
|
|
@@ -48728,7 +48728,6 @@ State each finding once here, with its issue, effect, and useful fix. Use short,
|
|
|
48728
48728
|
|
|
48729
48729
|
- **Checks run:** [command and result.]
|
|
48730
48730
|
- **Not verified:** [environment, path, behavior, or applicable repository guidance that could not be checked.]
|
|
48731
|
-
- **Council:** [source reports, actual model identities, unresolved disagreements, or not selected.]
|
|
48732
48731
|
- **Rubric:** [path to the copied YAML rubric with completed criterion results. Disclose missing, pending, skipped, or stale results.]
|
|
48733
48732
|
`;
|
|
48734
48733
|
var init_code_review = () => {};
|
|
@@ -48744,8 +48743,6 @@ review:
|
|
|
48744
48743
|
changed_files: []
|
|
48745
48744
|
exclusions: []
|
|
48746
48745
|
reviewers: []
|
|
48747
|
-
model_inputs: []
|
|
48748
|
-
model_results: []
|
|
48749
48746
|
sections:
|
|
48750
48747
|
- title: Intent Delivery
|
|
48751
48748
|
criteria:
|
|
@@ -48846,7 +48843,7 @@ sections:
|
|
|
48846
48843
|
applies_when: Added or modified test files.
|
|
48847
48844
|
default_severity: consider
|
|
48848
48845
|
issue: >-
|
|
48849
|
-
Verbose unit tests pad coverage without proving real contracts, or
|
|
48846
|
+
Verbose unit tests pad coverage without proving real contracts, validate static asset or template structure, test the test apparatus itself, add regression tests for changes within the same changeset or for alpha projects without users, or only verify external dependency behavior.
|
|
48850
48847
|
results: []
|
|
48851
48848
|
- id: testing.names
|
|
48852
48849
|
scope: applicable-file
|
|
@@ -49247,6 +49244,46 @@ The \`base_commit\` is the full SHA of \`origin/main\` when this branch was crea
|
|
|
49247
49244
|
`;
|
|
49248
49245
|
var init_poc_readme = () => {};
|
|
49249
49246
|
|
|
49247
|
+
// templates/hook-definition.md
|
|
49248
|
+
var hook_definition_default = `# {{name}}
|
|
49249
|
+
|
|
49250
|
+
## Trigger
|
|
49251
|
+
|
|
49252
|
+
{{trigger}}
|
|
49253
|
+
|
|
49254
|
+
## Action
|
|
49255
|
+
|
|
49256
|
+
- Handler: \`{{handler}}\`
|
|
49257
|
+
- Requires: \`{{requires}}\`
|
|
49258
|
+
- Receives: \`{{receives}}\`
|
|
49259
|
+
|
|
49260
|
+
## Instructions
|
|
49261
|
+
|
|
49262
|
+
{{instructions}}
|
|
49263
|
+
`;
|
|
49264
|
+
var init_hook_definition = () => {};
|
|
49265
|
+
|
|
49266
|
+
// templates/task.md
|
|
49267
|
+
var task_default = `# [Task title]
|
|
49268
|
+
|
|
49269
|
+
## Objective
|
|
49270
|
+
|
|
49271
|
+
[One-line description of what needs to be done.]
|
|
49272
|
+
|
|
49273
|
+
## Context
|
|
49274
|
+
|
|
49275
|
+
[Relevant background written using \`/difflab-writing-style\`, kept as terse as possible. Link to relevant architecture docs instead of repeating them. For a bug ticket, describe only the observable issue and impact; do not propose a solution.]
|
|
49276
|
+
|
|
49277
|
+
## Technical Approach
|
|
49278
|
+
|
|
49279
|
+
_To be completed by the person doing the work._
|
|
49280
|
+
|
|
49281
|
+
## References
|
|
49282
|
+
|
|
49283
|
+
- [Relevant links to wikis, architecture docs, tickets, external resources, CI logs, or incident portals.]
|
|
49284
|
+
`;
|
|
49285
|
+
var init_task = () => {};
|
|
49286
|
+
|
|
49250
49287
|
// templates/examples/plan-feature.md
|
|
49251
49288
|
var plan_feature_default = `# Invite teammates to a project
|
|
49252
49289
|
|
|
@@ -49321,18 +49358,31 @@ src/
|
|
|
49321
49358
|
|
|
49322
49359
|
#### Testing
|
|
49323
49360
|
|
|
49361
|
+
\`\`\`mermaid
|
|
49362
|
+
flowchart TD
|
|
49363
|
+
Invite["Owner creates invitation"] --> Saved["State: Pending invitation saved<br/>(even if email queue fails)"]
|
|
49364
|
+
Saved --> Accept["Recipient submits token"]
|
|
49365
|
+
Accept --> Eligible{"Intended recipient,<br/>unused & unexpired?"}
|
|
49366
|
+
Eligible -->|"no"| Reject["Reject; membership & token unchanged"]
|
|
49367
|
+
Eligible -->|"yes"| Tx["Consume token + add member"]
|
|
49368
|
+
Tx -->|"tx fails"| Rollback["Roll back membership & token"]
|
|
49369
|
+
Tx -->|"tx succeeds"| Member["Return active membership"]
|
|
49370
|
+
\`\`\`
|
|
49371
|
+
|
|
49324
49372
|
\`\`\`text
|
|
49325
49373
|
src/
|
|
49326
49374
|
\u251C\u2500\u2500 http/
|
|
49327
49375
|
\u2502 \u2514\u2500\u2500 [A] invitations.spec.ts (application behavior)
|
|
49328
|
-
\u2502 \u2514\u2500\u2500 [A]
|
|
49329
|
-
\u2502 \u251C\u2500\u2500 [A]
|
|
49330
|
-
\u2502 \u2514\u2500\u2500 [A]
|
|
49376
|
+
\u2502 \u2514\u2500\u2500 [A] given a pending owner invitation
|
|
49377
|
+
\u2502 \u251C\u2500\u2500 [A] when the intended recipient accepts, then membership appears in JSON response
|
|
49378
|
+
\u2502 \u2514\u2500\u2500 [A] when a wrong recipient or expired/used token is submitted, then it rejects without changing state
|
|
49331
49379
|
\u2514\u2500\u2500 invitations/
|
|
49332
49380
|
\u2514\u2500\u2500 [A] service.spec.ts (public module behavior)
|
|
49333
|
-
\
|
|
49334
|
-
|
|
49335
|
-
\u2514\u2500\u2500 [A]
|
|
49381
|
+
\u251C\u2500\u2500 [A] given an email queue failure, when creating an invitation, then the saved invitation stays pending for retry
|
|
49382
|
+
\u2514\u2500\u2500 [A] given a pending invitation (converged state)
|
|
49383
|
+
\u2514\u2500\u2500 [A] when the database transaction fails during acceptance
|
|
49384
|
+
\u251C\u2500\u2500 [A] then membership changes roll back
|
|
49385
|
+
\u2514\u2500\u2500 [A] then the invitation token remains unconsumed
|
|
49336
49386
|
\`\`\`
|
|
49337
49387
|
|
|
49338
49388
|
Use BDD-style nested \`given\`/\`when\`/\`then\` scenarios in \`src/http/invitations.spec.ts\` and \`src/invitations/service.spec.ts\`. Reuse fixtures with a real test store.
|
|
@@ -49444,17 +49494,26 @@ src/
|
|
|
49444
49494
|
|
|
49445
49495
|
#### Testing
|
|
49446
49496
|
|
|
49497
|
+
\`\`\`mermaid
|
|
49498
|
+
flowchart TD
|
|
49499
|
+
Write["writeActivity(event)"] --> Dual["Dual write with stable ID"]
|
|
49500
|
+
Dual -->|"destination fails"| Retry["Retry failed store"] --> Parity["State: Both stores hold identical events"]
|
|
49501
|
+
Backfill["Interrupted backfill"] --> Resume["Resume batch"] --> Parity
|
|
49502
|
+
Parity --> Cutover["Switch read flag to new store"]
|
|
49503
|
+
Cutover --> ReadCutover["Page history across cutover"]
|
|
49504
|
+
Cutover --> Rollback["Write post-cutover events, then roll back flag"]
|
|
49505
|
+
\`\`\`
|
|
49506
|
+
|
|
49447
49507
|
\`\`\`text
|
|
49448
49508
|
src/
|
|
49449
49509
|
\u2514\u2500\u2500 activity/
|
|
49450
49510
|
\u251C\u2500\u2500 [M] history.spec.ts (application behavior)
|
|
49451
|
-
\u2502 \u2514\u2500\u2500 [A]
|
|
49452
|
-
\u2502 \u251C\u2500\u2500 [A]
|
|
49453
|
-
\u2502 \u2514\u2500\u2500 [A]
|
|
49511
|
+
\u2502 \u2514\u2500\u2500 [A] given dual-written stores at parity (converged state)
|
|
49512
|
+
\u2502 \u251C\u2500\u2500 [A] when paging history across reader cutover, then records and cursors match
|
|
49513
|
+
\u2502 \u2514\u2500\u2500 [A] when rolling back the reader after new writes, then no events are lost
|
|
49454
49514
|
\u2514\u2500\u2500 [A] migration.spec.ts (public module behavior)
|
|
49455
|
-
\
|
|
49456
|
-
|
|
49457
|
-
\u2514\u2500\u2500 [A] given an interrupted backfill, when resumed, then IDs and order match without duplicates
|
|
49515
|
+
\u251C\u2500\u2500 [A] given a failed destination write, when retried, then one logical event exists in each store
|
|
49516
|
+
\u2514\u2500\u2500 [A] given an interrupted backfill batch, when resumed, then IDs and order match without duplicates
|
|
49458
49517
|
\`\`\`
|
|
49459
49518
|
|
|
49460
49519
|
Use BDD-style nested \`given\`/\`when\`/\`then\` scenarios in \`src/activity/history.spec.ts\` for application behavior and \`src/activity/migration.spec.ts\` for public storage APIs with real test stores.
|
|
@@ -49747,7 +49806,6 @@ Address the two requests. No unrelated cleanup is needed.
|
|
|
49747
49806
|
- **Checks run:** None. This is a fictional example.
|
|
49748
49807
|
- **Not verified:** Execution and real repository guidance.
|
|
49749
49808
|
- **Rubric:** A real review links its filled rubric here.
|
|
49750
|
-
- **Council:** Not selected.
|
|
49751
49809
|
`;
|
|
49752
49810
|
var init_review_change = () => {};
|
|
49753
49811
|
|
|
@@ -49919,6 +49977,8 @@ var init_source = __esm(() => {
|
|
|
49919
49977
|
init_exploration_research();
|
|
49920
49978
|
init_exploration_proposal();
|
|
49921
49979
|
init_poc_readme();
|
|
49980
|
+
init_hook_definition();
|
|
49981
|
+
init_task();
|
|
49922
49982
|
init_plan_feature();
|
|
49923
49983
|
init_plan_migration();
|
|
49924
49984
|
init_design_service();
|
|
@@ -49946,6 +50006,8 @@ var init_source = __esm(() => {
|
|
|
49946
50006
|
"exploration-research.md": exploration_research_default,
|
|
49947
50007
|
"exploration-proposal.md": exploration_proposal_default,
|
|
49948
50008
|
"poc-readme.md": poc_readme_default,
|
|
50009
|
+
"hook-definition.md": hook_definition_default,
|
|
50010
|
+
"task.md": task_default,
|
|
49949
50011
|
"examples/plan-feature.md": plan_feature_default,
|
|
49950
50012
|
"examples/plan-migration.md": plan_migration_default,
|
|
49951
50013
|
"examples/design-service.md": design_service_default,
|
|
@@ -49977,7 +50039,9 @@ var init_source = __esm(() => {
|
|
|
49977
50039
|
{ name: "exploration-summary", description: "Source-grounded technical exploration summary" },
|
|
49978
50040
|
{ name: "exploration-research", description: "Technical exploration research notes" },
|
|
49979
50041
|
{ name: "exploration-proposal", description: "Optional technical exploration approach" },
|
|
49980
|
-
{ name: "poc-readme", description: "Disposable proof-of-concept branch README" }
|
|
50042
|
+
{ name: "poc-readme", description: "Disposable proof-of-concept branch README" },
|
|
50043
|
+
{ name: "hook-definition", description: "Reusable global Agent Skill hook definition" },
|
|
50044
|
+
{ name: "task", description: "Terse task or bug ticket with objective, context, and references" }
|
|
49981
50045
|
];
|
|
49982
50046
|
embeddedSource = {
|
|
49983
50047
|
catalog,
|
|
@@ -52536,7 +52600,7 @@ function createProgram(write = console.log, version = "0.1.0", options = {}) {
|
|
|
52536
52600
|
|
|
52537
52601
|
// src/index.ts
|
|
52538
52602
|
init_errors3();
|
|
52539
|
-
var version2 = "0.
|
|
52603
|
+
var version2 = "0.13.0";
|
|
52540
52604
|
try {
|
|
52541
52605
|
await createProgram(console.log, version2).parseAsync(process.argv);
|
|
52542
52606
|
} catch (error) {
|