@webdyne/webdyne-zeroperl-5.44.0

This package contains the qualified ZeroPerl WebAssembly runtime for Perl 5.44.0, WebDyne, WebDyne::PAGI, PAGI::Tools, their required runtime and static-XS dependencies, a provider-neutral PAGI runtime, and the default Cloudflare adapter needed to serve a WebDyne PSP application.

Package version 1.0.16 corresponds to WebDyne build 16. The runtime is zeroperl-webdyne-5.44.0-1.0.16.wasm. The pre-Asyncify reactor and full attribution source archive are diagnostic build artifacts and are not included in npm.

The manifest records build provenance and hashes; not every build artifact is shipped in this package. THIRD-PARTY-LICENSES.txt contains the reviewed runtime licence and attribution texts. Full supporting evidence is available from the matching GitHub Release. See THIRD-PARTY-NOTICES.md for scope, the archive link and checksum. The runtime source is MIT-licensed; embedded components retain their own licenses.

Place the complete application tree in app/. A minimal project only needs package.json and app/app.psp; Cloudflare configuration is generated when the project does not provide its own wrangler.jsonc.

npm init
npm install @webdyne/[email protected]
npx webdyne-cloudflare init
npm run dev

Use webdyne-cloudflare check for a Wrangler dry run, webdyne-cloudflare dev for local development, and webdyne-cloudflare deploy for a checked deployment. The package includes its tested Wrangler version. Installation has no deployment side effects.

The explicit init command adds npm scripts for build, check, dev, deploy, destroy, login, logout, and whoami, retaining existing scripts. It sets webdyne.static: false and creates a root .assetsignore containing *.psp, *.pm, *.pl, and *.conf unless the file already exists. Use npm run login, npm run whoami, then npm run deploy to publish. Use npm run destroy to delete the configured Worker. Type the full Yes at the local confirmation (blank means No), then confirm Wrangler's named target. Destroy requires an interactive terminal, rejects confirmation-bypass flags, and uses deployment configuration without building the application. Rerun npx webdyne-cloudflare init after upgrading to add the new npm script.

When the application root contains .assetsignore, the CLI automatically passes --assets with that directory to Wrangler. Public assets are omitted from the application VFS; ignored files remain available to Perl. Add patterns for any data or templates Perl must read. Patterns are reread on every build. Only the root ignore file is supported by Wrangler; nested ignore files and misspelled .assetignore files produce an actionable error. Root patterns can match subdirectories. Existing explicit --assets DIR arguments take precedence; VFS filtering uses that directory's root ignore file. Without a root ignore file, VFS packaging remains unchanged. Automatic assets arguments override an assets directory in a custom Wrangler configuration; use explicit --assets to choose another root. Custom configurations remain responsible for WEBDYNE_STATIC=0.

Initialization accepts --app-directory DIR (alias --document-root), --entry FILE, --output DIR, --library DIR, and --wrangler-config FILE, and saves those settings. The default source root is webdyne.appDirectory or app; the runtime VFS root stays /app. Generated output must be outside the assets root. dev builds once before Wrangler starts; rerun npm run build after changing server-side files or ignore rules, or restart npm run dev.

Custom Wrangler configurations must include the enable_request_signal compatibility flag so disconnected SSE sessions stop promptly. Generated configurations include it automatically.

Explicit webdyne.perlLibrary / --library trees are packaged unchanged by Node, without requiring host Perl. Set webdyne.perlLibraryOptimize: true to opt them into staging optimisations. Explicit trees override managed libraries; later explicit roots win. Symlinks, special entries and native binaries are rejected; file contents and relative paths are preserved, with normalised tar metadata. File/directory collisions fail instead of deleting a tree.

Npm extension and CPAN libraries always use managed staging, requiring host Perl 5.18 or newer. A filesystem-only preflight checks for Perl on PATH; the Perl helper diagnoses missing or broken core modules at startup with installation guidance. Default webdyne.perlMinify: "auto" uses Perl::Tidy 20260826 if available; otherwise it warns, records the skipped minification, and continues the other staging optimisations. Install the optional formatter with cpanm Perl::Tidy@20260826. Set webdyne.perlMinify: true to require that version, or false to retain source formatting. Errors during formatting still fail the build. The minification setting alone does not opt explicit libraries into staging. Apps without managed libraries build with Node alone. The helper excludes installers and host artifacts, preserves application overrides, and reports per-file decisions in .webdyne/perl-library-report.json. Removed POD remains in the archive's /perl5/PERL-LIBRARY-DOCUMENTATION.txt; net size figures include it. See the staging helper documentation.

Portable settings belong below package.json.webdyne. Use appDirectory to override the source app/ directory, entry to override app.psp, static: false to disable static-file serving, or perlLibrary for one or more Pure-Perl library trees. The application always mounts at VFS /app. A root cpanfile is installed automatically into the cached .webdyne/cpan tree; commit cpanfile.snapshot for reproducible dependencies. Native Perl extensions are rejected because host binaries cannot execute inside the Wasm runtime. Runtime helpers and dependencies use /perl5, while /tmp is writable and exposed to Perl as TMPDIR=/tmp.

Optional provider packages are direct dependencies enabled through webdyne.extensions. The build reads their exported declarative manifests, adds their Pure-Perl files to /perl5/lib, and statically imports the selected Cloudflare adapters. Every regular file below the configured application directory is recursively included in VFS /app.