API stability
The v1 public surface follows semantic versioning across the core, controller, renderer, documented subpaths, Web Component, and official wrappers.
Stable public contracts
#Documented types, state fields, methods, callbacks, events, attributes, CSS properties, package exports, and wrapper inputs/outputs are compatibility commitments.
Safe evolution
#Minor releases may add optional fields, methods, modules, or features. Breaking removals and incompatible behavior require a major release and migration notes.
Consumer checks
#Pin versions where release control matters, run TypeScript and browser tests during upgrades, and avoid private DOM classes or internal runtime variables.
Keep public imports explicit
#This recipe focuses on the integration pattern. Replace application-specific values and callbacks with your own data and services.
import { DataTable } from 'wts-data-table';
import { createDataTableStateStorage } from 'wts-data-table/persistence';
import { selectionFeature } from 'wts-data-table/features/selection';
// Avoid undocumented deep paths and private DOM internals.The framework quick start includes install commands, a typed data file, and the component that renders it.
Go to the quick start →Ready to try it with real data?
Explore configurable examples ↗