@equinor/fusion-framework-cli 10.7.4 → 11.0.0-next.0

package/CHANGELOG.md

@@ -1,5 +1,49 @@
 # Change Log
 
+## 11.0.0-next.0
+
+### Major Changes
+
+- [#3074](https://github.com/equinor/fusion-framework/pull/3074) [`6b034e5`](https://github.com/equinor/fusion-framework/commit/6b034e5459094cea0c0f2490335eef3092390a13) Thanks [@odinr](https://github.com/odinr)! - The CLI has been rewritten to use Fusion Framework internally to minimize dependencies and improve performance. This change allows the CLI to be more efficient and maintainable. It also means that the CLI is now a first-class citizen in the Fusion Framework ecosystem, providing a more consistent and integrated experience.
+
+  The dev portal has been moved out to a separate package `@equinor/fusion-framework-dev-server`. This separation allows for a more modular architecture, enabling developers to use the dev portal independently of the CLI. It also facilitates easier updates and maintenance of the dev portal without affecting the CLI functionality. It also allows for 3rd party developers to create their own dev portals using the Fusion Framework. Also, moving the dev portal to a separate package allows for better versioning and dependency management, ensuring that developers can always use the latest features and improvements without being tied to the CLI release cycle.
+
+  The dev portal can be configured using the `dev-server.config.js` file, which allows developers to customize the behavior and appearance of the dev portal. This configuration file provides flexibility in how the dev portal operates, enabling developers to tailor it to their specific needs and preferences. **this is currently not documented, but will be in the future**
+
+  Since the dev portal uses the plugin `@equinor/fusion-framework-vite-plugin-spa`, it is possible to specify a live portal to preview the application in the dev portal. This feature allows developers to see their changes in real-time, enhancing the development experience and speeding up the feedback loop. It is particularly useful for testing and debugging applications during development.
+
+  The dev portal also supports mocking API services, which allows developers to simulate backend services without needing a live server. This feature is particularly useful for testing and development, as it enables developers to work on the frontend independently of the backend, ensuring a smoother development process. **this is currently not documented, but will be in the future**
+
+  The dev portal is a key component of the Fusion Framework ecosystem, providing a user-friendly interface for developers to interact with their applications. It allows developers to easily manage and test their applications, providing a streamlined development experience.
+
+  The Dev Portal uses by default the `@equinor/fusion-framework-dev-portal` package, which is the official dev portal package provided by Fusion which is developer-friendly portal for developing and testing Fusion Framework applications. But it is possible to specify any package as a dev portal, allowing for customization of the development experience. This flexibility enables developers to create their own dev portals or use third-party solutions that better fit their needs.
+
+  The CLI now supports the `fusion-framework-cli auth login` command for authentication, which is a more secure and user-friendly way to manage access to Fusion Framework applications. This command simplifies the authentication process, making it easier for developers to log in and start working on their applications without needing to manually set environment variables or manage tokens. _`FUSION_TOKEN`_ is still supported for CI/CD and automation, but the CLI now provides a more streamlined and intuitive way to handle authentication.
+
+  The CLI has now been divided into three main groups:
+
+  - **bin**: This namespace contains executable functions that can be executed from node scripts, handy for automation and scripting or creating a custom CLI.
+  - **commands**: This namespace contains commands that can be executed from the CLI, providing a user-friendly interface for developers to interact with the Fusion Framework.
+  - **lib**: This namespace is reserved for consumers of the CLI, like defining configuration files, exposing interfaces, and other utilities that can be used in custom scripts or applications. This separation allows for better organization and modularity of the CLI codebase, making it easier to maintain and extend.
+
+  **BREAKING CHANGES:**
+
+  the `--service` flag has been removed since the CLI now uses the Fusion Framework internally, which does not require this flag, but uses service discovery to resolve endpoints automatically according to provided Fusion environment variables. This change simplifies the CLI usage and aligns it more closely with the Fusion Framework's architecture, allowing for a more seamless integration and improved developer experience.
+
+  All `app -build-???` has alias to correct commands, but been flagged as deprecated and will be removed in the next major version.
+
+### Minor Changes
+
+- [#3074](https://github.com/equinor/fusion-framework/pull/3074) [`6b034e5`](https://github.com/equinor/fusion-framework/commit/6b034e5459094cea0c0f2490335eef3092390a13) Thanks [@odinr](https://github.com/odinr)! - Added CLI, bin and lib functionality to the Fusion Framework CLI for portal development and management.
+
+### Patch Changes
+
+- [#3074](https://github.com/equinor/fusion-framework/pull/3074) [`6b034e5`](https://github.com/equinor/fusion-framework/commit/6b034e5459094cea0c0f2490335eef3092390a13) Thanks [@odinr](https://github.com/odinr)! - update Vite to 6.3.5
+
+- Updated dependencies [[`6b034e5`](https://github.com/equinor/fusion-framework/commit/6b034e5459094cea0c0f2490335eef3092390a13), [`6b034e5`](https://github.com/equinor/fusion-framework/commit/6b034e5459094cea0c0f2490335eef3092390a13), [`6b034e5`](https://github.com/equinor/fusion-framework/commit/6b034e5459094cea0c0f2490335eef3092390a13), [`6b034e5`](https://github.com/equinor/fusion-framework/commit/6b034e5459094cea0c0f2490335eef3092390a13)]:
+  - @equinor/fusion-framework-dev-server@1.0.0-next.0
+  - @equinor/fusion-framework-dev-portal@1.0.0-next.0
+
 ## 10.7.4
 
 ### Patch Changes

package/README.md

@@ -1,42 +1,169 @@
 ---
 title: Fusion Framework CLI
+description: >
+  Fusion Framework CLI is a powerful tool for developing, building, and publishing applications and portal templates within the Fusion Framework ecosystem. See the documentation for full guides, configuration, and advanced usage.
+tags: 
+  - fusion-framework
+  - cli
+  - app-development
+  - portal-development
+  - dev-server
+  - ci-cd
+  - authentication
+  - configuration
+  - manifest
+  - registry
+  - publishing
+  - service-discovery
+  - equinor
+  - documentation
+  - getting-started
+keywords:
+  - fusion framework
+  - cli
+  - app development
+  - portal development
+  - dev server
+  - authentication
+  - ci/cd
+  - configuration
+  - manifest
+  - publishing
+  - registry
+  - service discovery
 ---
 
-### fusion-framework-cli
+# Fusion Framework CLI
 
-The cli, named `fusion-framework-cli`, contains tooling for running, building and publishing your application.
+[![npm version](https://img.shields.io/npm/v/@equinor/fusion-framework-cli.svg?style=flat)](https://www.npmjs.com/package/@equinor/fusion-framework-cli)
+[![License: ISC](https://img.shields.io/badge/License-ISC-blue.svg)](./LICENSE)
 
-The fusion-famework-cli should be installed as a devDependency.
+---
+
+## Table of Contents
+
+- [Fusion Framework CLI](#fusion-framework-cli)
+  - [Table of Contents](#table-of-contents)
+  - [Overview](#overview)
+  - [Features \& Benefits](#features--benefits)
+  - [Getting Started](#getting-started)
+    - [1. Install the CLI](#1-install-the-cli)
+    - [2. Initialize or update your app's manifest and config files](#2-initialize-or-update-your-apps-manifest-and-config-files)
+    - [3. Start the development server](#3-start-the-development-server)
+    - [4. Log in to the Fusion Framework (if needed)](#4-log-in-to-the-fusion-framework-if-needed)
+    - [5. Build and publish your app](#5-build-and-publish-your-app)
+    - [6. Upload configuration](#6-upload-configuration)
+  - [Common Commands](#common-commands)
+  - [Example: package.json](#example-packagejson)
+  - [Troubleshooting](#troubleshooting)
+  - [Documentation](#documentation)
+  - [Contributing](#contributing)
+  - [Tooling Roadmap](#tooling-roadmap)
+
+## Overview
+
+Fusion Framework CLI is a command-line tool for developing, building, and publishing applications and portal templates within the Fusion Framework ecosystem. It streamlines workflows, automates common tasks, and supports modern CI/CD pipelines.
+
+## Features & Benefits
+
+- **Unified developer experience**: One tool for development, build, and deployment.
+- **Rapid local development**: Hot reload and fast feedback.
+- **Environment-specific configuration**: Manage manifests and configs per environment.
+- **Integrated authentication**: Secure your apps locally and in CI/CD pipelines.
+- **Service discovery**: Built-in support for Fusion services.
+- **Extensible architecture**: Widgets, portals, and more coming soon.
+- **Comprehensive documentation**: Migration guides, app/portal setup, and troubleshooting.
+
+## Getting Started
+
+### 1. Install the CLI
 
 ```sh
 pnpm add -D @equinor/fusion-framework-cli
 ```
 
-You can always use the option `-h or --help or help` to get help for the CLI and its commands.
+### 2. Initialize or update your app's manifest and config files
+
+See [Developing Apps](./docs/application.md) for manual setup and configuration guidance.
+
+### 3. Start the development server
+
+```sh
+pnpm fusion-framework-cli dev
+```
+
+### 4. Log in to the Fusion Framework (if needed)
+
+```sh
+pnpm fusion-framework-cli auth login
+```
+
+### 5. Build and publish your app
+
+```sh
+pnpm fusion-framework-cli publish --env <environment>
+```
 
-Example:
+### 6. Upload configuration
 
 ```sh
-fusion-framework-cli help
+pnpm fusion-framework-cli app config --upload --env <environment>
+```
+
+> **Tip:** For CI/CD and automation, set the `FUSION_TOKEN` environment variable. See [Authentication](./docs/auth.md) for details.
+
+## Common Commands
+
+| Command                                | Description                          |
+| -------------------------------------- | ------------------------------------ |
+| `pnpm fusion-framework-cli dev`        | Start local development server       |
+| `pnpm fusion-framework-cli auth login` | Authenticate with Fusion             |
+| `pnpm fusion-framework-cli app ...`    | Working with Fusion applications     |
+| `pnpm fusion-framework-cli portal ...` | Working with Fusion portal templates |
+
+## Example: package.json
+
+A minimal example for a Fusion Framework app:
+
+```json
+{
+  "name": "@equinor/fusion-framework-app",
+  "version": "0.0.0",
+  "description": "Fusion Framework App",
+  "main": "dist/index.js",
+  "files": [
+    "path-to-some-file/foo.png"
+  ]
+}
 ```
 
-### App Commands
+> **Note:** The `main` field should point to the build output (e.g., `dist/index.js`).
+
+## Troubleshooting
 
-See [App Commands](/cli/docs/commands.md)
+If you encounter errors like `libsecret-1.so.0: cannot open shared object file`, it means `libsecret` is missing. see the [libsecret installation guide](./docs/libsecret.md) for instructions on how to install it based on your operating system.
 
-### Configuration
+- **Command not found?** Ensure your `node_modules/.bin` is in your PATH or use `pnpm`/`npx`.
+- **Authentication issues?** See [Authentication](./docs/auth.md) for troubleshooting tokens and login.
+- **Build errors?** Check your app's manifest and config files for typos or missing fields.
+- **Need help?** Open an issue or see the [docs folder](./docs/).
 
-See [Configuration](/cli/docs/configuration.md)
+## Documentation
 
-### Tooling
+- [Migration Guide: v10 to v11](./docs/migration-v10-to-v11.md): Learn about breaking changes and how to upgrade.
+- [Developing Apps](./docs/application.md): Step-by-step guide to building and configuring apps.
+- [Developing Portals](./docs/portal.md): Guide to building, configuring, and publishing portal templates.
+- [Authentication](./docs/auth.md): Setting up authentication for local and CI/CD environments.
+- For more guides and advanced topics, see the [docs folder](./docs/).
 
-- tooling for [Vitest](https://vitest.dev/) - 🚀 coming soon
-- tooling for proxy configuration  - 🚀 coming soon
+## Contributing
 
-### Widget
+We welcome contributions! See our [contributing guide](../../contributing/development.md) for details on how to get started, coding standards, and submitting pull requests.
 
-Tooling for developing widgets  - 🚀 coming soon
+## Tooling Roadmap
+
+- **Vitest integration** (coming soon)
+---
 
-### Portal
+For more information, visit the [docs folder](./docs/) or open an issue for support.
 
-Tooling for developing portals  - 🚀 coming

package/bin/cli.mjs

@@ -1,2 +1,5 @@
 #!/usr/bin/env node
-import('../dist/bin/main.js');
+// This file is a placeholder to prevent initial install failure due to a missing package entry file.
+// Importing './build/cli.js' before it exists is valid here, as the build step will generate it.
+// See project documentation for details.
+import('./build/cli.js');

package/dist/esm/bin/app-build.js

@@ -0,0 +1,34 @@
+import { build as viteBuild } from 'vite';
+import chalk from 'chalk';
+import { loadViteConfig } from './helpers/load-vite-config.js';
+import loadAppManifest from './app-manifest';
+/**
+ * Builds an application using Vite.
+ *
+ * Loads the application manifest, applies Vite configuration, and runs the Vite build process.
+ *
+ * @param opt - Build options including environment, manifest path, and logger.
+ * @returns Output containing package info, manifest, and output directory.
+ * @throws Will throw if the build process fails.
+ * @public
+ */
+export const buildApplication = async (opt) => {
+    const { log } = opt ?? {};
+    log?.log(chalk.bold('Starting to build application'));
+    // Load application manifest, package info, and environment variables
+    const { manifest, pkg, env } = await loadAppManifest({ log, manifest: opt?.manifest });
+    log?.start('loading vite config...');
+    // Load local Vite configuration for the build
+    const viteConfig = await loadViteConfig(env, pkg);
+    log?.succeed('vite config applied');
+    log?.debug('vite config:', viteConfig);
+    log?.start('🤞🏻', 'building application...');
+    log?.startNativeConsoleCapture();
+    await viteBuild(viteConfig);
+    log?.stopNativeConsoleCapture();
+    log?.succeed('build completed 😘');
+    // Output directory for the built application
+    const outDir = viteConfig.build.outDir;
+    return { pkg, manifest, outDir };
+};
+//# sourceMappingURL=app-build.js.map

package/dist/esm/bin/app-build.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"app-build.js","sourceRoot":"","sources":["../../../src/bin/app-build.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,KAAK,IAAI,SAAS,EAAE,MAAM,MAAM,CAAC;AAE1C,OAAO,KAAK,MAAM,OAAO,CAAC;AAU1B,OAAO,EAAE,cAAc,EAAE,MAAM,+BAA+B,CAAC;AAE/D,OAAO,eAAe,MAAM,gBAAgB,CAAC;AAwC7C;;;;;;;;;GASG;AACH,MAAM,CAAC,MAAM,gBAAgB,GAAG,KAAK,EACnC,GAA6B,EACI,EAAE;IACnC,MAAM,EAAE,GAAG,EAAE,GAAG,GAAG,IAAI,EAAE,CAAC;IAE1B,GAAG,EAAE,GAAG,CAAC,KAAK,CAAC,IAAI,CAAC,+BAA+B,CAAC,CAAC,CAAC;IAEtD,qEAAqE;IACrE,MAAM,EAAE,QAAQ,EAAE,GAAG,EAAE,GAAG,EAAE,GAAG,MAAM,eAAe,CAAC,EAAE,GAAG,EAAE,QAAQ,EAAE,GAAG,EAAE,QAAQ,EAAE,CAAC,CAAC;IAEvF,GAAG,EAAE,KAAK,CAAC,wBAAwB,CAAC,CAAC;IACrC,8CAA8C;IAC9C,MAAM,UAAU,GAAG,MAAM,cAAc,CAAC,GAAG,EAAE,GAAG,CAAC,CAAC;IAClD,GAAG,EAAE,OAAO,CAAC,qBAAqB,CAAC,CAAC;IACpC,GAAG,EAAE,KAAK,CAAC,cAAc,EAAE,UAAU,CAAC,CAAC;IAEvC,GAAG,EAAE,KAAK,CAAC,MAAM,EAAE,yBAAyB,CAAC,CAAC;IAC9C,GAAG,EAAE,yBAAyB,EAAE,CAAC;IACjC,MAAM,SAAS,CAAC,UAAU,CAAC,CAAC;IAC5B,GAAG,EAAE,wBAAwB,EAAE,CAAC;IAChC,GAAG,EAAE,OAAO,CAAC,oBAAoB,CAAC,CAAC;IAEnC,6CAA6C;IAC7C,MAAM,MAAM,GAAG,UAAU,CAAC,KAAK,CAAC,MAAM,CAAC;IAEvC,OAAO,EAAE,GAAG,EAAE,QAAQ,EAAE,MAAM,EAAE,CAAC;AACnC,CAAC,CAAC"}

package/dist/esm/bin/app-check.js

@@ -0,0 +1,63 @@
+import { initializeFramework, } from '../lib/framework.node.js';
+import { resolveProjectPackage } from './helpers/resolve-project-package.js';
+import { resolveAppManifest } from './helpers/resolve-app-manifest.js';
+/**
+ * Checks if the application is registered in the app store.
+ *
+ * Resolves the app package and manifest, initializes the Fusion Framework, and queries the app store.
+ *
+ * @param options - Options for environment, authentication, and logging.
+ * @returns A promise that resolves when the check is complete.
+ * @public
+ */
+export const checkApp = async (options) => {
+    const { log } = options;
+    // Resolve the application's package.json for metadata and dependencies
+    const pkg = await resolveProjectPackage(log);
+    // Resolve the application manifest for the build/production mode
+    // Manifest contains the appKey and other app metadata
+    const manifest = await resolveAppManifest({ command: 'build', mode: 'production' }, pkg, {
+        log,
+    });
+    log?.start('Initializing Fusion Framework...');
+    // Initialize the Fusion Framework with the provided environment and authentication
+    // If the auth object contains a token, use it; otherwise, use the provided auth config
+    const framework = await initializeFramework({
+        env: options.environment,
+        auth: 'token' in options.auth ? { token: options.auth.token } : options.auth,
+    });
+    log?.succeed('Initialized Fusion Framework');
+    // Create a client for the 'apps' service using service discovery
+    const appClient = await framework.serviceDiscovery.createClient('apps');
+    // Subscribe to outgoing requests for logging and debugging
+    appClient.request$.subscribe((request) => {
+        log?.info('🌎', 'Executing request to:', request.uri);
+        log?.debug('Request:', request);
+    });
+    try {
+        // Start the check for app registration in the app store
+        log?.start(`Checking if ${manifest.appKey} is registered in app store`);
+        // Send a HEAD request to check if the app is registered
+        const response = await appClient.fetch(`/apps/${manifest.appKey}`, {
+            method: 'HEAD',
+        });
+        // If the response is OK, the app is registered
+        if (response.ok) {
+            return log?.succeed('😃', `Application ${manifest.appKey} is registered in app store`);
+        }
+        // If the response is 404, the app is not registered
+        if (response.status === 404) {
+            return log?.fail('😞', `Application ${manifest.appKey} is not registered in app store`);
+        }
+        // Any other status is unexpected and should be handled as an error
+        throw new Error(`Unexpected response status: ${response.status}`);
+    }
+    catch (err) {
+        // Log and handle errors during the registration check
+        log?.fail('🙅‍♂️', 'Error checking application registration');
+        log?.error('Error checking application registration:', err);
+    }
+};
+// Export as default for compatibility with import patterns
+export default checkApp;
+//# sourceMappingURL=app-check.js.map

package/dist/esm/bin/app-check.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"app-check.js","sourceRoot":"","sources":["../../../src/bin/app-check.ts"],"names":[],"mappings":"AAEA,OAAO,EACL,mBAAmB,GAGpB,MAAM,0BAA0B,CAAC;AAElC,OAAO,EAAE,qBAAqB,EAAE,MAAM,sCAAsC,CAAC;AAC7E,OAAO,EAAE,kBAAkB,EAAE,MAAM,mCAAmC,CAAC;AAqBvE;;;;;;;;GAQG;AACH,MAAM,CAAC,MAAM,QAAQ,GAAG,KAAK,EAAE,OAAwB,EAAE,EAAE;IACzD,MAAM,EAAE,GAAG,EAAE,GAAG,OAAO,CAAC;IAExB,uEAAuE;IACvE,MAAM,GAAG,GAAG,MAAM,qBAAqB,CAAC,GAAG,CAAC,CAAC;IAE7C,iEAAiE;IACjE,sDAAsD;IACtD,MAAM,QAAQ,GAAG,MAAM,kBAAkB,CAAC,EAAE,OAAO,EAAE,OAAO,EAAE,IAAI,EAAE,YAAY,EAAE,EAAE,GAAG,EAAE;QACvF,GAAG;KACJ,CAAC,CAAC;IAEH,GAAG,EAAE,KAAK,CAAC,kCAAkC,CAAC,CAAC;IAC/C,mFAAmF;IACnF,uFAAuF;IACvF,MAAM,SAAS,GAAG,MAAM,mBAAmB,CAAC;QAC1C,GAAG,EAAE,OAAO,CAAC,WAAW;QACxB,IAAI,EAAE,OAAO,IAAI,OAAO,CAAC,IAAI,CAAC,CAAC,CAAC,EAAE,KAAK,EAAE,OAAO,CAAC,IAAI,CAAC,KAAK,EAAE,CAAC,CAAC,CAAC,OAAO,CAAC,IAAI;KAC7E,CAAC,CAAC;IACH,GAAG,EAAE,OAAO,CAAC,8BAA8B,CAAC,CAAC;IAE7C,iEAAiE;IACjE,MAAM,SAAS,GAAG,MAAM,SAAS,CAAC,gBAAgB,CAAC,YAAY,CAAC,MAAM,CAAC,CAAC;IAExE,2DAA2D;IAC3D,SAAS,CAAC,QAAQ,CAAC,SAAS,CAAC,CAAC,OAAO,EAAE,EAAE;QACvC,GAAG,EAAE,IAAI,CAAC,IAAI,EAAE,uBAAuB,EAAE,OAAO,CAAC,GAAG,CAAC,CAAC;QACtD,GAAG,EAAE,KAAK,CAAC,UAAU,EAAE,OAAO,CAAC,CAAC;IAClC,CAAC,CAAC,CAAC;IAEH,IAAI,CAAC;QACH,wDAAwD;QACxD,GAAG,EAAE,KAAK,CAAC,eAAe,QAAQ,CAAC,MAAM,6BAA6B,CAAC,CAAC;QACxE,wDAAwD;QACxD,MAAM,QAAQ,GAAG,MAAM,SAAS,CAAC,KAAK,CAAC,SAAS,QAAQ,CAAC,MAAM,EAAE,EAAE;YACjE,MAAM,EAAE,MAAM;SACf,CAAC,CAAC;QACH,+CAA+C;QAC/C,IAAI,QAAQ,CAAC,EAAE,EAAE,CAAC;YAChB,OAAO,GAAG,EAAE,OAAO,CAAC,IAAI,EAAE,eAAe,QAAQ,CAAC,MAAM,6BAA6B,CAAC,CAAC;QACzF,CAAC;QACD,oDAAoD;QACpD,IAAI,QAAQ,CAAC,MAAM,KAAK,GAAG,EAAE,CAAC;YAC5B,OAAO,GAAG,EAAE,IAAI,CAAC,IAAI,EAAE,eAAe,QAAQ,CAAC,MAAM,iCAAiC,CAAC,CAAC;QAC1F,CAAC;QACD,mEAAmE;QACnE,MAAM,IAAI,KAAK,CAAC,+BAA+B,QAAQ,CAAC,MAAM,EAAE,CAAC,CAAC;IACpE,CAAC;IAAC,OAAO,GAAG,EAAE,CAAC;QACb,sDAAsD;QACtD,GAAG,EAAE,IAAI,CAAC,OAAO,EAAE,yCAAyC,CAAC,CAAC;QAC9D,GAAG,EAAE,KAAK,CAAC,0CAA0C,EAAE,GAAG,CAAC,CAAC;IAC9D,CAAC;AACH,CAAC,CAAC;AAEF,2DAA2D;AAC3D,eAAe,QAAQ,CAAC"}

package/dist/esm/bin/app-config-publish.js

@@ -0,0 +1,89 @@
+import { HttpJsonResponseError } from '@equinor/fusion-framework-module-http/errors';
+import { initializeFramework, } from '../lib/framework.node.js';
+import { formatPath, chalk } from './utils';
+import { generateApplicationConfig } from './app-config.js';
+import { loadAppManifest } from './app-manifest.js';
+/**
+ * Publishes the application configuration to the app store for a specific build version.
+ *
+ * This function generates the application config, loads the manifest, initializes the Fusion Framework,
+ * and sends the config to the app service. Handles and logs errors for common failure scenarios.
+ *
+ * @param options - Options for config, manifest, environment, authentication, and logging.
+ * @returns A promise that resolves when publishing is complete.
+ * @throws If the build version is missing or publishing fails.
+ * @public
+ */
+export const publishAppConfig = async (options) => {
+    const { log } = options;
+    // Generate the application config using provided options and environment
+    const { config: appConfig } = await generateApplicationConfig({
+        log,
+        config: options.config,
+        env: { environment: options.environment },
+    });
+    // Load the application manifest for the specified environment
+    const { manifest: appManifest } = await loadAppManifest({
+        log,
+        manifest: options.manifest,
+        env: { environment: options.environment },
+    });
+    // Extract the build version from the manifest
+    const appVersion = appManifest.build?.version;
+    if (!appVersion) {
+        // Fail if no build version is found in the manifest
+        const error = new Error('No build version found in the manifest. Please make sure the manifest is valid.');
+        log?.fail('🤪', error.message);
+        throw error;
+    }
+    log?.start('Initializing Fusion Framework...');
+    // Initialize the Fusion Framework with the provided environment and authentication
+    const framework = await initializeFramework({
+        env: options.environment,
+        auth: options.auth,
+    });
+    log?.succeed('Initialized Fusion Framework');
+    // Create a client for the 'apps' service
+    const appClient = await framework.serviceDiscovery.createClient('apps');
+    // Subscribe to outgoing requests for logging and debugging
+    appClient.request$.subscribe((request) => {
+        log?.debug('Request:', request);
+        log?.info('🌎', 'Executing request to:', formatPath(request.uri));
+    });
+    log?.start('Publishing application config');
+    log?.info('Using environment:', chalk.redBright(options.environment));
+    try {
+        // Send a PUT request to publish the app config for the specific build version
+        const response = await appClient.json(`/apps/${appManifest.appKey}/builds/${appVersion}/config`, {
+            method: 'PUT',
+            body: appConfig,
+        });
+        log?.debug('Response:', response);
+        log?.succeed('Published application config');
+    }
+    catch (error) {
+        // Handle known HTTP errors with specific log messages
+        if (error instanceof HttpJsonResponseError) {
+            switch (error.response.status) {
+                case 410:
+                    log?.fail('🤬', `App ${appManifest.appKey} is deleted from apps-service. Please check the app key and try again.`);
+                    break;
+                case 404:
+                    log?.fail('🤬', `App ${appManifest.appKey} not found. Please check the app key and try again.`);
+                    break;
+                case 403:
+                case 401:
+                    log?.fail('🤬', 'You are not authorized to publish application config. Please check your permissions.');
+                    break;
+                default:
+                    log?.fail('🤬', 'Failed to publish application config.', `Status code: ${error.response.status}`, `Message: ${error.response.statusText}`);
+                    break;
+            }
+        }
+        // Rethrow error for upstream handling
+        throw error;
+    }
+};
+// Export as default for compatibility with import patterns
+export default publishAppConfig;
+//# sourceMappingURL=app-config-publish.js.map

package/dist/esm/bin/app-config-publish.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"app-config-publish.js","sourceRoot":"","sources":["../../../src/bin/app-config-publish.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,qBAAqB,EAAE,MAAM,8CAA8C,CAAC;AAErF,OAAO,EACL,mBAAmB,GAGpB,MAAM,0BAA0B,CAAC;AAElC,OAAO,EAAE,UAAU,EAAE,KAAK,EAAsB,MAAM,SAAS,CAAC;AAEhE,OAAO,EAAE,yBAAyB,EAAE,MAAM,iBAAiB,CAAC;AAC5D,OAAO,EAAE,eAAe,EAAE,MAAM,mBAAmB,CAAC;AAWpD;;;;;;;;;;GAUG;AACH,MAAM,CAAC,MAAM,gBAAgB,GAAG,KAAK,EAAE,OAAgC,EAAE,EAAE;IACzE,MAAM,EAAE,GAAG,EAAE,GAAG,OAAO,CAAC;IAExB,yEAAyE;IACzE,MAAM,EAAE,MAAM,EAAE,SAAS,EAAE,GAAG,MAAM,yBAAyB,CAAC;QAC5D,GAAG;QACH,MAAM,EAAE,OAAO,CAAC,MAAM;QACtB,GAAG,EAAE,EAAE,WAAW,EAAE,OAAO,CAAC,WAAW,EAAE;KAC1C,CAAC,CAAC;IAEH,8DAA8D;IAC9D,MAAM,EAAE,QAAQ,EAAE,WAAW,EAAE,GAAG,MAAM,eAAe,CAAC;QACtD,GAAG;QACH,QAAQ,EAAE,OAAO,CAAC,QAAQ;QAC1B,GAAG,EAAE,EAAE,WAAW,EAAE,OAAO,CAAC,WAAW,EAAE;KAC1C,CAAC,CAAC;IAEH,8CAA8C;IAC9C,MAAM,UAAU,GAAG,WAAW,CAAC,KAAK,EAAE,OAAO,CAAC;IAC9C,IAAI,CAAC,UAAU,EAAE,CAAC;QAChB,oDAAoD;QACpD,MAAM,KAAK,GAAG,IAAI,KAAK,CACrB,iFAAiF,CAClF,CAAC;QACF,GAAG,EAAE,IAAI,CAAC,IAAI,EAAE,KAAK,CAAC,OAAO,CAAC,CAAC;QAC/B,MAAM,KAAK,CAAC;IACd,CAAC;IAED,GAAG,EAAE,KAAK,CAAC,kCAAkC,CAAC,CAAC;IAC/C,mFAAmF;IACnF,MAAM,SAAS,GAAG,MAAM,mBAAmB,CAAC;QAC1C,GAAG,EAAE,OAAO,CAAC,WAAW;QACxB,IAAI,EAAE,OAAO,CAAC,IAAI;KACnB,CAAC,CAAC;IACH,GAAG,EAAE,OAAO,CAAC,8BAA8B,CAAC,CAAC;IAE7C,yCAAyC;IACzC,MAAM,SAAS,GAAG,MAAM,SAAS,CAAC,gBAAgB,CAAC,YAAY,CAAC,MAAM,CAAC,CAAC;IACxE,2DAA2D;IAC3D,SAAS,CAAC,QAAQ,CAAC,SAAS,CAAC,CAAC,OAAO,EAAE,EAAE;QACvC,GAAG,EAAE,KAAK,CAAC,UAAU,EAAE,OAAO,CAAC,CAAC;QAChC,GAAG,EAAE,IAAI,CAAC,IAAI,EAAE,uBAAuB,EAAE,UAAU,CAAC,OAAO,CAAC,GAAG,CAAC,CAAC,CAAC;IACpE,CAAC,CAAC,CAAC;IAEH,GAAG,EAAE,KAAK,CAAC,+BAA+B,CAAC,CAAC;IAC5C,GAAG,EAAE,IAAI,CAAC,oBAAoB,EAAE,KAAK,CAAC,SAAS,CAAC,OAAO,CAAC,WAAW,CAAC,CAAC,CAAC;IACtE,IAAI,CAAC;QACH,8EAA8E;QAC9E,MAAM,QAAQ,GAAG,MAAM,SAAS,CAAC,IAAI,CACnC,SAAS,WAAW,CAAC,MAAM,WAAW,UAAU,SAAS,EACzD;YACE,MAAM,EAAE,KAAK;YACb,IAAI,EAAE,SAAS;SAChB,CACF,CAAC;QACF,GAAG,EAAE,KAAK,CAAC,WAAW,EAAE,QAAQ,CAAC,CAAC;QAClC,GAAG,EAAE,OAAO,CAAC,8BAA8B,CAAC,CAAC;IAC/C,CAAC;IAAC,OAAO,KAAK,EAAE,CAAC;QACf,sDAAsD;QACtD,IAAI,KAAK,YAAY,qBAAqB,EAAE,CAAC;YAC3C,QAAQ,KAAK,CAAC,QAAQ,CAAC,MAAM,EAAE,CAAC;gBAC9B,KAAK,GAAG;oBACN,GAAG,EAAE,IAAI,CACP,IAAI,EACJ,OAAO,WAAW,CAAC,MAAM,wEAAwE,CAClG,CAAC;oBACF,MAAM;gBACR,KAAK,GAAG;oBACN,GAAG,EAAE,IAAI,CACP,IAAI,EACJ,OAAO,WAAW,CAAC,MAAM,qDAAqD,CAC/E,CAAC;oBACF,MAAM;gBACR,KAAK,GAAG,CAAC;gBACT,KAAK,GAAG;oBACN,GAAG,EAAE,IAAI,CACP,IAAI,EACJ,sFAAsF,CACvF,CAAC;oBACF,MAAM;gBACR;oBACE,GAAG,EAAE,IAAI,CACP,IAAI,EACJ,uCAAuC,EACvC,gBAAgB,KAAK,CAAC,QAAQ,CAAC,MAAM,EAAE,EACvC,YAAY,KAAK,CAAC,QAAQ,CAAC,UAAU,EAAE,CACxC,CAAC;oBACF,MAAM;YACV,CAAC;QACH,CAAC;QACD,sCAAsC;QACtC,MAAM,KAAK,CAAC;IACd,CAAC;AACH,CAAC,CAAC;AAEF,2DAA2D;AAC3D,eAAe,gBAAgB,CAAC"}

package/dist/esm/bin/app-config.js

@@ -0,0 +1,48 @@
+import { writeFile } from '../lib/utils';
+import { formatPath } from './utils';
+import { resolveProjectPackage } from './helpers/resolve-project-package.js';
+import { resolveAppConfig } from './helpers/resolve-app-config.js';
+/**
+ * Generates the application configuration object for the current project.
+ *
+ * This function resolves the app package, sets up the runtime environment, resolves the app config,
+ * and optionally writes the config to a file if an output path is provided. Logging is supported for
+ * debugging and progress tracking.
+ *
+ * @param options - Optional settings for logger, environment overrides, config path, and output file.
+ * @returns An object containing the generated config and the resolved package info.
+ * @throws If writing the config to file fails.
+ * @public
+ */
+export const generateApplicationConfig = async (options) => {
+    const { log } = options ?? {};
+    // Resolve the application's package.json for root and metadata
+    const pkg = await resolveProjectPackage(log);
+    // Setup the runtime environment for config resolution
+    const env = {
+        command: 'build',
+        mode: process.env.NODE_ENV ?? 'production',
+        root: pkg.root,
+        ...options?.env, // Allow overrides from options
+    };
+    // Resolve the application config using the environment and config path
+    const config = await resolveAppConfig(env, { log, config: options?.config });
+    log?.debug('config:', config);
+    // If an output path is provided, write the config to file
+    if (options?.output) {
+        log?.start('writing config to file');
+        try {
+            // Write the config as pretty-printed JSON
+            await writeFile(options.output, JSON.stringify(config, null, 2));
+            log?.succeed('config written successfully', formatPath(options.output, { relative: true }));
+        }
+        catch (error) {
+            // Log and rethrow errors encountered during file write
+            log?.fail('failed to write config');
+            throw error;
+        }
+    }
+    // Return the generated config and resolved package info for further use
+    return { config, pkg };
+};
+//# sourceMappingURL=app-config.js.map

package/dist/esm/bin/app-config.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"app-config.js","sourceRoot":"","sources":["../../../src/bin/app-config.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,SAAS,EAAE,MAAM,cAAc,CAAC;AAEzC,OAAO,EAAE,UAAU,EAAsB,MAAM,SAAS,CAAC;AAEzD,OAAO,EAAE,qBAAqB,EAAE,MAAM,sCAAsC,CAAC;AAC7E,OAAO,EAAE,gBAAgB,EAAE,MAAM,iCAAiC,CAAC;AA8BnE;;;;;;;;;;;GAWG;AACH,MAAM,CAAC,MAAM,yBAAyB,GAAG,KAAK,EAAE,OAA0C,EAAE,EAAE;IAC5F,MAAM,EAAE,GAAG,EAAE,GAAG,OAAO,IAAI,EAAE,CAAC;IAC9B,+DAA+D;IAC/D,MAAM,GAAG,GAAG,MAAM,qBAAqB,CAAC,GAAG,CAAC,CAAC;IAE7C,sDAAsD;IACtD,MAAM,GAAG,GAAe;QACtB,OAAO,EAAE,OAAO;QAChB,IAAI,EAAE,OAAO,CAAC,GAAG,CAAC,QAAQ,IAAI,YAAY;QAC1C,IAAI,EAAE,GAAG,CAAC,IAAI;QACd,GAAG,OAAO,EAAE,GAAG,EAAE,+BAA+B;KACjD,CAAC;IAEF,uEAAuE;IACvE,MAAM,MAAM,GAAG,MAAM,gBAAgB,CAAC,GAAG,EAAE,EAAE,GAAG,EAAE,MAAM,EAAE,OAAO,EAAE,MAAM,EAAE,CAAC,CAAC;IAC7E,GAAG,EAAE,KAAK,CAAC,SAAS,EAAE,MAAM,CAAC,CAAC;IAE9B,0DAA0D;IAC1D,IAAI,OAAO,EAAE,MAAM,EAAE,CAAC;QACpB,GAAG,EAAE,KAAK,CAAC,wBAAwB,CAAC,CAAC;QACrC,IAAI,CAAC;YACH,0CAA0C;YAC1C,MAAM,SAAS,CAAC,OAAO,CAAC,MAAM,EAAE,IAAI,CAAC,SAAS,CAAC,MAAM,EAAE,IAAI,EAAE,CAAC,CAAC,CAAC,CAAC;YACjE,GAAG,EAAE,OAAO,CAAC,6BAA6B,EAAE,UAAU,CAAC,OAAO,CAAC,MAAM,EAAE,EAAE,QAAQ,EAAE,IAAI,EAAE,CAAC,CAAC,CAAC;QAC9F,CAAC;QAAC,OAAO,KAAK,EAAE,CAAC;YACf,uDAAuD;YACvD,GAAG,EAAE,IAAI,CAAC,wBAAwB,CAAC,CAAC;YACpC,MAAM,KAAK,CAAC;QACd,CAAC;IACH,CAAC;IAED,wEAAwE;IACxE,OAAO,EAAE,MAAM,EAAE,GAAG,EAAE,CAAC;AACzB,CAAC,CAAC"}

package/dist/esm/bin/app-dev.js

@@ -0,0 +1,92 @@
+import { fileURLToPath } from 'node:url';
+import { fileExistsSync } from '../lib/utils/file-exists.js';
+import { resolveAppConfig } from './helpers/resolve-app-config.js';
+import { resolveProjectPackage } from './helpers/resolve-project-package.js';
+import { resolveAppManifest } from './helpers/resolve-app-manifest.js';
+import { createDevServer } from './utils/create-dev-server.js';
+/**
+ * Starts the application development server for local development.
+ *
+ * This function resolves the app package, manifest, and config, sets up the runtime environment,
+ * and launches a development server using the resolved configuration. It also attempts to resolve
+ * the portal entry point if available, and provides detailed logging for each step.
+ *
+ * @param options - Settings for environment, manifest path, config path, and logger.
+ * @returns A promise that resolves when the dev server has started.
+ * @public
+ */
+export const startAppDevServer = async (options) => {
+    const { log } = options ?? {};
+    // The portalId is currently hardcoded, but could be made configurable in the future
+    const portalId = '@equinor/fusion-framework-dev-portal';
+    // Resolve the application's package.json for root and metadata
+    const pkg = await resolveProjectPackage(log);
+    // Setup the runtime environment for the dev server
+    const env = {
+        root: pkg.root,
+        environment: 'local', // Always use 'local' for dev server
+        ...options?.env, // Allow overrides from options
+        mode: 'development', // Force development mode
+        command: 'serve', // Command is always 'serve' for dev
+    };
+    // Resolve the application manifest using the environment and manifest path
+    const appManifest = await resolveAppManifest(env, pkg, {
+        log,
+        manifestPath: options?.manifest,
+    });
+    // Resolve the application config using the environment and config path
+    const appConfig = await resolveAppConfig(env, { log, config: options?.config });
+    // Attempt to resolve the portal entry point if the portal is local
+    let portalEntryPoint;
+    const portalFilePath = fileURLToPath(import.meta.resolve(portalId));
+    if (fileExistsSync(portalFilePath)) {
+        // If the portal file exists locally, set the entry point for the dev server
+        portalEntryPoint = `/@fs${portalFilePath}`;
+    }
+    else {
+        // Otherwise, log that the portal is external and skip entry point resolution
+        log?.info(`Portal ${portalId} is external, skipping entry point resolution`);
+    }
+    log?.start('Starting app development server...');
+    // Create the dev server configuration, including portal and app settings
+    const devServer = await createDevServer(env, {
+        template: {
+            portal: {
+                id: portalId,
+            },
+        },
+        // If a local portal entry point is found, add it to the config
+        ...(portalEntryPoint
+            ? {
+                portal: {
+                    manifest: {
+                        id: portalId,
+                        build: {
+                            entrypoint: portalEntryPoint,
+                        },
+                    },
+                    // @todo - replace with real portal config when available
+                    config: {},
+                },
+            }
+            : {}),
+        app: {
+            manifest: appManifest,
+            config: appConfig,
+        },
+        server: {
+            port: options?.port || 3000, // Default to port 3000 if not specified
+            host: 'localhost', // Use localhost for local development
+        },
+    });
+    await devServer.listen();
+    log?.succeed('App development server started successfully');
+    // print the server URL for user convenience with `apps/<appKey>`
+    const protocol = devServer.config.server.https ? 'https' : 'http';
+    const host = devServer.config.server.host || 'localhost';
+    const port = devServer.config.server.port || 5173;
+    log?.info(`App development server is running at: ${protocol}://${host}:${port}/apps/${appManifest.appKey}`);
+    // Return the dev server instance for further use or testing
+    return devServer;
+};
+//# sourceMappingURL=app-dev.js.map

package/dist/esm/bin/app-dev.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"app-dev.js","sourceRoot":"","sources":["../../../src/bin/app-dev.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,aAAa,EAAE,MAAM,UAAU,CAAC;AAEzC,OAAO,EAAE,cAAc,EAAE,MAAM,6BAA6B,CAAC;AAG7D,OAAO,EAAE,gBAAgB,EAAE,MAAM,iCAAiC,CAAC;AACnE,OAAO,EAAE,qBAAqB,EAAE,MAAM,sCAAsC,CAAC;AAC7E,OAAO,EAAE,kBAAkB,EAAE,MAAM,mCAAmC,CAAC;AAGvE,OAAO,EAAE,eAAe,EAAE,MAAM,8BAA8B,CAAC;AAmC/D;;;;;;;;;;GAUG;AACH,MAAM,CAAC,MAAM,iBAAiB,GAAG,KAAK,EAAE,OAAkC,EAAE,EAAE;IAC5E,MAAM,EAAE,GAAG,EAAE,GAAG,OAAO,IAAI,EAAE,CAAC;IAE9B,oFAAoF;IACpF,MAAM,QAAQ,GAAG,sCAAsC,CAAC;IAExD,+DAA+D;IAC/D,MAAM,GAAG,GAAG,MAAM,qBAAqB,CAAC,GAAG,CAAC,CAAC;IAE7C,mDAAmD;IACnD,MAAM,GAAG,GAAe;QACtB,IAAI,EAAE,GAAG,CAAC,IAAI;QACd,WAAW,EAAE,OAAO,EAAE,oCAAoC;QAC1D,GAAG,OAAO,EAAE,GAAG,EAAE,+BAA+B;QAChD,IAAI,EAAE,aAAa,EAAE,yBAAyB;QAC9C,OAAO,EAAE,OAAO,EAAE,oCAAoC;KACvD,CAAC;IAEF,2EAA2E;IAC3E,MAAM,WAAW,GAAG,MAAM,kBAAkB,CAAC,GAAG,EAAE,GAAG,EAAE;QACrD,GAAG;QACH,YAAY,EAAE,OAAO,EAAE,QAAQ;KAChC,CAAC,CAAC;IAEH,uEAAuE;IACvE,MAAM,SAAS,GAAG,MAAM,gBAAgB,CAAC,GAAG,EAAE,EAAE,GAAG,EAAE,MAAM,EAAE,OAAO,EAAE,MAAM,EAAE,CAAC,CAAC;IAEhF,mEAAmE;IACnE,IAAI,gBAAoC,CAAC;IACzC,MAAM,cAAc,GAAG,aAAa,CAAC,MAAM,CAAC,IAAI,CAAC,OAAO,CAAC,QAAQ,CAAC,CAAC,CAAC;IACpE,IAAI,cAAc,CAAC,cAAc,CAAC,EAAE,CAAC;QACnC,4EAA4E;QAC5E,gBAAgB,GAAG,OAAO,cAAc,EAAE,CAAC;IAC7C,CAAC;SAAM,CAAC;QACN,6EAA6E;QAC7E,GAAG,EAAE,IAAI,CAAC,UAAU,QAAQ,+CAA+C,CAAC,CAAC;IAC/E,CAAC;IAED,GAAG,EAAE,KAAK,CAAC,oCAAoC,CAAC,CAAC;IAEjD,yEAAyE;IACzE,MAAM,SAAS,GAAG,MAAM,eAAe,CAAC,GAAG,EAAE;QAC3C,QAAQ,EAAE;YACR,MAAM,EAAE;gBACN,EAAE,EAAE,QAAQ;aACb;SACF;QACD,+DAA+D;QAC/D,GAAG,CAAC,gBAAgB;YAClB,CAAC,CAAC;gBACE,MAAM,EAAE;oBACN,QAAQ,EAAE;wBACR,EAAE,EAAE,QAAQ;wBACZ,KAAK,EAAE;4BACL,UAAU,EAAE,gBAAgB;yBAC7B;qBACF;oBACD,yDAAyD;oBACzD,MAAM,EAAE,EAAE;iBACX;aACF;YACH,CAAC,CAAC,EAAE,CAAC;QACP,GAAG,EAAE;YACH,QAAQ,EAAE,WAAW;YACrB,MAAM,EAAE,SAAS;SAClB;QACD,MAAM,EAAE;YACN,IAAI,EAAE,OAAO,EAAE,IAAI,IAAI,IAAI,EAAE,wCAAwC;YACrE,IAAI,EAAE,WAAW,EAAE,sCAAsC;SAC1D;KACF,CAAC,CAAC;IAEH,MAAM,SAAS,CAAC,MAAM,EAAE,CAAC;IAEzB,GAAG,EAAE,OAAO,CAAC,6CAA6C,CAAC,CAAC;IAC5D,iEAAiE;IACjE,MAAM,QAAQ,GAAG,SAAS,CAAC,MAAM,CAAC,MAAM,CAAC,KAAK,CAAC,CAAC,CAAC,OAAO,CAAC,CAAC,CAAC,MAAM,CAAC;IAClE,MAAM,IAAI,GAAG,SAAS,CAAC,MAAM,CAAC,MAAM,CAAC,IAAI,IAAI,WAAW,CAAC;IACzD,MAAM,IAAI,GAAG,SAAS,CAAC,MAAM,CAAC,MAAM,CAAC,IAAI,IAAI,IAAI,CAAC;IAClD,GAAG,EAAE,IAAI,CACP,yCAAyC,QAAQ,MAAM,IAAI,IAAI,IAAI,SAAS,WAAW,CAAC,MAAM,EAAE,CACjG,CAAC;IACF,4DAA4D;IAC5D,OAAO,SAAS,CAAC;AACnB,CAAC,CAAC"}

package/dist/esm/bin/app-manifest.js

@@ -0,0 +1,38 @@
+import { resolveAppManifest } from './helpers/resolve-app-manifest.js';
+import { resolveProjectPackage } from './helpers/resolve-project-package.js';
+/**
+ * Loads and resolves the application manifest based on the provided options.
+ *
+ * This function resolves the app package, sets up the runtime environment, and loads the manifest.
+ * Logging is supported for debugging and progress tracking. Returns the manifest, package, and environment.
+ *
+ * @param options - The options for resolving the application manifest.
+ * @returns An object containing the resolved manifest, package, and runtime environment.
+ * @throws Will throw an error if resolving the application package or manifest fails.
+ * @public
+ */
+export const loadAppManifest = async (options) => {
+    const { log } = options ?? {};
+    // Resolve the application's package.json for root and metadata
+    const pkg = await resolveProjectPackage(log);
+    log?.debug('package', pkg);
+    // Setup the runtime environment for manifest resolution
+    const env = {
+        command: 'build',
+        mode: process.env.NODE_ENV ?? 'production',
+        root: pkg.root,
+        ...options?.env, // Allow overrides from options
+    };
+    log?.debug('env:', env);
+    // Resolve the application manifest using the environment and manifest path
+    const manifest = await resolveAppManifest(env, pkg, {
+        log,
+        manifestPath: options?.manifest,
+    });
+    log?.debug('manifest:', manifest);
+    // Return the resolved manifest, package, and environment for further use
+    return { manifest, pkg, env };
+};
+// Export as default for compatibility with import patterns
+export default loadAppManifest;
+//# sourceMappingURL=app-manifest.js.map