a public builder

@publicbuilder.bsky.social

doing some experiments to build something in public

I am fed up with all the kubernetes DSL. helm and kustomize may do the work, but I need to learn a lot to do my job. E.g. a task as simple as copy and modify existing StorageClass to support Retain ReclaimPolicy is not easily achievable to me. I need to learn a ton of the syntax and semantics.

Gemini's batch generation api is a PITA. Some configs for normal generation (e.g. think config) are not available in batch generation. What's worse, you can pass a pillow Image.Image to generate_content, but you have to "reverse engineer" gemini source code to figure out to to serialize an Image.

Gee. Open telemetry and grafana cloud is really a godsend. Super easy to setup, yet extremely powerful (hope to show some dashboard porn soon, but for now, not enough data). Plus, grafana cloud is just too cheap.

BildBild

I have to confess my love for nextjs. This affection does not stem from its ease to use or unparalleled power. Having went through countless seemingly un-decipherable errors of nextjs should be a competitive edge for me. I hope nextjs would be more widely adopted. All my efforts shouldn't be in vain

Bild

I tried a ton of html to image libraries. None of they solve the problem "Error: CSSStyleSheet.cssRules getter: Not allowed to access cross-origin stylesheet". Most of the issues remain free-standing for quite a few years. github.com/bubkoo/html-... Alas, firefox is really not loved.

CSS CORS Issue · Issue #301 · bubkoo/html-to-image

I'm just starting to experiment with this library, as html2canvas is having some issues for me. The first thin I'm experiencing is a CSS CORS issue. The console debugger is throwing an error: Error...

github.com

I am horrified by typescript programmers' abuse of type inference on almost dynamic objects and functions. Can we just disband dynamic evils once and for all? Why would anyone prefer zod over real static types? Please use derive/deriving as in rust/haskell while crossing the boundary.

stackoverflow.com/questions/71... "Can we all agree this error message is worse than useless?!" My vibe-fu is strong enough to have the error "Hydration failed because the initial UI does not match what was rendered on the server", weak enough to not be able to ask the agent to try ~50 solutions.

React 18: Hydration failed because the initial UI does not match what was rendered on the server

I'm trying to get SSR working in my app, but I get the error: Hydration failed because the initial UI does not match what was rendered on the server. Live demo code is here. Live demo of problem is

stackoverflow.com

Why is the quality of popular nodejs libraries so low? I want to intercept openai traffic for debugging. proxy-agent library doesn't even have an option to use self-signed certificates. People came up with ingenious solutions, but the issue is never fixed in upstream. github.com/TooTallNate/...

Doesn't seem to pass options to tls.connect · Issue #89 · TooTallNate/proxy-agents

as per documentation https://www.npmjs.com/package/https-proxy-agent#new-httpsproxyagentobject-options Any other options given are passed to the net.connect()/tls.connect() functions. But when I tr...

github.com

Am I doing it wrong? Or, it's just prompting requires more work? The result generated from this prompt is really underwhelming. For this particular example, I should have used better-auth's client API instead of creating back-end interfaces. Neither me or the "agent" was smart enough.

BildBild

Some of the things are not open source (like vercel/og), which by itself is understandable. But given all the broken things I encountered in just a few days, I strongly believe that vercel is on its way to enshitification. These things may be broken by design.

There is also a feature disparity between vercel.json config and project config on the web. There are something you can set with the web interface (e.g. root directory), but you can't do that with vercel.json. Building on monorepo has been broken for years github.com/vercel/verce....

vercel@33.3.0 broke preBuilds in monorepo · Issue #12667 · vercel/vercel

Recreated #11097 as requested by @TooTallNate, We are using the preBuild option in our monorepo but after updating to vercel@33.3.0 it no longer works, when trying to do the deploy we get the follo...

github.com