stnd.buildSTANDARD MANUAL2026-07-15

@stnd/views

@stnd/views

Shared UI views and application-level components for the Standard Ecosystem.

Important

There’s no package.json here, so @stnd/views isn’t a real importable name; nothing in the repo currently imports these two files at all.

@stnd/views provides full-screen or modular UI views built with Svelte 5. These views are designed to be used as parts of larger applications, such as within the @stnd/launcher command palette or as dedicated pages.

Two full-screen Svelte views (a file navigator, a settings page) that were meant as reference implementations for the launcher’s “view” system — see @stnd/launcher‘s README for what a “view” is.

Available Views

A file-explorer-style view for navigating and managing hierarchical content.

  • Features: Breadcrumb navigation, file list, preview support, and search integration.

Settings View (SettingsView.svelte)

A comprehensive settings management interface.

  • Features: Tabbed organization, form validation, real-time preview of theme changes, and secure credential handling.

Usage

There’s no package to import from yet (see ELI5 above). If you want to use one of these views today, copy the file or import it by relative path from wherever you’re using it — there’s no stable public entry point.

Integration

These views are optimized for use within the Standard Launcher system, but can also be used as standalone components in any Svelte 5 application.

Notes / Observations

  • @stnd/launcher/launcher.ts used to import both files via
    ./views/NavigatorView.svelte — a relative path that doesn’t exist inside packages/launcher/ (the files live here, in packages/views/, a sibling package). Confirmed dead: neither imported binding was referenced anywhere else in that file, so the bundler silently tree-shook the broken import away instead of failing the build. Removed those two dead import lines from launcher.ts while doing this README pass.

Todo

Part of the Road to Public Release (Phase 1). Rolls up into the project board.

  • [ ] Decide: package or fold? @stnd/views has no package.json, so it is
    not importable as @stnd/views — it’s consumed by relative path. Either give it a real package.json or fold its two Svelte views into @stnd/launcher. Recommendation: fold — two files don’t justify a package, and nothing currently wires them up as live views anyway.