Packages
Packages
| Package | Role | State |
|---|---|---|
@strict-script/compiler | The name the compiler is imported under, and its tests: texts in, texts out, with no dependency on Node or on the TypeScript compiler | The kernel, values that can be changed, resources, extern, async; writes .js, .d.ts and .js.map |
@strict-script/self | The compiler, written in strict-script, and what it wrote for itself | The lexer, the parser, the checker, what writes the JavaScript, the driver |
@strict-script/std | What compiled programs import as they run | Option, Result, the collections, the checks of the boundary |
@strict-script/cli | The command line | check, build, run |
@strict-script/site | The website: a front page, these documents and the playground, as a folder of files; not packed | Builds to dist/; the samples of its front page are judged by the compiler when it is built; the playground has the compiler inside, and nine examples that all run in the page |
@strict-script/vite | The plugin for Vite: a .sts file imported by the build | A module imported by TypeScript or by a Vue component, its declarations, its source map; a Vue component whose script is strict-script, its state in cells |
@strict-script/react | strict-script in React: a component from a setup and a view written in the language | Elements, state in cells, tested in a browser and by a test of React Native; no effects, no styles |
@strict-script/loader | A loader for webpack (and Next), a transformer for Metro (React Native) and one for Jest | Tested with webpack, with Metro and with Jest; not run inside Next |
@strict-script/angular | strict-script in Angular: the state and the logic of a component, shown as signals | Tested in an application built by Angular's command line, in a browser; the class and the template stay TypeScript |
@strict-script/lsp | The language server: an editor is told what is refused, the type under the cursor, and what may be written there | Diagnostics, hover and completion |
@strict-script/fuzz | A fuzzer of the kernel: it writes programs, asks the compiler about each and runs what it accepts | A tool of the repository, run by the CI on a fixed seed; not packed |
@strict-script/vscode | The colours of the language in VS Code, with the language server; not packed | Builds a VSIX: the grammar, and the language server with the few lines that start it |
None is published. pnpm run pack writes the first four as files under tarballs/: see In a project.
The compiler holds every rule of the language. The command line, the playground and the editor extension are adapters around it: they find texts, hand them over and show what comes back.