@equinor/fusion-framework-cli 11.1.2 → 11.1.4

package/docs/auth.md

@@ -1,5 +1,7 @@
 The Fusion Framework CLI provides secure, robust authentication for both automation and interactive development scenarios by leveraging Microsoft's MSAL (Microsoft Authentication Library) and Azure Active Directory (Azure AD). Authentication is handled through the Fusion Framework for Node.js, using the `@equinor/fusion-framework-module-msal-node` package, which is built on top of Microsoft's official `msal-node` library. This ensures standards-compliant, up-to-date authentication flows and seamless integration across Fusion Framework applications and tools.
 
+For detailed information about the underlying authentication module, see the [MSAL Node Module documentation](https://equinor.github.io/fusion-framework/modules/auth/msal-node/).
+
 ## Key features
 - **Multiple authentication modes:**
   - `token_only`: Use a pre-provided token (e.g., for CI/CD and automation).
@@ -160,4 +162,9 @@ runs:
       shell: bash
       run: |
         echo "FUSION_TOKEN=$(az account get-access-token --scope ${{ inputs.scope }} --query accessToken --output tsv)" >> $GITHUB_ENV
+
+## Additional Resources
+
+- [MSAL Node Module Documentation](https://equinor.github.io/fusion-framework/modules/auth/msal-node/) - Complete reference for the underlying authentication module
+- [libsecret Setup Guide](https://equinor.github.io/fusion-framework/modules/auth/msal-node/docs/libsecret.html) - Platform-specific setup for secure credential storage on Linux systems
 ```

package/docs/portal.md

@@ -157,8 +157,8 @@ Tag a published portal template version in the Fusion portal registry.
 | Option/Argument   | Description                           | Default / Example |
 | ----------------- | ------------------------------------- | ----------------- |
 | `<tag>`           | Tag to apply (`latest` \| `preview`). |                   |
-| `--name <name>`   | Portal name.                          |                   |
-| `--version <ver>` | Version to tag.                       |                   |
+| `-p, --package`   | Package to tag in format name@version. |                   |
+| `-m, --manifest`  | Manifest file to use.                 | `portal.manifest.ts` |
 | `--token`         | Authentication token for Fusion.      |                   |
 | `--tenantId`      | Azure tenant ID for authentication.   |                   |
 | `--clientId`      | Azure client ID for authentication.   |                   |
@@ -170,8 +170,8 @@ pnpm fusion-framework-cli portal tag <tag> [options]
 
 **Examples:**
 ```sh
-pnpm fusion-framework-cli portal tag latest --name my-portal --version 1.0.0
-pnpm fusion-framework-cli portal tag preview --name my-portal --version 1.1.0-beta
+pnpm fusion-framework-cli portal tag latest --package my-portal@1.0.0
+pnpm fusion-framework-cli portal tag preview --package my-portal@1.1.0-beta
 ```
 
 ---

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@equinor/fusion-framework-cli",
-  "version": "11.1.2",
+  "version": "11.1.4",
   "keywords": [
     "Fusion",
     "Fusion Framework",
@@ -101,10 +101,10 @@
     "vite": "^6.3.5",
     "vite-tsconfig-paths": "^5.1.4",
     "zod": "^3.25.76",
-    "@equinor/fusion-framework-dev-portal": "^1.0.1",
-    "@equinor/fusion-framework-module-msal-node": "^1.0.1",
-    "@equinor/fusion-imports": "^1.1.2",
-    "@equinor/fusion-framework-dev-server": "^1.0.2"
+    "@equinor/fusion-framework-dev-portal": "^1.0.2",
+    "@equinor/fusion-framework-dev-server": "^1.0.2",
+    "@equinor/fusion-framework-module-msal-node": "^1.0.2",
+    "@equinor/fusion-imports": "^1.1.2"
   },
   "devDependencies": {
     "@rollup/plugin-commonjs": "^28.0.3",
@@ -112,10 +112,12 @@
     "@rollup/plugin-node-resolve": "^16.0.1",
     "@rollup/plugin-replace": "^6.0.2",
     "@types/adm-zip": "^0.5.0",
+    "@types/normalize-package-data": "^2.4.4",
     "adm-zip": "^0.5.10",
     "ajv": "^8.17.1",
     "chalk": "^5.6.0",
     "is-ci": "^4.1.0",
+    "normalize-package-data": "^8.0.0",
     "open": "^10.1.1",
     "pretty-bytes": "^7.0.0",
     "rollup": "^4.46.3",
@@ -124,7 +126,7 @@
     "type-fest": "^4.40.0",
     "typescript": "^5.8.2",
     "@equinor/fusion-framework-module": "^5.0.0",
-    "@equinor/fusion-framework-module-app": "^6.1.17",
+    "@equinor/fusion-framework-module-app": "^6.1.18",
     "@equinor/fusion-framework-module-http": "^6.3.4",
     "@equinor/fusion-framework-module-service-discovery": "^8.0.18"
   },

package/docs/libsecret.md

@@ -1,66 +0,0 @@
-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.
-
-> **What is `libsecret`?**  
-> [`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.
-
-## Platform Requirements
-
-- **Windows:** No additional dependencies. `keytar` uses the Windows Credential Manager.
-- **macOS:** No additional dependencies. `keytar` uses the macOS Keychain. If you encounter unusual issues (rare), you can optionally try installing `libsecret`:
-  ```bash
-  brew install libsecret
-  ```
-- **Linux:** You must install `libsecret` for secure credential storage. See below for instructions.
-
-## Linux Installation
-Install the `libsecret` library based on your distribution:
-
-- **Ubuntu/Debian**:
-  ```bash
-  sudo apt-get update
-  sudo apt-get install -y libsecret-1-0 libsecret-1-dev
-  ```
-  > Both runtime and development packages are required for building native modules.
-- **Fedora**:
-  ```bash
-  sudo dnf install -y libsecret libsecret-devel
-  ```
-  > Install both runtime and development packages if you plan to build native modules.
-- **Arch Linux**:
-  ```bash
-  sudo pacman -S --noconfirm libsecret
-  ```
-
-## Verifying Installation
-After installing `libsecret`, rebuild `keytar` to ensure it links correctly:
-
-```bash
-npm rebuild keytar
-```
-
-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:
-
-```js
-const keytar = require('keytar');
-keytar.setPassword('test-service', 'test-account', 'test-password')
-  .then(() => keytar.getPassword('test-service', 'test-account'))
-  .then(console.log)
-  .catch(console.error);
-```
-If you see errors related to `keytar` or `libsecret`, see troubleshooting below.
-
-## Troubleshooting
-- **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).
-- **Rebuild keytar:**
-  ```bash
-  npm rebuild keytar
-  ```
-- **Still having issues?**
-  - 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.
-  - See the [`keytar` troubleshooting guide](https://github.com/atom/node-keytar#troubleshooting).
-  - Consult your distribution's documentation for keyring setup.
-
-## Resources
-- [`keytar` documentation](https://github.com/atom/node-keytar)
-- [`libsecret` project page](https://wiki.gnome.org/Projects/Libsecret)
-- [@azure/msal-node](https://github.com/AzureAD/microsoft-authentication-library-for-js/tree/dev/lib/msal-node)