@mai0313/vibe-coding-tracker 0.5.2 → 0.5.4
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 +43 -20
- package/binaries/linux-arm64-gnu/vibe_coding_tracker +0 -0
- package/binaries/linux-x64-gnu/vibe_coding_tracker +0 -0
- package/binaries/macos-arm64/vibe_coding_tracker +0 -0
- package/binaries/macos-x64/vibe_coding_tracker +0 -0
- package/binaries/windows-arm64/vibe_coding_tracker.exe +0 -0
- package/binaries/windows-x64/vibe_coding_tracker.exe +0 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -12,6 +12,7 @@
|
|
|
12
12
|
[](https://github.com/Mai0313/VibeCodingTracker/actions/workflows/test.yml)
|
|
13
13
|
[](https://github.com/Mai0313/VibeCodingTracker/actions/workflows/code-quality-check.yml)
|
|
14
14
|
[](https://github.com/Mai0313/VibeCodingTracker/tree/master?tab=License-1-ov-file)
|
|
15
|
+
[](https://github.com/Mai0313/VibeCodingTracker)
|
|
15
16
|
[](https://github.com/Mai0313/VibeCodingTracker/pulls)
|
|
16
17
|
|
|
17
18
|
</center>
|
|
@@ -640,30 +641,65 @@ vct version --text
|
|
|
640
641
|
|
|
641
642
|
**Keep your installation up-to-date automatically.**
|
|
642
643
|
|
|
643
|
-
The update command
|
|
644
|
+
The update command works for **all installation methods** (npm/pip/cargo/manual) by directly downloading and replacing the binary from GitHub releases.
|
|
644
645
|
|
|
645
646
|
### Basic Usage
|
|
646
647
|
|
|
647
648
|
```bash
|
|
649
|
+
# Check for updates
|
|
650
|
+
vct update --check
|
|
651
|
+
|
|
648
652
|
# Interactive update with confirmation
|
|
649
653
|
vct update
|
|
650
654
|
|
|
651
|
-
#
|
|
652
|
-
vct update --check
|
|
653
|
-
|
|
654
|
-
# Force update without confirmation prompt
|
|
655
|
+
# Force update - always downloads latest version (even if already up-to-date)
|
|
655
656
|
vct update --force
|
|
656
657
|
```
|
|
657
658
|
|
|
658
|
-
### How It Works
|
|
659
|
+
### ✨ How It Works
|
|
659
660
|
|
|
660
661
|
1. **Check Latest Version**: Fetches the latest release from GitHub API
|
|
661
|
-
2. **Compare Versions**: Compares current version with the latest available
|
|
662
|
+
2. **Compare Versions**: Compares current version with the latest available (skipped with `--force`)
|
|
662
663
|
3. **Download Binary**: Downloads the appropriate binary for your platform (Linux/macOS/Windows)
|
|
663
664
|
4. **Smart Replacement**:
|
|
664
665
|
- **Linux/macOS**: Automatically replaces the binary (backs up old version to `.old`)
|
|
665
666
|
- **Windows**: Downloads as `.new` and creates a batch script for safe replacement
|
|
666
667
|
|
|
668
|
+
### 🔄 Force Update Mode
|
|
669
|
+
|
|
670
|
+
The `--force` flag bypasses version checking and **always downloads** the latest release:
|
|
671
|
+
|
|
672
|
+
```bash
|
|
673
|
+
# Force reinstall the latest version (useful for corrupted installations)
|
|
674
|
+
vct update --force
|
|
675
|
+
```
|
|
676
|
+
|
|
677
|
+
**Use cases**:
|
|
678
|
+
|
|
679
|
+
- Reinstall after corrupted binary
|
|
680
|
+
- Force download latest release without version check
|
|
681
|
+
- Troubleshooting installation issues
|
|
682
|
+
|
|
683
|
+
**Only fails if**: No binary is found for your platform (OS/architecture)
|
|
684
|
+
|
|
685
|
+
### 🎯 Works for All Installation Methods
|
|
686
|
+
|
|
687
|
+
Whether you installed via **npm**, **pip**, **cargo**, or **manually**, `vct update` will work the same way:
|
|
688
|
+
|
|
689
|
+
```bash
|
|
690
|
+
$ vct update --check
|
|
691
|
+
🔍 Checking for updates...
|
|
692
|
+
📌 Current version: 0.1.6
|
|
693
|
+
📌 Latest version: v0.1.7
|
|
694
|
+
|
|
695
|
+
🆕 New version available: v0.1.7
|
|
696
|
+
|
|
697
|
+
💡 To update, run:
|
|
698
|
+
vct update
|
|
699
|
+
```
|
|
700
|
+
|
|
701
|
+
**Why does this work?** All installation methods (npm/pip/cargo/manual) use the **same pre-compiled binaries** from GitHub releases. The update command simply downloads the latest binary and replaces your current installation.
|
|
702
|
+
|
|
667
703
|
### Platform Support
|
|
668
704
|
|
|
669
705
|
The update command automatically detects your platform and downloads the correct archive:
|
|
@@ -682,19 +718,6 @@ On Windows, the binary cannot be replaced while running. The update command:
|
|
|
682
718
|
|
|
683
719
|
Run the batch script after closing the application to finish the update.
|
|
684
720
|
|
|
685
|
-
### Automatic Update Notifications
|
|
686
|
-
|
|
687
|
-
**Stay informed of new releases automatically.**
|
|
688
|
-
|
|
689
|
-
When you start `vct`, it automatically checks for updates once every 24 hours and displays a notification if a new version is available. The notification intelligently detects your installation method and shows the appropriate update command:
|
|
690
|
-
|
|
691
|
-
- **npm**: `npm update -g @mai0313/vct`
|
|
692
|
-
- **pip**: `pip install --upgrade vibe_coding_tracker`
|
|
693
|
-
- **cargo**: `cargo install vibe_coding_tracker --force`
|
|
694
|
-
- **manual**: `vct update` or re-run installation script
|
|
695
|
-
|
|
696
|
-
This ensures you always use the correct update method and prevents version conflicts. The check runs silently in the background and won't disrupt your workflow if updates aren't available.
|
|
697
|
-
|
|
698
721
|
---
|
|
699
722
|
|
|
700
723
|
## 💡 Smart Pricing System
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@mai0313/vibe-coding-tracker",
|
|
3
|
-
"version": "0.5.
|
|
3
|
+
"version": "0.5.4",
|
|
4
4
|
"description": "Vibe Coding Tracker - AI coding assistant telemetry/usage parser, aggregate JSONL events into CodeAnalysis results",
|
|
5
5
|
"author": "Wei Lee <mai@mai0313.com>",
|
|
6
6
|
"license": "MIT",
|