lens-package-toolkit

Use IPackageActions.exportScript for script custom components (.lsc) and IPackageActions.exportPackage for folder packages (.lspkg), passing an absolute destination path and ExportOptions. Set ExportOptions.packagePolicy to control whether consumers can unpack or view the archive.

A .lsc archive has a ScriptAsset as its primary asset, where the script itself is the component. A .lspkg has a NativePackageDescriptor (package.native) as its primary asset and bundles a folder of assets. Both live under Packages/ after install.

Assign a fresh new Editor.Assets.Version(major, minor, patch, prerelease) to the descriptor or script — mutating fields in place does not persist. Then call model.project.save() and re-export the archive so consumers see the update.

Unpacking fails when the package was exported with PackagePolicy CannotBeUnpacked (0) or CannotBeUnpackedTransparent (2). Consumers cannot unlock it; only packages exported with CanBeUnpacked or CanBeUnpackedTransparent can be unpacked.

Yes. Packed packages extract contents to the project Cache directory under the package meta UUID, which you can read directly with filesystem tools. You can also walk getNativePackageItems to discover the inner file tree without mutating the package.

A setup script is JavaScript stored in the descriptor that returns an instantiate(asset, scene, target, instantiator) function, run when the package is dragged into a scene or installed. If empty, Lens Studio falls back to default instantiation behavior.