@mattpocockuk And you might have to sprinkle in some filehandle.sync(…) or filehandle.datasync(..) to make sure you get the right size as the file is being appended to….
@mattpocockuk As of what to use in node, I’d open a handle and then use https://t.co/YqaJc6giFF(..), it seems the easiest option, and filehandle.stat(…) to figure out length and block length (make your chunks a multiple of that, and align them)
https://t.co/IyPg9xtcEL
@Grady_Booch@benjedwards Hey GPT, rewrite the following (series of insults to some random idiot) and make it sound firm, but polite and professional…
You don’t know how many times it avoided me getting in trouble with HR 🤣😂
Apart from this, utterly useless!
@mattpocockuk@sminnee Sometimes, the interpreter *itself* strips types (deno, or the next version of node - now experimental) so there’s NO .js file at all… requiring imports of an artifact that is possibly produced by TSC is just nonsensical to me…
@mattpocockuk@sminnee Actually it is… the generated extension is a product of the transpilation process: same .ts can be transpiled as .cjs, .mts or .js - depending on what’s actually transpiling and how the transpiler is configured (think esbuild, for example)
@mattpocockuk@JoshuaKGoldberg And, before you ask, yes, I need some time to write some darn documentation for it 😀 I'd love if someone wanted to help with it!!!
@mattpocockuk@JoshuaKGoldberg We've been using this on all our internal repos for around a couple of years, super happy with it (we have for example integrations to deploy on AWS lambda, Cloudflare workers, all our workflow) and recently I've been thinking it might be a good idea to share