SvelteKit $app/environment's version not matching release number.

[kyllerss]

I am using Vercel to host a SvelteKit site. I use a service worker on the client side.

I am seeing that the build release number in Sentry is 44c172aaf0ef9c233c802af6490b1fcca6b40484, while the version environment variable exposed by $app/enviroment shows the value as 1706216591938.

I want to do a better job of identifying issues where a clients are accessing server endpoints using an outdated client version.

How can I make sure these match? Did I misconfigure something along the way that resulted in the release number being different than the version number? Or does this require a separate setup?

Any help/suggestions greatly appreciated.

[Lms24]

Hi @kyllerss thanks for writing in and apologies for the late reply (we don't track discussions as rigorously as issues internally so some slip through).

TBH I've never worked with version before but the way I understand your question is that you want to set it as a Sentry release?
Based on the JSDoc around version, I can see that SvelteKit uses this version to determine when served content changes during a user session. I guess this is quite important if you're caching stuff with a service worker, too.

I'm not sure that people would generally want to set version to their app version but if that's what you'd like to do, I think it should be possible:

The SDK won't pick up version automatically, meaning you'd need to set the release property in

• hooks.client.ts

  Sentry.init({
    // ...
    release: version
  });

• hooks.server.ts (same as in client hooks)
• vite.config.ts:

   sentrySvelteKit({
     sourceMapsUploadOptions: {
       release: version,
     },
   }),

Does this work for you?

[kyllerss]

Hi, @Lms24. No worries! SvelteKit provides a version field to identify unique builds. This field is available both through their $app/environment and $service-worker modules.

To my understanding, the version environment variable is a build-related version (it's used by service workers to identify when a build has changed and static assets need to be eagerly cached). When I look at the version value on my deployments, it's a numerical version. This mismatches with the release version that the Vercel+Sentry integration uses (it's a hash value instead of the numeric value).

Ideally I'd like both fields to coincide. Wouldn't following your suggestion undo the existing build integration (eg. source map integration) between Vercel and Sentry? Any thoughts on how I could proceed?