Sourcemaps not being parsed properly?

[kennand]

Hey! Not sure if I'm doing something wrong here, but I see the sourcemap next to my files and it's not being parsed by my log viewer... Anyone else using source maps?

#91

[floydspace]

hey @kennandavison could you try using inline sourcemaps to reduce the number of the possible reasons of the issue

custom:
  esbuild:
    sourcemap: inline

[kennand]

Tried that and still having troubles getting sourcemap associated.

More context: using seed.run (which has a Sentry-like stack trace viewer). Was using serverless-bundle which worked, but not working here. Trying to also see if it's on their end as well!

[floydspace]

Hey @kennandavison, I'm trying to test the issue. Have prepared the stack for seed.run, it's perfectly deployed, but not sure how to reproduce your issue, could you please guide me where is that Sentry-like stack trace viewer. thank you

[kennand]

https://seed.run/docs/issues-and-alerts.html#enabling-issues should get it up and running

[floydspace]

@kennandavison I bet you're expecting stack trace like this:

with exact pointer where is the issue?

[kennand]

Yep, the line number/pointer is off when using esbuild, but correct when using serverless bundle. Are you seeing the same thing?

[floydspace]

@kennandavison yes I could reproduce it. so with serverless-esbuild plugin I cannot see the pointer to the source code line.
But I cannot help here much, because it's esbuild feature itself. Esbuild just creates source maps a little bit differently than webpack. I would raise the issue in their repository. My assumption is you probably have to push source code to lambda along with bundled one to have it worked.

[floydspace]

@kennandavison no the assumption does not work either, so it's definitely esbuild issue

[kennand]

Got it - thanks for checking this out!

[floydspace]

@kennandavison let me know if you gonna raise the issue in esbuild repo.
Closing this issue.

[kennand]

Hey - turns out you just need to add an env var! Serverless-bundle automatically does this while serverless-esbuild doesn't. https://serverless.pub/aws-lambda-node-sourcemaps/#enabling-the-native-source-map-support-for-node-12

Hope this helps someone else using sourcemaps :)

[pierreh]

also make sure to use sourcemaps: true instead of sourcemaps: external this will set sourceMappingURL correctly.