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.
49 lines
1.6 KiB
Markdown
49 lines
1.6 KiB
Markdown
# estree-walker
|
|
|
|
Simple utility for walking an [ESTree](https://github.com/estree/estree)-compliant AST, such as one generated by [acorn](https://github.com/marijnh/acorn).
|
|
|
|
|
|
## Installation
|
|
|
|
```bash
|
|
npm i estree-walker
|
|
```
|
|
|
|
|
|
## Usage
|
|
|
|
```js
|
|
var walk = require('estree-walker').walk;
|
|
var acorn = require('acorn');
|
|
|
|
ast = acorn.parse(sourceCode, options); // https://github.com/acornjs/acorn
|
|
|
|
walk(ast, {
|
|
enter(node, parent, prop, index) {
|
|
// some code happens
|
|
},
|
|
leave(node, parent, prop, index) {
|
|
// some code happens
|
|
}
|
|
});
|
|
```
|
|
|
|
Inside the `enter` function, calling `this.skip()` will prevent the node's children being walked, or the `leave` function (which is optional) being called.
|
|
|
|
Call `this.replace(new_node)` in either `enter` or `leave` to replace the current node with a new one.
|
|
|
|
Call `this.remove()` in either `enter` or `leave` to remove the current node.
|
|
|
|
## Why not use estraverse?
|
|
|
|
The ESTree spec is evolving to accommodate ES6/7. I've had a couple of experiences where [estraverse](https://github.com/estools/estraverse) was unable to handle an AST generated by recent versions of acorn, because it hard-codes visitor keys.
|
|
|
|
estree-walker, by contrast, simply enumerates a node's properties to find child nodes (and child lists of nodes), and is therefore resistant to spec changes. It's also much smaller. (The performance, if you're wondering, is basically identical.)
|
|
|
|
None of which should be taken as criticism of estraverse, which has more features and has been battle-tested in many more situations, and for which I'm very grateful.
|
|
|
|
|
|
## License
|
|
|
|
MIT
|