@uipath/packager-tool-functions-browser 0.0.0-stage → 1.204.0-preview.256

package/LICENSE.txt

@@ -0,0 +1,3 @@
+© 2026 UiPath
+Use of this product is subject (a) to the applicable licensing agreement available: https://www.uipath.com/legal/trust-and-security/legal-terms#content-1 and, (b) for paid products listed here https://licensing.uipath.com/: the licensing agreement agreed between you and UiPath.
+(UiPath means UiPath SRL with headquarters at 4 Vasile Alecsandri Str. and 11 Constantin Daniel Str., Building A, floors 5 and 6, District 1, Bucharest 010639, Romania and UiPath Inc. with principal place of business: One Vanderbilt Avenue, 60th Floor, New York, NY 10017)

package/README.md

@@ -1,3 +1,28 @@
-# Temporary Holding Version
+# @uipath/packager-tool-functions-browser
 
-This version is a temporary placeholder for this package. An operational version to replace this has been submitted for review and is awaiting a staged release.
+Browser packager tool for `ProjectType.Function`. It packs Functions projects through the UiPath Remote Agent, in the same Orchestrator job as the solution's RPA projects.
+
+## Why
+
+The local `FunctionsTool` (`@uipath/packager-tool-functions`) runs in the browser, but it can only ship the `entry-points.json` and `bindings_v2.json` already in the snapshot. Generating them from the sources, as `uip function pack` does, needs Node, TypeScript and a real disk. When those files are stale, the pack still succeeds, but the deployed function has the wrong HTTP triggers. The Remote Agent can run the generator.
+
+## Usage
+
+Register it **instead of** `FunctionsToolFactory`. Both claim `Function`, and the first registration of a type wins:
+
+```ts
+import { RemoteFunctionsToolFactory } from "@uipath/packager-tool-functions-browser";
+import { WorkflowCompilerToolFactory } from "@uipath/packager-tool-workflowcompiler-browser";
+
+toolsFactoryRepository.registerProjectToolFactory(new RemoteFunctionsToolFactory());
+toolsFactoryRepository.registerProjectToolFactory(new WorkflowCompilerToolFactory());
+```
+
+Both factories use the shared executor from `@uipath/packager-remote-agent-browser`, so Function and RPA projects pack in one agent job. Set `functionsPackagerVersion` on the pack options to pin the packager the agent restores.
+
+Only pack goes to the agent. A Functions project has nothing to validate or clean up, so validate and cleanup succeed locally and tell the shared executor to skip the project (`skipAsync`): the RPA projects' job does not wait for it and carries no `FunctionProjects`, and a Function-only solution starts no job. Restore and build are local no-ops.
+
+## Requirements
+
+- A Remote Agent that packs `FunctionProjects`. An older one ignores the list and packs only the RPA projects; each Function project then fails with "The remote agent returned no package for …" when the result arrives.
+- The same pack options remote RPA packing needs: `connection` (`cloudUrl`, `accessToken`, `folderId`) and `downloadUrl`.

package/dist/index.d.ts

@@ -0,0 +1 @@
+export { RemoteFunctionsToolFactory } from "./remote-functions-tool-factory.js";

package/dist/index.js

@@ -0,0 +1,32 @@
+// src/remote-functions-tool-factory.ts
+import {
+  RemoteAgentProjectToolFactory
+} from "@uipath/packager-remote-agent-browser";
+import {
+  ProjectTypes
+} from "@uipath/solutionpackager-tool-core";
+
+// src/remote-functions-tool.ts
+import { RemoteAgentProjectTool } from "@uipath/packager-remote-agent-browser";
+import {
+  ensureProjectId
+} from "@uipath/solutionpackager-tool-core";
+
+class RemoteFunctionsTool extends RemoteAgentProjectTool {
+  async resolveProjectIdAsync(options) {
+    return options.projectStorageId || await ensureProjectId(options.projectPath, this.fileSystem);
+  }
+}
+
+// src/remote-functions-tool-factory.ts
+class RemoteFunctionsToolFactory extends RemoteAgentProjectToolFactory {
+  supportedTypes = [ProjectTypes.Function];
+  createTool(fileSystem, logger, bundleExecutor, context) {
+    return new RemoteFunctionsTool(fileSystem, logger, bundleExecutor, context);
+  }
+}
+export {
+  RemoteFunctionsToolFactory
+};
+
+//# debugId=57F0E44E9DE9F84A64756E2164756E21

package/dist/remote-functions-tool-factory.d.ts

