How techniq/layerstack works
Project Type and Purpose
• This is a pnpm‐based monorepo hosting a suite of open‐source Svelte libraries and utilities (“svelte-actions,” “svelte-stores,” “svelte-table,” a Tailwind plugin, generic “utils”) plus a SvelteKit documentation site (“sites/docs”).
• Purpose: provide composable actions/stores/themes for Svelte apps, bundled with automated CI/CD to build, test, publish each package to npm, and deliver a live docs site.
File Structure Analysis
• Root
– pnpm-workspace.yaml ties all packages and docs into one workspace
– .github/workflows: CI (lint/test/build), release (npm publish), preview and prod deploy pipelines
– package.json: workspace scripts (build:all, test:all, docs:build)
• packages/*
– Each folder (svelte-actions, svelte-stores, svelte-table, tailwind, utils) follows the same substructure: src/lib → TypeScript sources, tsconfig*.json, vite.config.js, CHANGELOG.md, LICENSE, package.json
– Tests co-located with source (e.g. .test.ts files)
• sites/docs
– SvelteKit app (src/routes for dynamic docs pages, mdsvex + plugins, Vite build, Tailwind, static assets)
– Pulls in the workspace packages as dependencies to render live examples and API docs
• CI/CD config
– build-preview/deploy-preview: preview docs on PRs
– deploy-prod: publish docs site to production host or GitHub Pages
– release.yml: on tag push, build/test each package, bump version, and publish to npm
README Insights
• LayerStack umbrella brand for libraries; companion projects (LayerChart, Svelte UX).