Extras for Weave — the fine-grained reactive, signal-native
UI framework. Additional components, extensions of existing ones, and plugins, published as a single
package: @weave-framework/extra.
Nothing is exported from the package root — every entry has its own subpath, so a consumer pays only for what it names:
import Chart from '@weave-framework/extra/components/chart';
import Metric from '@weave-framework/extra/components/metric';
import Split from '@weave-framework/extra/components/split';
import SplitPane from '@weave-framework/extra/components/split-pane';
import { tablePlugin } from '@weave-framework/extra/plugins/table';
import { compile } from '@weave-framework/extra/plugins/schema';
import NumberInput from '@weave-framework/extra/extends/number-input';| Bucket | What belongs there |
|---|---|
components/ |
New standalone components that do not exist in @weave-framework/ui |
extends/ |
Extensions of existing components — export const extend = Base (RFC 0008) |
plugins/ |
use: directives, CDK primitives, and service extensions (forms, data, router, i18n) |
Each bucket's README states its layout and rules.
The visual extras have live counterparts in the examples app (pnpm run examples), in pairs: the
recipes page is a single feature per section with its own complete source underneath, and the
other is the same surface assembled the way a real screen uses it. plugins/schema renders nothing,
so its live page is a playground: the presets are the cases the document argues about, and the
errors, the refused schemas and the coerced values are on screen to be poked at. Its other
counterparts are tests — test/schema.test.mjs asserts every decision in the document, and
test/conformance.test.mjs runs the official JSON Schema test suite over it.
@weave-framework/runtime and @weave-framework/ui (>= 3.0) are peer dependencies — this package
never bundles its own copy.
A live page for everything in here — one section per extra, imported through the package's own name
so the exports map is exercised the way a consumer resolves it.
pnpm run examplespnpm install
pnpm run typecheck
pnpm testpnpm run typecheck (plain tsc) is the check that counts. weave check does not type-check this
package's src — it reports no errors on a file containing an identifier that exists nowhere.
pnpm test builds first and runs node --test against dist/, with no framework and no config.
Testing the built output rather than the source is deliberate: it is what consumers get, so a build
that drops a module fails here rather than at someone else's install. See
test/README.md for what earns a test.
pnpm run build
pnpm publish --access publicpnpm publish, not npm publish. The manifest's exports, main and types point at
src/*.ts so the repo and the examples resolve TypeScript directly; publishConfig swaps them for
dist/*.js at publish time. pnpm applies those overrides — npm 11.17 does not. Published with
npm, the tarball ships dist (per files) while its manifest still points at src, so every
consumer import resolves to a file that is not in the package.
Verify before publishing, rather than trusting it:
pnpm pack --pack-destination /tmp && tar -xzOf /tmp/weave-framework-extra-*.tgz package/package.jsonThe exports in that output must read ./dist/….
MIT © Aidas Josas