0015. Packages under the @nascencestudio scope
- Status: Accepted
- Date: 2026-10-06
Context
Section titled “Context”The project is published by the user’s business, Nascence Studio, and now has
a second package (the media library). The plugin was @tapestry/studiocms.
Decision
Section titled “Decision”- All packages use the npm scope
@nascencestudio:@nascencestudio/tapestry(was@tapestry/studiocms) and@nascencestudio/medialibrary. Directories staypackages/tapestryandpackages/medialibrary. - The StudioCMS plugin identifier follows the package name, so Tapestry’s
dashboard page is now
/dashboard/plugins@nascencestudio/tapestry. - Saved toolbar settings move to row
@nascencestudio/tapestry-toolbars; the old row (@tapestry/studiocms-toolbars) is still read when the new one doesn’t exist. - Older devlog entries keep the old name (history).
Consequences
Section titled “Consequences”- Publishing to npm needs the
@nascencestudioorganization on npmjs.com (free for public packages), and publishing with provenance (roadmap, Phase 5). - Site code imports
@nascencestudio/tapestry,@nascencestudio/tapestry/page,…/AdminBar.astro,…/RichText.astro, and@nascencestudio/medialibrary.
Source: docs/decisions/0015-nascence-studio-namespace.md (view on GitHub)