Question for anyone on here: Has anyone integrated...

# kobweb

[Ryan Scott]

Question for anyone on here: Has anyone integrated Sentry/Glitchtip? I was just able to do it (and exceptions are getting reported), but the main thing I haven't been able to do is get the kotlin source maps working.

[David Herman]

Through Kobweb? I thought running jsBrowserDevelopmentRun (which kobweb run calls) was all you needed to do?

[Ryan Scott]

No--you have to upload the source maps.

[Ryan Scott]

Unless I'm missing something.

[David Herman]

Maybe I should look into what Sentry/Glitchtip are :)

[Ryan Scott]

I see. Sentry is basically like Firebase Crashlytics. I works super-well for browser apps.

[Ryan Scott]

Glitchtip performs the same function, but it's easier to self-host.

[David Herman]

Ah I see. So basically when you build your code, you want to do an additional gradle step to upload those source maps?

[Ryan Scott]

That's correct.

[David Herman]

Production only yeah?

[Ryan Scott]

Correct.

[Ryan Scott]

Within the browser itself, the console links to the appropriate kotlin code--which is handy.

[Ryan Scott]

It doesn't seem like much of a stretch to get that to work when uploading stacktraces.

[Ryan Scott]

Unless things work differently than I think.

[David Herman]

Are you having trouble finding the task that generates the source maps?

[Ryan Scott]

(which is entirely possible)

[David Herman]

(I assume the webpack task)

[Ryan Scott]

I was reading through the kobweb application plugin code to see if I could find that.

[David Herman]

Do this

[Ryan Scott]

Which led me here: https://github.com/varabyte/kobweb/blob/main/tools/gradle-plugins/application/src/[…]m/varabyte/kobweb/gradle/application/KobwebApplicationPlugin.kt

[David Herman]

In your projectn site, run ../gradlew kobwebStart --dry-run

[David Herman]

That will show you all the dependency tasks

[David Herman]

You can then locate the source maps in your build dir

[David Herman]

Then just run the raw Gradle commands until the source maps appear

[David Herman]

Then you have a Gradle task you can at least hook onto/depend on at which point you can locate and upload those files to sentry or whatever

[David Herman]

https://kobweb.varabyte.com/docs/getting-started/kobweb-project#gradle-commands may help and make sure you pass in gradle args that indicate a production run and not a dev run

[Ryan Scott]

until the source maps appear

I'm not sure I know what to check for.

[David Herman]

What source map is the browser linking to?

[David Herman]

Actually I think maybe we copy it on export now that I'm recalling it

[David Herman]

https://github.com/varabyte/kobweb/blob/4646ef660dd44b74397968beacc332c06b02ddfd/tools/gradle-plugins/application/src/main/kotlin/com/varabyte/kobweb/gradle/application/tasks/KobwebExportTask.kt#L338

[Ryan Scott]

Is it this?

[S.]

aren't js maps included per default in the export?

[David Herman]

We drop a source map under .kobweb/site somewhere (I think the location depends on fullstack vs static)

[Ryan Scott]

Ah--it's .kobweb/site/site.js/site.js.map

[David Herman]

So you can basically grab the export task by name in your build script, configure it, and in a doLast find the file and upload it

[Ryan Scott]

Cool. I've almost got it working, but the reason it's not working is not because of anything related to kobweb.