@@ -0,0 +1,26 @@
+import { type IRemoteAgentBundleExecutor, RemoteAgentProjectToolFactory } from "@uipath/packager-remote-agent-browser";
+import { type IFileSystem, type IToolLogger, type ProjectOperationContext, type ProjectTool, type ProjectType } from "@uipath/solutionpackager-tool-core";
+/**
+ * Factory for the browser Functions tool that packs through the Remote Agent.
+ * Handles projects with projectType "Function".
+ *
+ * It claims the same type as `FunctionsToolFactory` from
+ * `@uipath/packager-tool-functions`, and the first registration of a type
+ * wins, so a consumer registers one or the other. Its tools share the remote
+ * agent bundle executor with `WorkflowCompilerToolFactory` from
+ * `@uipath/packager-tool-workflowcompiler-browser`, so a solution's Function
+ * and RPA projects pack in one agent job.
+ *
+ * Opt-in: a consumer that registers the local `FunctionsToolFactory` instead
+ * keeps packing Function projects in the browser. No robot is needed: the
+ * agent runs as a serverless job unless the pack targets a local robot, the
+ * same as for RPA projects.
+ *
+ * Needs a Remote Agent that packs `FunctionProjects`. An older one ignores
+ * that list; each Function project then fails when the result arrives without
+ * its package.
+ */
+export declare class RemoteFunctionsToolFactory extends RemoteAgentProjectToolFactory {
+    readonly supportedTypes: readonly ProjectType[];
+    protected createTool(fileSystem: IFileSystem, logger: IToolLogger, bundleExecutor: IRemoteAgentBundleExecutor, context?: ProjectOperationContext): ProjectTool;
+}

package/dist/remote-functions-tool.d.ts

@@ -0,0 +1,20 @@
+import { RemoteAgentProjectTool } from "@uipath/packager-remote-agent-browser";
+import { type IProjectPackOptions } from "@uipath/solutionpackager-tool-core";
+/**
+ * Browser Functions tool that packs through the Remote Agent.
+ *
+ * The browser cannot generate a Functions project's `entry-points.json` and
+ * `bindings_v2.json` from its sources (that needs Node, TypeScript and a real
+ * disk), so the local `FunctionsTool` ships whatever manifests are in the
+ * snapshot. This tool hands the project to the shared remote-agent bundle
+ * executor instead: it is packed by the agent in the same Orchestrator job as
+ * the solution's RPA projects, and the package comes back through the same
+ * bucket.
+ *
+ * Only pack goes to the agent. A Functions project has nothing to validate or
+ * clean up (the local `FunctionsTool` does neither), so validate and cleanup
+ * succeed here and tell the bundle to skip the project.
+ */
+export declare class RemoteFunctionsTool extends RemoteAgentProjectTool {
+    protected resolveProjectIdAsync(options: IProjectPackOptions): Promise<string>;
+}

package/package.json

@@ -1,6 +1,35 @@
 {
-  "name": "@uipath/packager-tool-functions-browser",
-  "version": "0.0.0-stage",
-  "stub": true,
-  "description": "Temporary package placeholder for staged publishing"
-}
+    "name": "@uipath/packager-tool-functions-browser",
+    "version": "1.204.0-preview.256",
+    "description": "UiPath Functions tool - browser implementation that packs through the Remote Agent",
+    "type": "module",
+    "exports": {
+        ".": "./dist/index.js"
+    },
+    "repository": {
+        "type": "git",
+        "url": "https://github.com/UiPath/cli.git",
+        "directory": "packages/packager/packager-tool-functions-browser"
+    },
+    "publishConfig": {
+        "registry": "https://registry.npmjs.org/"
+    },
+    "types": "./dist/index.d.ts",
+    "files": [
+        "dist"
+    ],
+    "author": "UiPath",
+    "license": "SEE LICENSE IN LICENSE.txt",
+    "peerDependencies": {
+        "@uipath/packager-remote-agent-browser": "1.204.0",
+        "@uipath/solutionpackager-tool-core": "1.205.0"
+    },
+    "devDependencies": {
+        "@uipath/packager-remote-agent-browser": "1.204.0",
+        "@uipath/solutionpackager-tool-core": "1.205.0",
+        "@vitest/coverage-v8": "^4.1.11",
+        "typescript": "^7.0.2",
+        "vitest": "^4.1.11"
+    },
+    "gitHead": "63740c6cbb7ff282fa9118cc16a148eb030b245f"
+}