tmu
fe9d59f8d4
The publish job re-ran npm ci + build from scratch, discarding the output that check, test:ci and publint had already gated, and paying the build twice on a tag push. Upload dist/ as an artifact from build and download it in publish instead. npm ci stays for the publint/attw binaries; only the redundant rebuild is gone.
103 lines
7.4 KiB
Plaintext
103 lines
7.4 KiB
Plaintext
Tasks
|
|
|
|
Backlog and tracking for tiny-pattern-ts. Managed in vscode-todotasks format.
|
|
|
|
---
|
|
|
|
Setup:
|
|
✔ Establish release CI workflow: post-tag checks + npm publish after release tag push => pi --session 01a06e72-e61e-7327-b3e9-3e11749a523f @high @done (9/11/2026, 12:37:35 AM)
|
|
☐ Add gitea release page in CI @high
|
|
☐ Split off template into separate package => pi --session 01a07dde-7050-7054-bb36-1606d7eb2bc3 @high
|
|
☐ Make the pi-lsp install reproducible
|
|
- `.pi/npm/.gitignore` is `*` / `!.gitignore`, so only `.gitignore` is committed; `.pi/npm/package.json` and `package-lock.json` are untracked
|
|
- the README insists `@spences10/pi-lsp` is "pinned to 0.0.46", but the lockfile that pins the transitive tree does not survive a fresh clone
|
|
☐ Commit `.pi/npm/package.json` + `package-lock.json` (recommended: treat it as a dev-environment lockfile, same class as the root one)
|
|
☐ Or document that pi self-installs the extension and the pin is advisory — decide which
|
|
☐ Gate the emit path in `npm run verify`
|
|
- `verify = check + test:unit`; `check:tsc` uses the root config (`noEmit: true`), so `tsconfig.build.json` is only exercised by `build`
|
|
- a broken build config (bad `rootDir`, emit-option typo) passes `verify` and only fails in CI
|
|
☐ Add `build` to `verify` (or to `check`)
|
|
☐ Fix `.ts` extensions in emitted `.d.ts`
|
|
- emitted JS rewrites `./pattern.ts` → `./pattern.js`, but `dist/*.d.ts` still imports `"./pattern.ts"` / `"./match.ts"`
|
|
- resolves under TS7, but a portability risk for older resolvers/bundlers; `attw` does not catch it
|
|
☐ Fix the declaration emit (`.d.ts` post-step) or stop using relative `.ts` in the declaration surface
|
|
☐ Reconcile the README/CONTRIBUTING claim that `rewriteRelativeImportExtensions` yields "conventional ESM imports"
|
|
☐ Add a consumer-resolution test to the suite (durable guard; `attw` currently misses it)
|
|
☐ Document pi-lsp false-positive diagnostics
|
|
- `lsp_diagnostics` reports TS1295/TS1287 "CommonJS file under `verbatimModuleSyntax`" errors that `check:tsc` never produces — the server is not picking up the repo's `tsconfig.json`
|
|
- AGENTS.md only warns that empty LSP output is inconclusive, not that it can emit false errors
|
|
☐ Add a line to AGENTS.md: ignore LSP errors that `check:tsc` does not reproduce
|
|
☐ Or fix the LSP server configuration so it picks up `tsconfig.json`
|
|
✔ Run packaging checks in CI `build` @done
|
|
- `publish:publint` / `publish:attw` only run in the tag-triggered `publish` job, so a PR that breaks packaging stays green until release
|
|
✔ At minimum add `publish:publint` to the `build` job (offline, fast); `attw` needs a pack @done
|
|
✔ Publish the exact artifact CI tested @done
|
|
- `publish: needs: build`, then re-runs `npm ci` + `build` from scratch, discarding the tested output
|
|
- tag push pays a double build and the two builds could differ
|
|
✔ Persist `dist/` as an artifact in `build` and consume it in `publish` @done
|
|
☐ Confirm pre-push gate strength
|
|
- pre-push runs `npm test` (`check:tsc` + tests), not full `check`; oxlint/oxfmt/cspell drift on unstaged content is only caught per-staged-file at commit or whole-project in CI
|
|
☐ Confirm this is intended per the feedback-tier table, or point pre-push at `verify`
|
|
✔ Clean stale `coverage/` in `npm run clean` @done
|
|
✔ `npm run clean` only removes `dist`; add `coverage` (both are gitignored but bloat the working tree) @done
|
|
✔ Drop redundant `main`/`types` top-level fields @done
|
|
✔ `exports` is the source of truth; `main`/`types` are redundant (harmless, but publint/ATTW prefer `exports`) @done
|
|
✔ Silence the knip `@runwisp/pubv` false positive @done
|
|
- `pubv` is a CLI invoked by `release.sh`, not imported, so knip flags it as an unused devDependency and advisory output stays permanently red
|
|
✔ Add a knip `ignoreDependencies` entry @done
|
|
☐ Resolve sourcemap sources for consumers
|
|
- `dist/*.map` `sources` are `../src/*.ts`, but `src` is not in `files`, so debuggers get missing sources
|
|
☐ Ship `src`, or disable `sourceMap`/`declarationMap` for the published artifact
|
|
✔ Sweep doc/formatter drift before v1.0 @done
|
|
✔ README says `--experimental-strip-types`; scripts use `--strip-types` @done
|
|
✔ `.vscode/settings.json` bundles `[markdown]`/`[yaml]` oxfmt formatters separately from `.oxfmtrc.json`'s `ignorePatterns` — align @done
|
|
✔ Document branching model @done
|
|
✔ Describe branching model: when to branch, base branch, naming @done
|
|
✔ Clarify release workflow: who pushes `main`, CI as post-merge gate, drop PR usage @done (9/8/2026, 2:54:32 PM)
|
|
✔ Evaluate connecting the agent to lsp typescript server @done
|
|
- might be more difficult with TS7, since LSP Server has changed from 6
|
|
- but since vscode is running TS7, maybe it is possible to connect to the TS7 LSP server of vscode
|
|
- LSP servers in general?
|
|
- maybe skills?
|
|
→ resolved: adopted @spences10/pi-lsp@0.0.46 as a project-local pi extension (`.pi/settings.json`). It auto-detects the repo's TypeScript 7 (no `lib/tsserver.js`) and spawns `tsc --lsp --stdio` — the same tsgo binary VS Code's native-preview uses. Read-only: hover / definition / references / symbols / diagnostics. No skill; skills don't own persistent processes.
|
|
|
|
✔ Adopt a `setup:` prefix for one-time clone configuration @done
|
|
✔ Register `use:git-commit-message` as its first member (and retire `use:` — it is in no prefix list) @done
|
|
✔ Create an umbrella 'setup' task that runs all setup tasks - currently one @done
|
|
|
|
v1.0:
|
|
☐ API surface is stable and fully typed
|
|
☐ Finalize public exports in `src/index.ts`
|
|
☐ Document all exported types and functions
|
|
☐ Add JSDoc for public APIs
|
|
☐ Test coverage meets threshold
|
|
☐ Achieve 100% branch coverage on `src/pattern.ts`
|
|
☐ Achieve 100% branch coverage on `src/match.ts`
|
|
☐ Achieve 100% branch coverage on `src/index.ts`
|
|
☐ `dist/` output is clean
|
|
☐ Verify `.d.ts` declarations match public exports
|
|
☐ Ensure `.js` files use `.js` extensions (not `.ts`)
|
|
☐ Test `attw --profile esm-only` passes
|
|
|
|
Bugs:
|
|
|
|
Enhancements:
|
|
|
|
Documentation:
|
|
☐ Add usage examples to README.md
|
|
☐ Create `examples/` directory with runnable snippets
|
|
☐ Add comparison section vs. other TS pattern-matching libs
|
|
☐ Write migration guide for users coming from discriminated unions
|
|
☐ Create backlog tasks for implementation
|
|
|
|
Maintenance:
|
|
☐ Serve CI coverage over a tiny self-hosted webserver (replace the zip artifact) @low
|
|
☐ Add a minimal dir-listing webserver to the gitea docker setup (e.g. caddy `file_server browse` reusing the existing reverse proxy, or any single-binary static server, lipanski/docker-static-website)
|
|
☐ CI writes each run's `coverage/` into a shared volume keyed by project + tag (e.g. `/coverage/tiny-pattern-ts/<tag>/`)
|
|
☐ Browse to `…/coverage/<repo>/<tag>/index.html` in the browser; drop the `actions/upload-artifact` coverage step in favour of the shared-dir layout
|
|
→ design: no deploy step in CI; the webserver just exposes the shared directory (decided over Gitea Pages / Codecov — neither confirmed available/ wanted)
|
|
✔ Set up lefthook pre-commit hook @done (9/8/2026, 10:52:56 AM)
|
|
✔ Configure tsconfig strictest + node26 profiles @done (9/8/2026, 10:08:37 AM)
|
|
✔ Add check:tsc as first tier in `npm run check` @done (9/8/2026, 10:08:37 AM)
|
|
✔ Pin Node.js >= 26 via `.node-version` @done (9/8/2026, 10:08:38 AM)
|