Piero Bosio Social Web Site Personale

#LogTape 2.2.0 is out! The headline is two new packages: @logtape/lint adds lint rules for ESLint v8/v9 (flat config), Oxlint, and Deno Lint that catch common logging mistakes before they reach production: template literal interpolation in message arguments, eager property evaluation where lazy is needed, unawaited async log callbacks, and missing meta sink configuration. @logtape/testing gives you createLogRecorder() and domain-aware assertion helpers, replacing the hand-rolled array-sink boilerplate that every project ends up writing. Other highlights: context: true on Express/Hono/Koa/Elysia middleware handles request ID generation, x-request-id header propagation, and implicit context. One option instead of several moving parts. Seven performance optimizations on the enabled-logging hot path New logtape.org website Full release notes: https://github.com/dahlia/logtape/discussions/179 #JavaScript #TypeScript #Deno #Node #NodeJS #Bun #logging #opensource

#Optique 1.0.0을 릴리스했습니다. Haskell의 optparse-applicative 스타일의 #TypeScript #CLI 파서가 필요해서 만들었습니다. 작은 타입 파서들을 조합하면 TypeScript가 결과 타입을 자동으로 추론합니다. 서브커맨드, 옵션 간 의존성, 셸 완성, 맨(man) 페이지 생성 등을 지원하고, #Deno, #Node.js, #Bun 등에서 동작합니다. 이번 버전에서는 @optique/env (환경 변수 폴백) 패키지와 @optique/inquirer (Inquirer.js 프롬프트 폴백) 패키지를 추가했습니다. API의 어색한 부분들도 많이 정리하고, 다섯 가지 셸의 완성 스크립트 버그도 한꺼번에 잡았습니다. JSR과 npm에서 설치하실 수 있습니다. https://github.com/dahlia/optique/discussions/796

#Optique 1.0.0 is out! If you build #CLI tools with #TypeScript, it might be worth a look. I started it because I wanted a TypeScript CLI parser that felt more like optparse-applicative than the usual builder-style APIs. You build up small typed parsers, compose them, and TypeScript infers the result. It handles subcommands, option dependencies, shell completion, and man pages, and it runs on #Deno, #Node.js, and #Bun. For 1.0 I added @optique/env, so env vars can fill in missing flags, and @optique/inquirer, so missing values can fall back to Inquirer.js prompts. I also cleaned up a lot of awkward API edges and fixed a long backlog of completion bugs across five shells. Packages are on JSR and npm. https://github.com/dahlia/optique/discussions/796

@grahamperrin can't reply on reddit, but as you know I have a similar setup. It will work, but expect classic Optimus problems : finger crossing Xorg won't be buggy, proprietary often buggy nvidia-driver mandatory, drivers mismatching... But it will probably work, assuming the user knows these caveats and how to solve them...