I can't "Start game", "Options" is the only thing that works (the console has "SyntaxError: await is only valid in async functions"). * * *

``You're calling OpenAI from Node.js. 99% of requests work. Then randomly: BadRequestError: 400 could not parse JSON body Or: SyntaxError: Invalid JSON: EOF while parsing an object Or, if you're using tool calling: Invalid JSON in tool call arguments You check your code. Nothing changed. You retry manually — it works. You deploy again. It breaks again. ## What's actually happening These errors are NOT your bugs. They're transient artifacts from: 1. Proxy / network corruption — the request body arrives at OpenAI partially mangled. OpenAI returns 400. 2. Streaming truncation — the SDK parses JSON before the stream signals completion. Especially with max_output_tokens set low. 3. Model-side tool call malformation — the model emits single quotes, trailing commas, or markdown code fences inside function.arguments. Every one of these is intermittent. So you can't debug it with a stack trace. You just suffer. ## The wrong fix People usually do this: try { const res = await client.chat.completions.create({...}); } catch (e) { const res = await client.chat.completions.create({...}); } Problems: * You retry errors that should NOT be retried (invalid API key, rate limit that needs backoff, context length exceeded). * You don't sanitize tool call args, so malformed JSON still crashes downstream. * You add 20 lines of retry boilerplate per call site. ## The right fix: classify then act Different errors need different handling: Error | Correct action ---|--- Transient 400 (could not parse JSON body) | Retry with backoff + jitter Truncated stream (EOF while parsing) | Retry, possibly with higher max_tokens Malformed tool args | Sanitize inline, no retry needed Invalid API key | Fail fast, do NOT retry Rate limit | Retry with longer backoff Doing this manually is ~150 lines of code you'll write badly. Or: npm install @coder12-z/llm-shield import { shield } from "@coder12-z/llm-shield"; import OpenAI from "openai"; const client = new OpenAI(); const safeCall = shield(async (prompt) => client.chat.completions.create({ model: "gpt-4o-mini", messages: [{ role: "user", content: prompt }], response_format: { type: "json_object" }, }), { maxRetries: 3, onRetry: ({ attempt, kind }) => console.log(`retry #${attempt} (${kind})`), } ); Three lines of config. Zero dependencies. Works with OpenAI, Anthropic, Gemini, or anything that throws Error objects with status and message. ## What it doesn't do * It doesn't repair arbitrary JSON strings — for that, use jsonrepair (https://www.npmjs.com/package/jsonrepair). * It doesn't call LLMs for you — it wraps your existing calls. * No API key. No network calls. No telemetry. ## Links * npm: https://www.npmjs.com/package/@coder12-z/llm-shield * GitHub: https://github.com/zey-netizen/llm-shield * Landing: https://zey-netizen.github.io/llm-shield/ MIT licensed. Feedback welcome.

はじめに react-router-dom導入時の話 問題 Switchコンポーネントがないと言われる 解決 今のverではSwitchはないので、Routesコンポーネントを使う 終わりに

YouTube video by DJ iD01t

The JavaScript exception "raw bracket is not allowed in regular expression with unicode flag" occurs when a Unicode-aware regular expressi…

The page shows in Firefox 78 because it didn't support logical OR assignment (||=): CODE: Uncaught SyntaxError: expected expression, got '=' chunk-QFMPRPBF-p0C_NFcx.js:1:24656 It just so happens that the browser stops parsing JavaScript before the page blanking function got called due to the SyntaxError. Funnily this ||= operator was only supported in Firefox starting in version 79, and indeed firing up an instance of FF79 from mozregression I can see that the script from Shopify's CDN blanks the page. I bet it will also become blank in an instance of Firefox ESRs 91 and 102 as well, since TextEncoderStream support only got implemented by Mozilla in version 105. Hell I just fired an instance of Firefox 53 from mozregression as I'm typing this and the page didn't become blank there (in that case it errored so early that it didn't even get to the point of calling the offending script from Shopify). Really the problem in this case is that Pale Moon's JavaScript engine supports more than what FF78 did, to the extent as to make the page blanking possible, but not more than that to avoid the page blanking from being triggered. And this is one of the reasons why it's not really helpful to point out that "it works in Firefox <insert version here>". * * *