@tpsdev-ai/flair 0.25.3 → 0.25.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/dist/cli.js +9 -1
- package/package.json +1 -1
package/dist/cli.js
CHANGED
|
@@ -8018,7 +8018,15 @@ program
|
|
|
8018
8018
|
{
|
|
8019
8019
|
name: "@tpsdev-ai/flair",
|
|
8020
8020
|
kind: "bin",
|
|
8021
|
-
|
|
8021
|
+
// Same PATH-independence fix as flair-mcp below: when `flair` isn't on
|
|
8022
|
+
// PATH (a custom npm prefix — mise/fnm/nvm/volta, or the sudo-less
|
|
8023
|
+
// user-prefix install the README recommends), the bin probe returns
|
|
8024
|
+
// null even though the package IS globally installed, and `flair
|
|
8025
|
+
// upgrade` mis-reports "not detected → run npm install -g". Fall back
|
|
8026
|
+
// to the lib probe, which require.resolves the package.json regardless
|
|
8027
|
+
// of PATH or `--version` support. (Canary's 0.25.3 dogfooding caught
|
|
8028
|
+
// this — the fallback existed for flair-mcp but not for flair itself.)
|
|
8029
|
+
probe: () => probeBinVersion(execFileSync, "flair") ?? probeLibVersion("@tpsdev-ai/flair"),
|
|
8022
8030
|
},
|
|
8023
8031
|
{
|
|
8024
8032
|
name: "@tpsdev-ai/flair-mcp",
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@tpsdev-ai/flair",
|
|
3
|
-
"version": "0.25.
|
|
3
|
+
"version": "0.25.4",
|
|
4
4
|
"packageManager": "bun@1.3.10",
|
|
5
5
|
"description": "Identity, memory, and soul for AI agents. Cryptographic identity (Ed25519), semantic memory with local embeddings, and persistent personality — all in a single process.",
|
|
6
6
|
"type": "module",
|