Packages, modules and what you develop

Read the packages and public modules Workspace detected, see which build, choose explicitly what is in development, and create files, modules and packages with the assistants. Page, widget and layout assistants are not available.

  • Availability: Experimental
  • Evidence: Recorded run
  • How-to guide

Before you start

Your environment must be Ready. The words package, public module and bare import are defined in Develop with Beyond.

What is detected for you

Packages lists the packages of the project and their public modules. Nothing is configured there: "Packages and dependencies are shown as Packages detected them from the code." A module reads builds, does not build or not built yet, per platform, and Show what it reaches lists the other modules of the project it imports. A project with none says "No public modules": "A package exposes modules through the exports of its package.json."

Diagnostics shows the Last build and the Modules that do not build, or "Every public module builds." Messages are the text the compiler delivers: "Packages reports these as text, without a file position to jump to."

Choose what you develop

What is in development is served from your environment. Everything else comes from the CDN at its published version.

  • Until somebody chooses, the panel says "Nobody has selected yet, so every package is in development."
  • After a choice: "Only what is selected below is served from this environment; the rest comes from the CDN."
  • "Opening or editing a file never changes this." Only the controls in In development do: Whole package, Develop on one module, and Forget the selection, which goes back to every package.

If the panel says "This Dev Server version does not support choosing what is in development.", the choice does not exist there; it is not an empty selection. A selected name that left the project is reported: "Selected but no longer in the workspace:".

A package that is not in development must have been published to the CDN at the version in its package.json, or the preview has no address for it.

Create with an assistant

New… opens Create: "These forms write real files in your working copy. They never replace an existing file." They are forms, not Codex.

Assistant Asks for Writes
File Path An empty file. "A file is not a public module. To expose code to other packages, create a module."
Module Package, Public subpath, optional Platforms The entry point, and its entry in the exports of the package. "An existing export is never replaced." module.json is written only when you choose a platform
Package Package name, Directory, Version package.json with its exports and bundler, the first entry point, and the directory added to beyond.json

A refusal names its reason and writes nothing, for example "The package already exports {subpath}. A public subpath is never replaced." or "beyond.json already lists {directory}." If a group of files stops part way: "Stopped part way. Files already written stay; the rest were not written."

Next action

Read Packages and public modules for the rules a module must keep.