Skip to content
Norsk

Studio libraries

Norsk Studio’s node catalog is extended through libraries — npm packages baked into the Studio image and loaded via Studio’s server.library config list.

norsk-ctl no longer manages libraries. The Studio product authors its own server.library list via a NODE_CONFIG environment variable in its product template compose, so library selection is a property of the product template you launch:

  • On the Studio Dev product template, the library list is exposed as a STUDIO_LIBRARIES product template parameter — set it on the launch form (or with --param STUDIO_LIBRARIES=... on instance launch-template) to choose which packages the instance loads.
  • Other Studio product templates ship the library list their workflows need; there is nothing to toggle daemon-wide.

Component packages shipped inside a product template’s components/ directory are still added to server.library automatically at launch — that is the generic product template contract, independent of the Studio library list.

Where the old controls went

Section titled “Where the old controls went”

Earlier versions of norsk-ctl shipped a curated library catalog with a Settings-page card, norsk-ctl library {list,enable,disable} CLI commands, and library.* MCP tools, persisted in the daemon’s state database. All of that was retired: the daemon carries no library knowledge, and any previously persisted toggle state is dropped by a database migration on upgrade.

See also

Section titled “See also”