René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"[Feature]: Promote `concurrency` to Stable — define exit criteria from Experimental","articleBody":"**Pre-flight checklist**\n- [x] I searched existing issues and did not find a duplicate request.\n- [x] I explained the problem or use case, not just the desired API.\n\n**Problem or use case**\n`concurrency` is **Experimental** and carries hard documented constraints that block real adoption: handlers must be standalone serializable functions (no closures); the module is browser-only (\"Node / Deno / Bun adapters: not adopted\"); it requires a relaxed CSP (`'unsafe-eval'` plus `worker-src blob:`) because worker bodies are revived via `new Function(...)`; and `createSharedBuffer()` needs `crossOriginIsolated` with COOP/COEP headers. The `'unsafe-eval'` requirement in particular directly contradicts bQuery's secure-by-default posture. There is no published path out of Experimental.\n\n**Proposed solution**\nPublish exit criteria and resolve the two adoption-blocking constraints tracked in #134 (CSP-safe execution) and, where appropriate, document the closure limitation as a permanent, clearly-explained design boundary rather than a bug. Criteria: (a) a default execution mode that needs no `'unsafe-eval'` (#134); (b) documented, enforced guidance for the serializable-handler constraint with good error messages; (c) test coverage for pools, RPC, and shared buffers; (d) an explicit statement of the runtime boundary (browser-focused) consistent with the module's stated non-goals.\n\n**Possible API or UX shape**\n```\n## Stability: targeting Stable in 1.15.0\nExit criteria:\n- [ ] CSP-safe default worker mode, no 'unsafe-eval' (#134)\n- [ ] Serializable-handler constraint documented + enforced with clear errors\n- [ ] Coverage: task/pool/RPC/sharedBuffer\n- [ ] Runtime boundary stated (browser-focused, per non-goals)\n```\n\n**Alternatives considered**\nKeeping `concurrency` Experimental because it is browser-only — the browser focus is a legitimate scoping decision and need not block stability; what blocks it is the `eval`-dependent default and undocumented constraints, both addressable. Adding Node/Deno/Bun worker adapters — explicitly out of scope per the module's non-goals, so not proposed here.\n\n**Relevant area**\n`concurrency`\n\n**Additional context**\nThe module's ThreadTS parity matrix marks pools/collection helpers as \"Adapted\" and decorators/runtime adapters as \"Not adopted,\" which is fine to keep. The `'unsafe-eval'` requirement is the item most at odds with the framework's security identity and should be treated as the primary blocker.\n","author":{"url":"https://github.com/JosunLP","@type":"Person","name":"JosunLP"},"datePublished":"2026-06-26T21:25:12.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/133/bQuery/issues/133"}