You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
Running npx @sentry/wizard@latest -i sveltekit (wizard 3.7.1), I get this output:
...
■ Error while setting up the SvelteKit SDK:
│
● TypeError: 'set' on proxy: trap returned falsish for property 'plugins'
🎉 Successfully set up Sentry for your project 🎉
Running it again with --debug, I get:
...
■ Error while setting up the SvelteKit SDK:
│
● TypeError: 'set' on proxy: trap returned falsish for property 'plugins'
{
"integration": {
"_argv": {
"_": [],
"i": "sveltekit",
"integration": "sveltekit",
"debug": true,
"uninstall": false,
"skip-connect": false,
"skipConnect": false,
"quiet": false,
"s": false,
"signup": false,
"disable-telemetry": false,
"disableTelemetry": false,
"$0": "../../../.npm/_npx/ddb126e78325956c/node_modules/.bin/sentry-wizard"
},
"_isDebug": true
}
}
🎉 Successfully set up Sentry for your project 🎉
The --debug option didn’t add any output that could help me debug the issue.
(the error itself is tracked in #362 and the bug of the success message that shows even when there’s an error is tracked in #337)
The text was updated successfully, but these errors were encountered:
Hi @bfontaine! You're right, in this case --debug doesn't do a lot. However, for the specific error you're referring to we wouldn't have gotten much more than the TypeError message anyway. magicast's error messages aren't very descriptive in many cases.
I'm currently reworking the vite setup in the SvelteKit wizard and I'll try to add some better debug logging.
Hello,
Running
npx @sentry/wizard@latest -i sveltekit
(wizard 3.7.1), I get this output:Running it again with
--debug
, I get:The
--debug
option didn’t add any output that could help me debug the issue.(the error itself is tracked in #362 and the bug of the success message that shows even when there’s an error is tracked in #337)
The text was updated successfully, but these errors were encountered: