@equinor/fusion-framework-cli 11.0.0-next.8 → 11.0.0

package/dist/types/lib/utils/resolve-github-annotations.d.ts

@@ -1,13 +1,44 @@
 /**
- * Interface for the expected structure of the GitHub Actions event payload.
+ * Represents the payload structure for various GitHub webhook events.
+ *
+ * This type covers common fields found in GitHub event payloads, such as push, pull request,
+ * workflow, and release events. All properties are optional to accommodate the differences
+ * between event types.
+ *
+ * @remarks only some are mapped to the GitHub API event types.
+ *
+ * @property after - The SHA of the most recent commit on the ref after the event.
+ * @property head_commit - Information about the head commit, including its SHA.
+ * @property ref - The Git ref (branch or tag) that triggered the event.
+ * @property workflow - The name of the workflow (for workflow-related events).
+ * @property action - The action performed (e.g., "opened", "closed", "created").
+ * @property repository - Information about the repository where the event occurred.
+ * @property pull_request - Details about the pull request (for pull request events).
+ * @property release - Details about the release (for release events).
+ * @property sender - Information about the user who triggered the event.
  */
-export interface GithubEventPayload {
+type GithubEventPayload = {
+    after?: string;
+    head_commit?: {
+        id?: string;
+    };
+    ref?: string;
+    workflow?: string;
+    action?: string;
+    repository?: {
+        owner?: {
+            login?: string;
+            avatar_url?: string;
+        };
+        name?: string;
+        license?: {
+            name?: string;
+        };
+        homepage?: string;
+    };
     pull_request?: {
         number?: number;
         title?: string;
-        user?: {
-            login?: string;
-        };
         head?: {
             sha?: string;
             ref?: string;
@@ -16,11 +47,6 @@ export interface GithubEventPayload {
         updated_at?: string;
         html_url?: string;
     };
-    after?: string;
-    head_commit?: {
-        id?: string;
-    };
-    ref?: string;
     release?: {
         tag_name?: string;
         name?: string;
@@ -31,9 +57,54 @@ export interface GithubEventPayload {
         published_at?: string;
         html_url?: string;
     };
+    sender?: {
+        login?: string;
+        avatar_url?: string;
+    };
+};
+/**
+ * Represents metadata and contextual information related to GitHub Actions workflows,
+ * pull requests, commits, releases, and associated actors.
+ *
+ * @property pull_request - Information about the pull request associated with the workflow run.
+ * @property pull_request.number - The pull request number.
+ * @property pull_request.title - The title of the pull request.
+ * @property pull_request.user - The user who created the pull request.
+ * @property pull_request.user.login - The login name of the pull request creator.
+ * @property pull_request.head - The head commit information of the pull request.
+ * @property pull_request.head.sha - The SHA of the head commit.
+ * @property pull_request.head.ref - The reference name of the head commit.
+ * @property pull_request.created_at - The creation timestamp of the pull request.
+ * @property pull_request.updated_at - The last update timestamp of the pull request.
+ * @property pull_request.html_url - The URL to view the pull request on GitHub.
+ * @property actor - The GitHub username of the actor who triggered the workflow.
+ * @property runId - The unique identifier of the workflow run.
+ * @property runUrl - The URL to view the workflow run on GitHub.
+ * @property repository - The full name of the repository (e.g., "owner/repo").
+ * @property after - The SHA of the commit after the workflow run.
+ * @property head_commit - Information about the head commit.
+ * @property head_commit.id - The SHA of the head commit.
+ * @property ref - The Git reference (e.g., "refs/heads/main").
+ * @property release - Information about the release associated with the workflow run.
+ * @property release.tag_name - The tag name of the release.
+ * @property release.name - The name of the release.
+ * @property release.body - The body or description of the release.
+ * @property release.draft - Indicates if the release is a draft.
+ * @property release.prerelease - Indicates if the release is a prerelease.
+ * @property release.created_at - The creation timestamp of the release.
+ * @property release.published_at - The publication timestamp of the release.
+ * @property release.html_url - The URL to view the release on GitHub.
+ * @property workflow - The name of the workflow.
+ * @property action - The name of the action being executed.
+ */
+export type GithubAnnotations = GithubEventPayload & {
     workflow?: string;
     action?: string;
-}
+    eventName: string;
+    actor?: string;
+    runId?: string;
+    runUrl?: string;
+};
 /**
  * Resolves GitHub Actions-specific annotation variables from environment variables.
  *
@@ -50,6 +121,7 @@ export interface GithubEventPayload {
  *   - GITHUB_REPOSITORY: Repository in the format owner/repo
  *   - GITHUB_SERVER_URL: Base URL of the GitHub server (defaults to https://github.com)
  *   - GITHUB_EVENT_PATH: Path to the event payload file (JSON)
+ *   - GITHUB_WORKFLOW: Name of the workflow
  *
  * Notes for maintainers:
  *   - The event payload can be large; consider truncating or parsing if only specific fields are needed.
@@ -61,5 +133,5 @@ export interface GithubEventPayload {
  *   - To add more annotations, extract additional environment variables as needed and include them in the returned object.
  *   - For custom workflows or self-hosted runners, verify that all required environment variables are available.
  */
-export declare const resolveAnnotations: () => Record<string, string>;
-export default resolveAnnotations;
+export declare const resolveGithubAnnotations: () => GithubAnnotations;
+export default resolveGithubAnnotations;

package/dist/types/lib/utils/types.d.ts

@@ -1,6 +1,62 @@
+/**
+ * Recursively makes all properties of a type optional, including nested objects and arrays.
+ *
+ * - For object types, all properties become optional and the transformation is applied deeply.
+ * - For array properties, the transformation is applied to the array's element type.
+ * - For primitive types and functions, the type is preserved as-is.
+ *
+ * This utility is useful for scenarios such as:
+ *   - Creating deeply partial configuration objects (e.g., for overrides or patch updates)
+ *   - Accepting partial user input for complex data structures
+ *   - Safely merging deeply nested objects
+ *
+ * @template T - The type to make recursively partial.
+ *
+ * @example
+ * // Simple object
+ * type Foo = { a: number; b: { c: string } };
+ * // RecursivePartial<Foo> is: { a?: number; b?: { c?: string } }
+ *
+ * // Object with array
+ * type Bar = { items: { id: string; value: number }[] };
+ * // RecursivePartial<Bar> is: { items?: Array<{ id?: string; value?: number }> }
+ *
+ * // Nested and mixed types
+ * type Baz = { x: number; y: { z: { w: string[] } } };
+ * // RecursivePartial<Baz> is: { x?: number; y?: { z?: { w?: string[] } } }
+ *
+ * // With primitives and functions
+ * type Qux = { cb: () => void; flag: boolean; nested: { n: number } };
+ * // RecursivePartial<Qux> is: { cb?: () => void; flag?: boolean; nested?: { n?: number } }
+ *
+ * @remarks
+ * - RecursivePartial preserves the original type for primitives, functions, and Date objects.
+ * - For union types, each member is transformed recursively.
+ * - TypeScript's built-in Partial<T> only makes top-level properties optional; RecursivePartial applies this deeply.
+ *
+ * @see Partial
+ * @see Value
+ */
 export type RecursivePartial<T> = {
     [P in keyof T]?: T[P] extends Array<infer U> ? Array<Value<U>> : Value<T[P]>;
 };
-type AllowedPrimitives = Function | boolean | string | number | Date;
+type AnyFunction = (...args: any[]) => unknown;
+/**
+ * Represents the set of primitive types and commonly used types allowed in the framework.
+ * Includes function types, booleans, strings, numbers, and Date objects.
+ *
+ * @remarks
+ * - `AnyFunction` should be defined elsewhere as a type representing any function signature.
+ * - Useful for constraining generic types or utility functions to a specific set of primitives.
+ */
+type AllowedPrimitives = AnyFunction | boolean | string | number | Date;
+/**
+ * Resolves to the type `T` if it extends `AllowedPrimitives`, otherwise recursively makes all properties of `T` optional.
+ *
+ * @typeParam T - The type to be evaluated.
+ * @remarks
+ * This utility type is useful for creating deeply partial versions of complex types,
+ * while preserving primitive types as-is.
+ */
 type Value<T> = T extends AllowedPrimitives ? T : RecursivePartial<T>;
 export {};

package/dist/types/version.d.ts

@@ -1 +1 @@
-export declare const version = "11.0.0-next.8";
+export declare const version = "11.0.0";

package/docs/application.md

@@ -98,6 +98,18 @@ pnpm init
 }
 ```
 
+> **Build Output Configuration:**
+> The CLI uses the `main` field (or `module` field) in your `package.json` to determine where to output the built application bundle. If neither field is specified, it defaults to `./dist/bundle.js`. 
+> 
+> **Why this approach?** Using the `main`/`module` fields ensures your package works correctly when served directly or when developing portals with internal references. This follows Node.js package conventions and enables proper module resolution.
+> 
+> **Important:** The output directory cannot be the project root, the `src` directory, or the current working directory. Always specify a dedicated build directory like `dist/`, `build/`, or similar.
+>
+> **Examples:**
+> - `"main": "dist/index.js"` → outputs to `dist/index.js`
+> - `"module": "build/app.esm.js"` → outputs to `build/app.esm.js`
+> - No `main`/`module` specified → defaults to `dist/bundle.js`
+
 #### Example `app.manifest.ts`
 
 ```ts
@@ -105,8 +117,8 @@ import { defineAppManifest } from '@equinor/fusion-framework-cli/app';
 
 export default defineAppManifest(async (env, { base }) => ({
   ...base,
-  name: 'My Fusion App',
-  version: '0.0.1',
+  appKey: 'my-app',
+  displayName: 'My First Awesome Fusion App'
   // Add more manifest fields as needed
 }));
 ```
@@ -136,6 +148,15 @@ pnpm fusion-framework-cli dev
 
 ### 5. Log in to Fusion Framework (if needed)
 
+> [!NOTE] 
+> __All HTTP requests to Fusion services require an authorized user.__  
+> For example, before running `fusion-framework-cli app publish`, make sure you are authenticated using `fusion-framework-cli auth login`.
+
+> [!WARNING]
+> The `fusion-framework-cli auth login` command is only available in interactive environments (such as your local terminal). For CI/CD pipelines or automated deployments, you must provide a valid authentication token using the `FUSION_TOKEN` environment variable.  
+>  
+> See [Authentication](./auth.md#setting-the-fusion-token-in-github) for details on setting up tokens for CI/CD.
+
 ```sh
 pnpm fusion-framework-cli auth login
 ```
@@ -144,7 +165,7 @@ pnpm fusion-framework-cli auth login
 
 ```sh
 pnpm fusion-framework-cli publish --env <environment>
-pnpm fusion-framework-cli app config --upload --env <environment>
+pnpm fusion-framework-cli app config --publish --env <environment>
 ```
 
 > **Tip:** For CI/CD and automation, set the `FUSION_TOKEN` environment variable. See [Authentication](./docs/auth.md) for details.
@@ -292,7 +313,7 @@ jobs:
       - name: Publish application
         run: pnpm exec fusion-framework-cli app upload --env ${{ matrix.env }} app-bundle.zip
       - step: Upload configuration
-        run: pnpm exec fusion-framework-cli app config --upload --env ${{ matrix.env }}
+        run: pnpm exec fusion-framework-cli app config --publish --env ${{ matrix.env }}
 ```
 
 > [!TIP]
@@ -305,7 +326,7 @@ You can use environment variables in your app configuration to inject secrets or
 
 ```yml
 step: Upload configuration
-run: pnpm exec fusion-framework-cli app config --upload --env ${{ matrix.env }}
+run: pnpm exec fusion-framework-cli app config --publish --env ${{ matrix.env }}
 with:
   CONFIG_VALUE_FOO: ${{ VAR.ENVIRONMENT_CONFIG_VALUE }}
   CONFIG_VALUE_BAR: ${{ SECRETS.ENVIRONMENT_CONFIG_SECRET_VALUE }}
@@ -342,6 +363,7 @@ The Fusion Framework CLI provides a suite of commands to support the full applic
 - [Pack](#pack) — Bundle your app into a distributable archive.
 - [Upload](#upload) — Upload your app bundle to the Fusion app store.
 - [Tag](#tag) — Tag a published app version for release management.
+- [Manifest](#manifest) — Generate your app manifest file.
 - [Check](#check) — Verify your app's registration status.
 - [Aliases](#aliases) — Deprecated commands and their replacements.
 
@@ -383,7 +405,7 @@ Publish your application to the Fusion app store (registry) for deployment. This
 | ------------------ | --------------------------------------------------------------------------------------------------- | ----------------- |
 | `[bundle]`         | Path to the app bundle to upload. If omitted, the CLI will build and bundle your app automatically. |                   |
 | `-e`, `--env`      | Target environment for deployment (e.g., `ci`, `fqa`, `fprd`).                                      |                   |
-| `-m`, `--manifest` | Manifest file to use for bundling (e.g., `app.manifest.ts`).                                        | `app.manifest.ts` |
+| `-m`, `--manifest` | Manifest file to use for bundling (e.g., `app.manifest.ts`) (optional).                             | `app.manifest.ts` |
 | `-t`, `--tag`      | Tag to apply to the published app (`latest` \| `preview`).                                          | `latest`          |
 | `-d`, `--debug`    | Enable debug mode for verbose logging.                                                              | `false`           |
 | `--token`          | Authentication token for Fusion.                                                                    |                   |
@@ -474,6 +496,14 @@ pnpm fusion-framework-cli build
 pnpm fusion-framework-cli build app.manifest.dev.ts --debug
 ```
 
+> [!NOTE]
+> The build output location is determined by the `main` field (or `module` field) in your `package.json`. If neither field is specified, the CLI defaults to `./dist/bundle.js`. This approach ensures your package works correctly when served directly or when developing portals with internal references, following Node.js package conventions for proper module resolution. The output directory cannot be the project root, the `src` directory, or the current working directory.
+>
+> **Examples:**
+> - `"main": "dist/index.js"` → builds to `dist/index.js`
+> - `"module": "build/app.esm.js"` → builds to `build/app.esm.js`
+> - No `main`/`module` specified → defaults to `dist/bundle.js`
+
 ### Pack
 
 Build a distributable app bundle archive for deployment.
@@ -562,17 +592,42 @@ pnpm fusion-framework-cli app tag <tag> [options]
 ```sh
 pnpm fusion-framework-cli app tag latest
 pnpm fusion-framework-cli app tag preview --env prod --manifest app.manifest.prod.ts
-pnpm fusion-framework-cli app tag stable --appKey my-app --version 1.2.3
+pnpm fusion-framework-cli app tag latest --appKey my-app --version 1.2.3
 ```
 
 > [!TIP] You can roll back a release by tagging a previous build as `latest`. Simply run the tag command with the desired version to make it the active release for deployment.
 
 > [!NOTE]
 > - The `tag` command requires a published application version. You can specify the app key and version directly, or let the CLI resolve them from your manifest file.
-> - Supported tags are: `latest`, `preview`, and `stable`.
+> - Supported tags are: `latest` and `preview`.
 > - Authentication options (`--token`, `--tenantId`, `--clientId`) can be set via CLI flags or environment variables.
 > - If tagging fails, an error will be logged and the process will exit with a non-zero code.
 
+### Manifest
+
+Generate and output your application manifest for Fusion apps.
+
+| Option/Argument       | Description                                                                | Default / Example |
+| --------------------- | -------------------------------------------------------------------------- | ----------------- |
+| `[manifest]`          | Manifest build file to use (e.g., `app.manifest[.env]?.[ts,js,json]`).   | `app.manifest.ts` |
+| `-d, --debug`         | Enable debug mode for verbose logging.                                    | `false`           |
+| `-o, --output <path>` | Write manifest to the specified file (default: stdout).                   | `stdout`          |
+| `-s, --silent`        | Silent mode, suppresses output except errors.                             | `false`           |
+
+**Usage:**
+```sh
+pnpm fusion-framework-cli app manifest [manifest] [options]
+```
+
+**Examples:**
+```sh
+pnpm fusion-framework-cli app manifest
+pnpm fusion-framework-cli app manifest app.manifest.prod.ts --output ./dist/app.manifest.json
+pnpm fusion-framework-cli app manifest --debug
+```
+
+> **Tip:** By default, the manifest is printed to stdout. Use `--output` to write it to a file for use in CI/CD pipelines or for inspection.
+
 ### Check
 
 Check if a Fusion application is registered in the Fusion app store (registry).

package/docs/auth.md

@@ -75,7 +75,7 @@ When configuring authentication for the Fusion Framework CLI, you will encounter
 
 ## Local Development
 
-### Logging in with the CLI
+### Login in with the CLI
 
 For local development, you should authenticate interactively using the CLI's built-in login command. This uses the `interactive` authentication mode, which will prompt you to sign in via your browser and securely store your credentials for future CLI commands.
 
@@ -113,6 +113,22 @@ The CLI provides several authentication-related options for advanced scenarios o
 
 These options allow you to use the CLI with custom tenants, client apps, or tokens if needed, but for most development scenarios, the built-in defaults are sufficient and only the `--scope` option is commonly changed. This flexibility supports both simple and advanced authentication needs, making it easy to get started while enabling custom setups for more complex environments.
 
+### Acquiring token
+
+The `auth token` command is designed to show your access token for the current user.
+
+```sh
+fusion-framework-cli auth token
+```
+
+> [!TIP]
+> The `--silent` flag outputs only the token (no extra logging), which is useful for exporting the token as an environment variable or saving it to a file for local testing or scripting:
+> ```sh
+> export FUSION_TOKEN=$(fusion-framework-cli auth token --silent)
+> ```
+
+> [!Note] This command requires an interactive user context and MSAL Node. It is not suitable for CI/CD environments, as there is no user available in those scenarios. Use it for local development, testing, or whenever you need to preserve a Fusion token for your own scripts or tools.
+
 ## CI/CD
 
 ### Setting the Fusion Token in GitHub

package/docs/migration-v10-to-v11.md

@@ -1,5 +1,5 @@
 ---
-title: Migration Guide: v10 to v11 CLI Command Changes
+title: Migration Guide - v10 to v11 CLI Command Changes
 description: >
   Comprehensive guide to migrating CLI commands from v10 to v11 of the Fusion Framework, including deprecated commands, new command names, authentication changes, and best practices for updating scripts and pipelines.
 category: cli
@@ -33,11 +33,11 @@ With v11, we switched to using the Fusion Framework itself for CLI operations. T
 - **Reduced duplication:** By reusing core modules, bug fixes and new features are shared between CLI and Framework code.
 - **Performance:** The framework is now initialized only when needed (e.g., for HTTP calls or authentication), improving startup time and resource usage.
 
-## Deprecated App Command Aliases
+## Command Changes
 
-This guide covers command changes for the `fusion-framework-cli app` scope.
+### Deprecated App Command Aliases
 
-The following table lists the old commands and their new equivalents:
+The following `fusion-framework-cli app` commands have been renamed:
 
 | Old Command    | New Command |
 | -------------- | ----------- |
@@ -46,29 +46,41 @@ The following table lists the old commands and their new equivalents:
 | build-manifest | manifest    |
 | build-publish  | publish     |
 
-When using a deprecated command, the CLI will display a warning message and guide you to use the new command. Deprecated options such as `--service` are no longer supported; use `--env` instead.
-
 > [!WARNING]
-> The deprecated commands will continue to work for now, but they are scheduled for removal in the next major release. Please migrate to the new commands as soon as possible.
+> **Deprecated commands will be removed in the next major release.** While they continue to work with warning messages, please migrate to the new commands immediately.
 
-### Additional Notes
-- The deprecated `--service` option is no longer supported. Use `--env` for environment selection.
-- Only the new command names will be supported in future versions. Update your CI/CD pipelines and documentation as soon as possible.
-- The deprecated commands are maintained for backward compatibility during the transition to v11, but will be removed in the next major release. Please migrate to the new commands as soon as possible.
+### Option Changes
+- **Removed:** `--service` option
+- **Use instead:** `--env` for environment selection
 
 ## Authentication Changes
-- The `FUSION_TOKEN` environment variable should only be used for CI/CD and automated deployments.
-- For local development, users should authenticate interactively by running:
+
+Authentication behavior has been updated to improve security and consistency:
+
+- **For CI/CD and automation:** Continue using the `FUSION_TOKEN` environment variable
+- **For local development:** Use interactive authentication:
   ```sh
   fusion-framework-cli auth login
   ```
-  before executing any commands.
 
-## What to Check When Migrating
-- Update all scripts, documentation, and CI/CD pipelines to use the new command names.
-- Remove any usage of the deprecated `--service` option and replace it with `--env`.
-- Ensure your local development workflow uses `fusion-framework-cli auth login` for authentication.
-- Review any custom integrations that may rely on CLI startup behavior, as initialization is now on-demand.
+## Migration Checklist
+
+When upgrading from v10 to v11, ensure you:
+
+- [ ] **Update command names** in all scripts and CI/CD pipelines:
+  - `build-pack` → `pack`
+  - `build-upload` → `upload` 
+  - `build-manifest` → `manifest`
+  - `build-publish` → `publish`
+- [ ] **Replace `--service` with `--env`** for environment selection
+- [ ] **Update local development workflow** to use `fusion-framework-cli auth login`
+- [ ] **Review custom integrations** that may depend on CLI startup behavior (now on-demand)
+- [ ] **Update documentation** and team guidelines with new command syntax
+
+## Getting Help
 
-For more details, see the CLI release notes or run `pnpm fusion-framework-cli app --help`.
+For additional information:
+- Run `pnpm fusion-framework-cli app --help` to see current command options
+- Check the CLI release notes for detailed changes
+- Review related documentation: [Authentication](./auth.md) and [Application Commands](./application.md)
 

package/package.json

@@ -1,7 +1,6 @@
 {
   "name": "@equinor/fusion-framework-cli",
-  "version": "11.0.0-next.8",
-  "homepage": "https://github.com/equinor/fusion-framework",
+  "version": "11.0.0",
   "keywords": [
     "Fusion",
     "Fusion Framework",
@@ -12,12 +11,17 @@
   "publishConfig": {
     "access": "public"
   },
+  "engines": {
+    "node": ">=20.0.0"
+  },
   "files": [
-    "bin",
-    "dist",
-    "docs",
-    "CHANGELOG.md",
-    "README.md"
+    "./bin",
+    "./dist/esm/lib",
+    "./dist/esm/version.js",
+    "./dist/types",
+    "./docs",
+    "./CHANGELOG.md",
+    "./README.md"
   ],
   "type": "module",
   "bin": {
@@ -45,7 +49,43 @@
     },
     "./bin": {
       "types": "./dist/types/bin/index.d.ts",
-      "import": "./bin/build/bin.js"
+      "import": "./bin/build/bin.mjs"
+    },
+    "./lib": {
+      "types": "./dist/types/lib/index.d.ts",
+      "import": "./dist/esm/lib/index.js"
+    },
+    "./utils": {
+      "types": "./dist/types/lib/utils/index.d.ts",
+      "import": "./dist/esm/lib/utils/index.js"
+    },
+    "./package.json": "./package.json",
+    "./README.md": "./README.md",
+    "./CHANGELOG.md": "./CHANGELOG.md"
+  },
+  "typesVersions": {
+    "*": {
+      ".": [
+        "dist/types/lib/index.d.ts"
+      ],
+      "app": [
+        "dist/types/lib/app/index.d.ts"
+      ],
+      "portal": [
+        "dist/types/lib/portal/index.d.ts"
+      ],
+      "dev-server": [
+        "dist/types/lib/dev-server.d.ts"
+      ],
+      "bin": [
+        "dist/types/bin/index.d.ts"
+      ],
+      "lib": [
+        "dist/types/lib/index.d.ts"
+      ],
+      "utils": [
+        "dist/types/lib/utils/index.d.ts"
+      ]
     }
   },
   "repository": {
@@ -54,46 +94,42 @@
     "directory": "packages/cli"
   },
   "dependencies": {
-    "adm-zip": "^0.5.10",
     "commander": "^13.0.0",
-    "keytar": "7.9.0",
+    "deepmerge": "^4.3.1",
     "ora": "^8.0.1",
-    "vite": "^6.3.5",
-    "chalk": "^5.3.0",
     "read-package-up": "^11.0.0",
-    "zod": "^3.25.20",
-    "@equinor/fusion-framework-dev-portal": "^1.0.0-next.2",
-    "@equinor/fusion-framework-dev-server": "^1.0.0-next.4",
-    "@equinor/fusion-imports": "^1.1.1-next.0"
+    "vite": "^6.3.5",
+    "zod": "^3.25.76",
+    "@equinor/fusion-framework-dev-portal": "^1.0.0",
+    "@equinor/fusion-framework-dev-server": "^1.0.0",
+    "@equinor/fusion-framework-module-msal-node": "^1.0.0",
+    "@equinor/fusion-imports": "^1.1.1"
   },
   "devDependencies": {
-    "ajv": "^8.17.1",
-    "pretty-bytes": "^7.0.0",
-    "is-ci": "^4.1.0",
-    "open": "^10.1.1",
-    "lodash.mergewith": "^4.6.2",
-    "type-fest": "^4.40.0",
-    "rollup": "^4.39.0",
     "@rollup/plugin-commonjs": "^28.0.3",
     "@rollup/plugin-json": "^6.1.0",
     "@rollup/plugin-node-resolve": "^16.0.1",
+    "@rollup/plugin-replace": "^6.0.2",
     "@types/adm-zip": "^0.5.0",
-    "@types/lodash.mergewith": "^4.6.9",
-    "@types/node": "^20.11.14",
+    "adm-zip": "^0.5.10",
+    "ajv": "^8.17.1",
+    "chalk": "^5.3.0",
+    "is-ci": "^4.1.0",
+    "open": "^10.1.1",
+    "pretty-bytes": "^7.0.0",
+    "rollup": "^4.46.3",
+    "rollup-plugin-terser": "^7.0.2",
     "rxjs": "^7.8.1",
+    "type-fest": "^4.40.0",
     "typescript": "^5.8.2",
-    "@equinor/fusion-framework-module-app": "^6.1.13",
-    "@equinor/fusion-framework-module-http": "^6.3.3-next.2",
-    "@equinor/fusion-framework-module": "^4.4.3-next.1",
-    "@equinor/fusion-framework-module-msal-node": "^0.1.1-next.2",
-    "@equinor/fusion-framework-module-service-discovery": "^8.0.15-next.2"
+    "@equinor/fusion-framework-module-app": "^6.1.17",
+    "@equinor/fusion-framework-module": "^5.0.0",
+    "@equinor/fusion-framework-module-http": "^6.3.4",
+    "@equinor/fusion-framework-module-service-discovery": "^8.0.18"
   },
   "peerDependenciesMeta": {
     "typescript": {
       "optional": true
-    },
-    "keytar": {
-      "optional": true
     }
   },
   "scripts": {

package/bin/build/bin.js

@@ -1,28 +0,0 @@
-export { b as buildApplication, c as buildPortal, a as bundleApp, d as bundlePortal, g as generateApplicationConfig, e as generatePortalConfig, l as loadPortalManifest, h as pack, p as publishAppConfig, f as publishPortalConfig, s as startAppDevServer } from './portal-config-publish-ezU_DFki.js';
-import 'vite';
-import 'chalk';
-import '@equinor/fusion-imports';
-import '@equinor/fusion-framework-dev-server';
-import 'node:fs';
-import 'node:fs/promises';
-import 'node:path';
-import 'read-package-up';
-import 'node:url';
-import 'node:assert';
-import 'node:child_process';
-import 'zod';
-import 'adm-zip';
-import 'http';
-import 'https';
-import 'crypto';
-import 'buffer';
-import 'stream';
-import 'util';
-import 'fs';
-import 'path';
-import 'node:http';
-import 'node:process';
-import 'node:buffer';
-import 'node:util';
-import 'node:os';
-import 'ora';