@equinor/fusion-framework-cli 11.1.1 → 11.1.3
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/CHANGELOG.md +79 -0
- package/README.md +3 -2
- package/bin/build/bin.mjs +1 -1
- package/bin/build/cli.mjs +3 -3
- package/dist/esm/version.js +1 -1
- package/dist/types/cli/commands/app/build.d.ts +1 -1
- package/dist/types/cli/commands/app/check.d.ts +3 -3
- package/dist/types/cli/commands/app/config.d.ts +4 -4
- package/dist/types/cli/commands/app/dev.d.ts +4 -4
- package/dist/types/cli/commands/app/manifest.d.ts +4 -4
- package/dist/types/cli/commands/app/pack.d.ts +3 -3
- package/dist/types/cli/commands/app/publish.d.ts +4 -4
- package/dist/types/cli/commands/app/tag.d.ts +10 -11
- package/dist/types/cli/commands/app/upload.d.ts +4 -4
- package/dist/types/cli/commands/auth/login.d.ts +14 -0
- package/dist/types/cli/commands/auth/logout.d.ts +13 -3
- package/dist/types/cli/commands/auth/token.d.ts +15 -1
- package/dist/types/cli/commands/portal/build.d.ts +25 -0
- package/dist/types/cli/commands/portal/config.d.ts +4 -4
- package/dist/types/cli/commands/portal/dev.d.ts +25 -0
- package/dist/types/cli/commands/portal/manifest.d.ts +28 -0
- package/dist/types/cli/commands/portal/pack.d.ts +24 -0
- package/dist/types/cli/commands/portal/publish.d.ts +29 -0
- package/dist/types/cli/commands/portal/schema.d.ts +27 -0
- package/dist/types/cli/commands/portal/tag.d.ts +29 -0
- package/dist/types/cli/commands/portal/upload.d.ts +25 -0
- package/dist/types/cli/options/auth.d.ts +16 -0
- package/dist/types/version.d.ts +1 -1
- package/docs/application.md +5 -6
- package/docs/auth.md +7 -0
- package/docs/portal.md +4 -4
- package/package.json +6 -5
- package/docs/libsecret.md +0 -66
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@equinor/fusion-framework-cli",
|
|
3
|
-
"version": "11.1.
|
|
3
|
+
"version": "11.1.3",
|
|
4
4
|
"keywords": [
|
|
5
5
|
"Fusion",
|
|
6
6
|
"Fusion Framework",
|
|
@@ -99,10 +99,11 @@
|
|
|
99
99
|
"ora": "^8.0.1",
|
|
100
100
|
"read-package-up": "^11.0.0",
|
|
101
101
|
"vite": "^6.3.5",
|
|
102
|
+
"vite-tsconfig-paths": "^5.1.4",
|
|
102
103
|
"zod": "^3.25.76",
|
|
103
|
-
"@equinor/fusion-framework-dev-portal": "^1.0.
|
|
104
|
-
"@equinor/fusion-framework-
|
|
105
|
-
"@equinor/fusion-framework-
|
|
104
|
+
"@equinor/fusion-framework-dev-portal": "^1.0.2",
|
|
105
|
+
"@equinor/fusion-framework-dev-server": "^1.0.2",
|
|
106
|
+
"@equinor/fusion-framework-module-msal-node": "^1.0.2",
|
|
106
107
|
"@equinor/fusion-imports": "^1.1.2"
|
|
107
108
|
},
|
|
108
109
|
"devDependencies": {
|
|
@@ -122,9 +123,9 @@
|
|
|
122
123
|
"rxjs": "^7.8.1",
|
|
123
124
|
"type-fest": "^4.40.0",
|
|
124
125
|
"typescript": "^5.8.2",
|
|
125
|
-
"@equinor/fusion-framework-module": "^5.0.0",
|
|
126
126
|
"@equinor/fusion-framework-module-app": "^6.1.17",
|
|
127
127
|
"@equinor/fusion-framework-module-http": "^6.3.4",
|
|
128
|
+
"@equinor/fusion-framework-module": "^5.0.0",
|
|
128
129
|
"@equinor/fusion-framework-module-service-discovery": "^8.0.18"
|
|
129
130
|
},
|
|
130
131
|
"peerDependenciesMeta": {
|
package/docs/libsecret.md
DELETED
|
@@ -1,66 +0,0 @@
|
|
|
1
|
-
This CLI enables secure authentication and persistent token caching by storing credentials in your system's keychain. It uses [`@azure/msal-node`](https://github.com/AzureAD/microsoft-authentication-library-for-js/tree/dev/lib/msal-node) for authentication, which relies on the [`keytar`](https://github.com/atom/node-keytar) module for secure credential storage.
|
|
2
|
-
|
|
3
|
-
> **What is `libsecret`?**
|
|
4
|
-
> [`libsecret`](https://wiki.gnome.org/Projects/Libsecret) is a library for storing and retrieving passwords and secrets. On Linux, `keytar` depends on `libsecret` to access the system keyring.
|
|
5
|
-
|
|
6
|
-
## Platform Requirements
|
|
7
|
-
|
|
8
|
-
- **Windows:** No additional dependencies. `keytar` uses the Windows Credential Manager.
|
|
9
|
-
- **macOS:** No additional dependencies. `keytar` uses the macOS Keychain. If you encounter unusual issues (rare), you can optionally try installing `libsecret`:
|
|
10
|
-
```bash
|
|
11
|
-
brew install libsecret
|
|
12
|
-
```
|
|
13
|
-
- **Linux:** You must install `libsecret` for secure credential storage. See below for instructions.
|
|
14
|
-
|
|
15
|
-
## Linux Installation
|
|
16
|
-
Install the `libsecret` library based on your distribution:
|
|
17
|
-
|
|
18
|
-
- **Ubuntu/Debian**:
|
|
19
|
-
```bash
|
|
20
|
-
sudo apt-get update
|
|
21
|
-
sudo apt-get install -y libsecret-1-0 libsecret-1-dev
|
|
22
|
-
```
|
|
23
|
-
> Both runtime and development packages are required for building native modules.
|
|
24
|
-
- **Fedora**:
|
|
25
|
-
```bash
|
|
26
|
-
sudo dnf install -y libsecret libsecret-devel
|
|
27
|
-
```
|
|
28
|
-
> Install both runtime and development packages if you plan to build native modules.
|
|
29
|
-
- **Arch Linux**:
|
|
30
|
-
```bash
|
|
31
|
-
sudo pacman -S --noconfirm libsecret
|
|
32
|
-
```
|
|
33
|
-
|
|
34
|
-
## Verifying Installation
|
|
35
|
-
After installing `libsecret`, rebuild `keytar` to ensure it links correctly:
|
|
36
|
-
|
|
37
|
-
```bash
|
|
38
|
-
npm rebuild keytar
|
|
39
|
-
```
|
|
40
|
-
|
|
41
|
-
You can verify that `keytar` is working by running your CLI and checking for credential storage warnings. Alternatively, you can test with a simple script:
|
|
42
|
-
|
|
43
|
-
```js
|
|
44
|
-
const keytar = require('keytar');
|
|
45
|
-
keytar.setPassword('test-service', 'test-account', 'test-password')
|
|
46
|
-
.then(() => keytar.getPassword('test-service', 'test-account'))
|
|
47
|
-
.then(console.log)
|
|
48
|
-
.catch(console.error);
|
|
49
|
-
```
|
|
50
|
-
If you see errors related to `keytar` or `libsecret`, see troubleshooting below.
|
|
51
|
-
|
|
52
|
-
## Troubleshooting
|
|
53
|
-
- **Missing `libsecret` errors:** Ensure you have installed both the runtime and development packages (e.g., `libsecret-1-0` and `libsecret-1-dev` on Ubuntu/Debian).
|
|
54
|
-
- **Rebuild keytar:**
|
|
55
|
-
```bash
|
|
56
|
-
npm rebuild keytar
|
|
57
|
-
```
|
|
58
|
-
- **Still having issues?**
|
|
59
|
-
- Ensure your system keyring (e.g., GNOME Keyring or KWallet) is running and unlocked. On some headless or minimal Linux environments, you may need to start or configure the keyring daemon manually.
|
|
60
|
-
- See the [`keytar` troubleshooting guide](https://github.com/atom/node-keytar#troubleshooting).
|
|
61
|
-
- Consult your distribution's documentation for keyring setup.
|
|
62
|
-
|
|
63
|
-
## Resources
|
|
64
|
-
- [`keytar` documentation](https://github.com/atom/node-keytar)
|
|
65
|
-
- [`libsecret` project page](https://wiki.gnome.org/Projects/Libsecret)
|
|
66
|
-
- [@azure/msal-node](https://github.com/AzureAD/microsoft-authentication-library-for-js/tree/dev/lib/msal-node)
|