zzstoatzz.io
claude up some atproto stuff
fix wisp skill: rewriter mangles inline scripts, not just HTML attrs
previous description said wisp only rewrites HTML href/src attributes.
wrong — it also rewrites inside <script> tags. anything matching
`= /...` gets path-prefixed, turning `= await res.json()` into
`=/did:plc:.../site/await res.json()`. the safe fix is always using
external .js files instead of inline scripts.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
+2
-2
skills/wisp/SKILL.md
+2
-2
skills/wisp/SKILL.md
···
25
25
26
26
- **Frameworks must use relative paths.** Absolute paths like `/_app/...` will break.
27
27
- **SvelteKit**: set `paths.relative = true` in `svelte.config.js`. Avoid SPA fallback — prerender instead.
28
-
- **Wisp rewrites HTML `href`/`src` attributes but not JS string literals** in inline `<script>` tags. If your framework emits `import("/_app/...")` in inline scripts, those paths will break.
29
-
- When in doubt, prerender everything and use relative paths throughout.
28
+
- **Wisp's path rewriter is aggressive** — it rewrites paths inside inline `<script>` tags too, not just HTML attributes. For example, `const data = await res.json()` can be mangled into `const data=/did:plc:.../site-name/await res.json()` because the rewriter interprets `= /...` as a relative path assignment. **Always use external `.js` files instead of inline scripts.**
29
+
- When in doubt, prerender everything, use relative paths, and keep JS in external files.
30
30
31
31
## domains
32
32