This is one of those annoying things. Updating OctoKit updated some transitive sindresorhus dependency which now forces onto ESM.
This proves to be a pretty annoying problem because you can't use CommonJS from inside ESM and vice versa. Somehow, as an industry, we've managed to invent "what color is your import" for NodeJS, which is a pretty brutal problem.
Anyway. I've made this specific package into an ESM module, and what it compiles to is a module now, too, instead of CommonJS. Luckily, because the github bot is so small and isolated, it means we have very little trouble doing this (and hopefully no brutal side effects).
* temporary dvctr
* start of work
* fix: timeouts in windows
* fish?
* feat: better, working stuff
* refactor: rename database-seeds to seeds/
* better
* fdsaf
* feat: don't let our container get owned by root
* fix: better user handling
* feat: falling asleep at my desk i yield to you what i have done
* feat: autoadminify
* docs: denote trickshot
* feat: open in browser on launch
* better seeds workings...
* fix: dont kill shell
* docs: mention dev/debs
* fix: whoops
* fix: make seeds load within the century
* feat: rest of the containerisation
* feat: new alias
* style: fix linter errors
* fix: bad call
* fix: better justfile
i knew updating octokit would break something stupid and here's
the exact stupid thing breaking.
literally no idea. all autogenned types that don't seem to even agree
with eachother. What even is the point man
this was causing issues with vite and is potentially a bug in prudence
or in vite. it's very hard to tell and i've already spent
3 hours trying to fix this, so here.
zkldi