@piklv/ftaql-cli 1.0.1 → 1.0.2
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 +5 -1
- package/binaries/ftaql-aarch64-apple-darwin/ftaql +0 -0
- package/binaries/ftaql-aarch64-pc-windows-msvc/ftaql.exe +0 -0
- package/binaries/ftaql-aarch64-unknown-linux-musl/ftaql +0 -0
- package/binaries/ftaql-arm-unknown-linux-musleabi/ftaql +0 -0
- package/binaries/ftaql-x86_64-apple-darwin/ftaql +0 -0
- package/binaries/ftaql-x86_64-pc-windows-msvc/ftaql.exe +0 -0
- package/binaries/ftaql-x86_64-unknown-linux-musl/ftaql +0 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -6,7 +6,11 @@ FtaQl helps you see where risk is actually accumulating in a TS/JS project. It w
|
|
|
6
6
|
|
|
7
7
|
After one run you can ask which files stay expensive across revisions, where coupling keeps growing, and when runtime cycles first appeared. That makes it useful for refactors, CI, and history analysis when you need an accumulated dataset instead of a one-off report.
|
|
8
8
|
|
|
9
|
-
|
|
9
|
+
FtaQl started as a fork of [`sgb-io/fta`](https://github.com/sgb-io/fta) and gradually grew into its own continuation of that idea. I am grateful to that project for the original inspiration and for making it possible to take the idea further.
|
|
10
|
+
|
|
11
|
+
---
|
|
12
|
+
|
|
13
|
+
The core is written in Rust, so repeated runs across large codebases and revision history stay practical. On Apple M1 hardware FtaQl can analyze up to **10000 files per second**.
|
|
10
14
|
|
|
11
15
|
## What FtaQl Collects
|
|
12
16
|
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|