Invalid DSN error deploying on Vercel with SvelteKit

[atcupps]

Starting today, I've started getting this Sentry error on Vercel deployments of my SvelteKit project:

SentryError2: Invalid Dsn
    at new SentryError2 (/var/task/node_modules/vercel/dist/index.js:10658:30)
    at Dsn2._fromString (/var/task/node_modules/vercel/dist/index.js:12377:19)
    at new Dsn2 (/var/task/node_modules/vercel/dist/index.js:12361:18)
    at NodeBackend2._setupTransport (/var/task/node_modules/vercel/dist/index.js:15325:21)
    at NodeBackend2.BaseBackend2 (/var/task/node_modules/vercel/dist/index.js:12842:34)
    at new NodeBackend2 (/var/task/node_modules/vercel/dist/index.js:15319:44)
    at NodeClient2.BaseClient2 (/var/task/node_modules/vercel/dist/index.js:12578:27)
    at new NodeClient2 (/var/task/node_modules/vercel/dist/index.js:15407:25)
    at Object.initAndBind (/var/task/node_modules/vercel/dist/index.js:12878:40)
    at Object.init3 (/var/task/node_modules/vercel/dist/index.js:16217:14)

I'm not sure why this error is occuring, since I didn't change anything and this error has never occurred before today. I'm initializing Sentry simply with the following in hooks.server.ts:

Sentry.init({
  dsn: 'https://#######@#########.ingest.us.sentry.io/#########',
  tracesSampleRate: 1.0, 
});

[atcupps]

Not sure why this happened, but I seem to have fixed it by just generating and using a new DSN.