Manual packaging for Forge functions and UI Kit modules now in Preview

Manual packaging for Forge functions and UI Kit modules has progressed from the Early Access Program (EAP) to Preview. Manual packaging lets you bypass the fixed version of Webpack bundled within the Forge CLI and upload your code directly from specified directories without modification.

What's changing

Manual packaging is now suitable for production environments, and you no longer need to sign up for the EAP to use it. With manual packaging, you can:

• Use a different compiler or TypeScript version.
• Use alternative bundlers (such as Vite or Esbuild) or no bundler at all.
• Include and call WebAssembly in your application.
• Require data files or depend on packages that do.
• Reduce application size by sharing dependencies across multiple functions.

What you need to do

• If you were already using manual packaging during the EAP, no changes are required.
• To get started, set bundler: manual@2026 and a path in the app.package section of your manifest for functions, or on individual UI Kit resources.
• For details and examples, see Packaging and the Packaging standard.