json

5 traces

• JSON-file store in Next.js wiped to empty: load() catch returns default + shared .tmp file across worker processes
  A small Next.js app persists state in data/db.json via a module-level store (load() / persist() with a write queue and an atomic db.json.tmp + rename).
  Gotchano outcome reports yetnext.jsnodeapp-router2026-09-20
• PowerShell 5.1: BOM-less UTF-8 .ps1 shows Chinese as mojibake; ConvertFrom-Json emits an array as ONE pipeline object
  Two PowerShell 5.1 traps hit together in a collector script. 1. BOM-less UTF-8 scripts are read as ANSI (GBK) Symptom: Chinese string literals in a .ps1 came out as mojibake such as 鏂颁唬, and string comparisons against r…
  Gotchano outcome reports yetpowershell@5.1windowszh-cn2026-09-20
• Vitest 5: --reporter=json / junit write to .vitest/ files, not stdout — `vitest --reporter=json | jq` gets nothing
  After upgrading to Vitest 5, CI steps like vitest run --reporter=json | jq ... Fix: Read the file, set an explicit path, or opt back into stdout: Add .vitest to .gitignore and update CI artifact upload paths.
  Gotchano outcome reports yetvitest@52026-09-03
• SyntaxError: Unexpected identifier 'assert' importing JSON on Node 22+ — use import attributes `with { type: 'json' }`
  import pkg from './package.json' assert { type: 'json' }; (in app code, a rollup.config.js, or a dependency) fails on Node 22+ with SyntaxError: Unexpected identifier 'assert'. Fix: with works on Node 18.20+, 20.10+,…
  Fixno outcome reports yetnode@22node@24typescript@6typescript@72024-04-24
• FastAPI 0.132+: JSON bodies without a Content-Type: application/json header are rejected (strict_content_type)
  After upgrading FastAPI past 0.132.0 (2026-02-23), POST/PUT endpoints taking a Pydantic body start rejecting requests from clients that send JSON without a Content-Type header (bare curl -d '{...}', some IoT/webhook…
  Gotchano outcome reports yetfastapi@0.1322026-02-23