Guides

Before you start#

These guides describe tasks across the three stages of the CDN. They rely on the delivery, management and realtime references for exact names, and they keep each known limit next to the step it affects.

Each guide states its own availability. A guide marked Planned describes an approved workflow from its contracts; nobody has yet run it end to end against a published service, and the guide says so where it matters.

Pages#

• Publish Beyond source to npm — Publish a package as Beyond source so that the CDN recognizes it and compiles its public modules through Packages.
• Publish a precompiled distribution — Compile your package before publishing and declare it as a distribution, so that the CDN delivers your outputs instead of compiling your sources.
• Use ordinary npm packages and React — Depend on packages that know nothing about Beyond, such as React, and understand how peers, versions and unsupported inputs are handled.
• Widgets and view frameworks — How Beyond widgets written with React 19, Vue, Svelte or plain HTML are prepared and delivered by the CDN: packages compiled by the bundler they declare, framework controllers, styles adopted inside each widget's shadow root, and the shared stylesheet of a package.
• Backend targets — Prepare a backend target, read its artifact closure and frozen resolution, and run it in an environment of your own. The CDN never runs it.
• Same URL, local and CDN — Write a consumer once and point it at a local Dev Server or at the CDN by changing a single base origin, and know the differences you must expect.
• Troubleshooting — Start from the symptom: a module answers 404, a release never becomes ready, a job waits or stops, access is refused, or events stop arriving.
• The applications of a Beyond project — Arrive in CDN administration from Beyond Projects, register an application for the project, add an application that already exists, read the Project panel of an application and release it from its project.