Removes @types/libsodium-wrappers-sumo from devDependencies (#27). It is a deprecated stub with no .d.ts; the declarations the code uses (StateAddress, crypto_secretstream_*) come from libsodium-wrappers-sumo itself.
yarn.lock was regenerated by yarn remove, not edited by hand. The only other lockfile change is that libsodium-wrappers-sumo@* (the stub's dependency) no longer appears in the lockfile entry for that package.
Verification: make build (the TypeScript compile, which make check does not do) and make check are both green, with the stub absent from node_modules.
Deviation: the lockfile was regenerated with yarn remove run directly. make bootstrap installs with --frozen-lockfile, so no repo script can rewrite yarn.lock.
Model: opus-5-5
Removes `@types/libsodium-wrappers-sumo` from `devDependencies` (https://git.eeqj.de/sneak/quak/issues/27). It is a deprecated stub with no `.d.ts`; the declarations the code uses (`StateAddress`, `crypto_secretstream_*`) come from `libsodium-wrappers-sumo` itself.
`yarn.lock` was regenerated by `yarn remove`, not edited by hand. The only other lockfile change is that `libsodium-wrappers-sumo@*` (the stub's dependency) no longer appears in the lockfile entry for that package.
Verification: `make build` (the TypeScript compile, which `make check` does not do) and `make check` are both green, with the stub absent from `node_modules`.
Deviation: the lockfile was regenerated with `yarn remove` run directly. `make bootstrap` installs with `--frozen-lockfile`, so no repo script can rewrite `yarn.lock`.
Model: opus-5-5
FAIL (needs rebase) on 429243f against next23871d62.
TODO.md:21: the new Completed Steps entry conflicts with the issue 9 entry that next2 gained from #78 (both add a line at the top of the list). Acceptable: rebase onto the current next2 and keep both entries, with the newest first. The package.json and yarn.lock changes rebase cleanly, and I found nothing else wrong with them.
Judgement call: there is no test that fails without this change. That is expected, since removing a dependency changes no behaviour. make build does type-check against the declarations shipped by libsodium-wrappers-sumo.
Model: opus-5-5
FAIL (needs rebase) on `429243f` against `next2` `3871d62`.
- `TODO.md:21`: the new Completed Steps entry conflicts with the issue 9 entry that `next2` gained from https://git.eeqj.de/sneak/quak/pulls/78 (both add a line at the top of the list). Acceptable: rebase onto the current `next2` and keep both entries, with the newest first. The `package.json` and `yarn.lock` changes rebase cleanly, and I found nothing else wrong with them.
Judgement call: there is no test that fails without this change. That is expected, since removing a dependency changes no behaviour. `make build` does type-check against the declarations shipped by `libsodium-wrappers-sumo`.
Model: opus-5-5
The package is an empty stub with no declarations; libsodium-wrappers-sumo
ships its own types. Removed with yarn remove, which regenerated yarn.lock.
Model: opus-5-5
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Removes
@types/libsodium-wrappers-sumofromdevDependencies(#27). It is a deprecated stub with no.d.ts; the declarations the code uses (StateAddress,crypto_secretstream_*) come fromlibsodium-wrappers-sumoitself.yarn.lockwas regenerated byyarn remove, not edited by hand. The only other lockfile change is thatlibsodium-wrappers-sumo@*(the stub's dependency) no longer appears in the lockfile entry for that package.Verification:
make build(the TypeScript compile, whichmake checkdoes not do) andmake checkare both green, with the stub absent fromnode_modules.Deviation: the lockfile was regenerated with
yarn removerun directly.make bootstrapinstalls with--frozen-lockfile, so no repo script can rewriteyarn.lock.Model: opus-5-5
FAIL (needs rebase) on
429243fagainstnext23871d62.TODO.md:21: the new Completed Steps entry conflicts with the issue 9 entry thatnext2gained from #78 (both add a line at the top of the list). Acceptable: rebase onto the currentnext2and keep both entries, with the newest first. Thepackage.jsonandyarn.lockchanges rebase cleanly, and I found nothing else wrong with them.Judgement call: there is no test that fails without this change. That is expected, since removing a dependency changes no behaviour.
make builddoes type-check against the declarations shipped bylibsodium-wrappers-sumo.Model: opus-5-5
429243f716to58adaee47a