dtoro
d4d99a7473
Problem: the hexagonal refactor churns the backend tree for nine more phases; the UI delivery stack (web/ SPA, cmd/desktop Wails wrapper, compose/web image) must move to its own repo first so doc/layout rewrites land once on a backend-only tree. Change: - New repo git.hubris.network/dtoro/oikos-web (v0.33.0): web/, desktop/ (updateURL repointed to oikos-web releases), compose/, own CI (web + desktop jobs), own deploy script (CI-green gate, TOCTOU guard, version-tagged images, prune-to-3), own webhook receiver on :9798 + launchd unit, own compose project publishing the same 8091:80. - Cutover executed on mac-mini in order: oikos stack's web service stopped+removed, oikos-web project brought up on 8091; outer Caddy untouched (targets the published port) — serving + Authentik flow + /wails 404 quirk verified post-cutover. - Stripped from oikos: web/, cmd/desktop/, compose/web/, desktop CI workflow, ci.yml web job, Makefile ui/desktop/desktop-package/install targets, the compose web service, oikos-web from deploy.sh's fallback prune list; wails + go-keyring dropped from go.mod, vendor synced. - README / CONTRIBUTING / AGENTS.md / .agents dev+operations docs now point at the new repo; mbse + mascot design docs carry a path note. Risk: production SPA serving depends on the new pipeline now; rollback is versioned-image re-up of the old web service from a pre-split checkout (port 8091). Desktop builds installed before the split still check dtoro/oikos releases — one manual reinstall, noted in the oikos-web release notes. Verification: go vet, make test (race), make generate-check, golangci (no new findings; baseline down 400→365); post-cutover curls — localhost:8091 200, /wails/runtime.js 404, outer Caddy 302 Authentik.
112 lines
2.4 KiB
Markdown
112 lines
2.4 KiB
Markdown
# CSS Tokenizer <img src="https://cssdb.org/images/css.svg" alt="for CSS" width="90" height="90" align="right">
|
|
|
|
[<img alt="npm version" src="https://img.shields.io/npm/v/@csstools/css-tokenizer.svg" height="20">][npm-url]
|
|
[<img alt="Build Status" src="https://github.com/csstools/postcss-plugins/actions/workflows/test.yml/badge.svg?branch=main" height="20">][cli-url]
|
|
[<img alt="Discord" src="https://shields.io/badge/Discord-5865F2?logo=discord&logoColor=white">][discord]
|
|
|
|
Implemented from : https://www.w3.org/TR/2021/CRD-css-syntax-3-20211224/
|
|
|
|
## API
|
|
|
|
[Read the API docs](./docs/css-tokenizer.md)
|
|
|
|
## Usage
|
|
|
|
Add [CSS Tokenizer] to your project:
|
|
|
|
```bash
|
|
npm install @csstools/css-tokenizer --save-dev
|
|
```
|
|
|
|
```js
|
|
import { tokenizer, TokenType } from '@csstools/css-tokenizer';
|
|
|
|
const myCSS = `@media only screen and (min-width: 768rem) {
|
|
.foo {
|
|
content: 'Some content!' !important;
|
|
}
|
|
}
|
|
`;
|
|
|
|
const t = tokenizer({
|
|
css: myCSS,
|
|
});
|
|
|
|
while (true) {
|
|
const token = t.nextToken();
|
|
if (token[0] === TokenType.EOF) {
|
|
break;
|
|
}
|
|
|
|
console.log(token);
|
|
}
|
|
```
|
|
|
|
Or use the `tokenize` helper function:
|
|
|
|
```js
|
|
import { tokenize } from '@csstools/css-tokenizer';
|
|
|
|
const myCSS = `@media only screen and (min-width: 768rem) {
|
|
.foo {
|
|
content: 'Some content!' !important;
|
|
}
|
|
}
|
|
`;
|
|
|
|
const tokens = tokenize({
|
|
css: myCSS,
|
|
});
|
|
|
|
console.log(tokens);
|
|
```
|
|
|
|
### Options
|
|
|
|
```ts
|
|
{
|
|
onParseError?: (error: ParseError) => void
|
|
}
|
|
```
|
|
|
|
#### `onParseError`
|
|
|
|
The tokenizer is forgiving and won't stop when a parse error is encountered.
|
|
|
|
To receive parsing error information you can set a callback.
|
|
|
|
```js
|
|
import { tokenizer, TokenType } from '@csstools/css-tokenizer';
|
|
|
|
const t = tokenizer({
|
|
css: '\\',
|
|
}, { onParseError: (err) => console.warn(err) });
|
|
|
|
while (true) {
|
|
const token = t.nextToken();
|
|
if (token[0] === TokenType.EOF) {
|
|
break;
|
|
}
|
|
}
|
|
```
|
|
|
|
Parser errors will try to inform you where in the tokenizer logic the error happened.
|
|
This tells you what kind of error occurred.
|
|
|
|
## Goals and non-goals
|
|
|
|
Things this package aims to be:
|
|
- specification compliant CSS tokenizer
|
|
- a reliable low level package to be used in CSS parsers
|
|
|
|
What it is not:
|
|
- opinionated
|
|
- fast
|
|
- small
|
|
|
|
[cli-url]: https://github.com/csstools/postcss-plugins/actions/workflows/test.yml?query=workflow/test
|
|
[discord]: https://discord.gg/bUadyRwkJS
|
|
[npm-url]: https://www.npmjs.com/package/@csstools/css-tokenizer
|
|
|
|
[CSS Tokenizer]: https://github.com/csstools/postcss-plugins/tree/main/packages/css-tokenizer
|