feat(skills-next): add svelte SDK references#253
Conversation
184603b to
42b4a42
Compare
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 42b4a42. Configure here.
| import * as Sentry from "@sentry/sveltekit"; | ||
|
|
||
| Sentry.init({ | ||
| dsn: import.meta.env.VITE_SENTRY_DSN, |
There was a problem hiding this comment.
Client DSN env var mismatch
Medium Severity
The main SvelteKit setup in index.md reads PUBLIC_SENTRY_DSN (with VITE_SENTRY_DSN fallback), but several feature references use only import.meta.env.VITE_SENTRY_DSN. Teams following the index and then a feature doc can end up with an empty client DSN and a disabled SDK.
Additional Locations (2)
Reviewed by Cursor Bugbot for commit 42b4a42. Configure here.
| import * as Sentry from "@sentry/sveltekit"; | ||
|
|
||
| export const handle = sequence( | ||
| Sentry.sentryHandle(), |
There was a problem hiding this comment.
Bug: The SvelteKit hooks.server.ts code sample uses the sequence function without importing it from @sveltejs/kit/hooks, which will cause a ReferenceError.
Severity: MEDIUM
Suggested Fix
Add the line import { sequence } from "@sveltejs/kit/hooks"; to the top of the code sample in logging.md to ensure the sequence function is correctly imported and available at runtime.
Prompt for AI Agent
Review the code at the location below. A potential bug has been identified by an AI
agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's
not valid.
Location: skills-next/references/sdks/svelte/logging.md#L166
Potential issue: The code sample for "Isolation scope (per-request in SvelteKit)" in
`logging.md` demonstrates using the `sequence` function to compose SvelteKit server
hooks. However, it omits the necessary import statement: `import { sequence } from
"@sveltejs/kit/hooks";`. A developer copying this code into their project will encounter
a `ReferenceError: sequence is not defined` when their application starts, as the
`sequence` function will not be in scope. Other examples in the documentation correctly
include this import, indicating this is an oversight.


Direct LLM port of the existing
svelteSDK skill into the skills-next per-SDK reference layout underskills-next/references/sdks/svelte/. This content has NOT been reviewed at all — it is a machine-generated port of the existing SDK skill, and every file should be treated as unverified.