Projects using npm in BangkokProjects using npm in Bangkok
Projects
People
Cover image for WebP encoding. Pure TypeScript. No
WebP encoding. Pure TypeScript. No WASM. WebP encoding, without shipping a native binary or a WebAssembly module. I ported my PHP WebP encoder (https://contra.com/p/RQF2OWNY-pico-web-p-building-a-web-p-encoder-in-php?r=niko_minadze_98hnmhja) to TypeScript and published PicoWebPJS. It includes its own PNG, baseline JPEG and BMP readers and writes the WebP bitstream itself. The same encoding core runs in Node.js and modern browsers, with zero runtime dependencies. That gives an upload tool the option to convert images on the user's device, and a Node application an encoder without platform-specific native bindings. Transparency and colour profiles are preserved, with a browser-worker example and resumable Node.js encoding included. Native encoders are generally faster. This package is for the cases where keeping image processing portable and free of native tooling is worth that trade-off. Open source. MIT licensed. Available on npm. npm install picowebpjs Package (https://www.npmjs.com/package/picowebpjs) · Source (https://github.com/lame13/picowebpjs)
0
35
Cover image for An audit report should still
An audit report should still make sense after it’s been forwarded three times. I’ve released SSRWire 0.5.0, with a new HTML report for handing over findings from streamed HTML checks. Each built-in finding explains: What was observed. Why it matters. What to change. Fix examples can be tailored to Next.js, Nuxt, Astro, WordPress and other supported stacks. The framework choice changes the guidance; the findings still come from the captured response. Response timings and metadata arrival order sit alongside those explanations, so a developer can inspect the evidence behind a finding. The result is one HTML file that opens offline, without JavaScript or remote assets. Attach it to an issue, send it to a client, or keep it with the release checks. Even the social-preview section stays local: it shows the captured metadata and image URL without fetching the image. SSRWire 0.5.0 on npm (https://www.npmjs.com/package/ssrwire)
1
270
Cover image for A page can look correct
A page can look correct after hydration while still delivering incomplete, late or inconsistent HTML to search crawlers and social-preview bots. I built SSRWire to inspect that exact layer. It makes real HTTP requests using browser, Googlebot, Bingbot, X/Twitter and Facebook user-agent profiles, then reads the streamed HTML incrementally. It records when titles, descriptions, canonicals, robots directives, Open Graph and Twitter Card metadata, JSON-LD, H1s and main content become observable—including timing, byte position and whether each signal arrived in <head> or <body>. The new 0.4.0 release can also compare preview and production audits without repeating the requests. It separates regressions, fixes and neutral changes, applies configurable timing thresholds, and generates a self-contained HTML waterfall for each user-agent profile. JSON and SARIF output make the checks usable in CI: npx ssrwire https://example.com/ No browser installation and no JavaScript execution. SSRWire is deliberately an HTTP-level SSR consistency and release-QA tool, not a full crawler or rendering emulator. https://www.npmjs.com/package/ssrwire
1
254