Skip to content

node-web-components

UI library and Storybook

node-web-components

Public library to consolidate reusable components, browsable Storybook and auditable distribution without depending on exposure of the private workspace.

5

named technologies

3

documented commands

3

linked surfaces

Context

docs · active

Public Web Components library with Storybook, multiframe wrappers and auditable npm distribution.

Workspace: projects/node-web-components

  • TypeScript
  • Vite
  • Storybook
  • Lit
  • npm

Delivery

Focus and primary signals

Focus
  • reusable components
  • public showcase
  • auditable release flow
Outcomes
  • public Storybook
  • accessible npm package
  • typed central catalog

Highlights

Why this case matters

  • typed catalog with deterministic audit
  • public Storybook showcase with family-based explorers
  • release manifest for npm with mandatory human review

Capabilities

Connected domains

  • Full stack product
  • Architecture and contracts
  • Observability and operations

Narrative references: github-profile, mozgbrasil.github.io

Commands

Suggested operational path

Local Storybooknpm run storybook

start the navigable showcase for component inspection

Storybook buildnpm run build:storybook

generate the static surface published on GitHub Pages

Release manifestnpm run release:manifest

document public metadata, gates and operational policy for the package

Maintenance

Notes for coherent evolution

  • public package metadata must not point to the private workspace
  • central catalog, Storybook and release manifest need to evolve together
  • publishing closes with human review and no automatic agent git push

Architecture, full stack, platform engineering, automation and observability.