nativescript-community / nativescript-community/sentry

No sourcemap in Sentry

Open
#23 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
18
Forks
12
PR merge metrics
No merged PRs in 30d

Description

I followed the readme closely (but had to make changes to make it work in the current NS setup), but I can't get sourcemaps to show up in Sentry. I'm 100% certain the source maps are uploaded (I validated in Sentry), and I'm also 100% sure that the release and dist in the Webpack sentryWebpackPlugin match up with what I configure in the plugin.

But it still ends up like this in Sentry:

image

Any idea what I can do here? I also tried with and without rewriting. My webpack looks like this now:

    if (env.uploadSourceMap) {
        webpack.chainWebpack((config) => {
            config.devtool = false;

            // Write away sourcemaps outside build dir.
            const customSourceMapDevToolPluginInstance = new SourceMapDevToolPlugin({
                append: `\n//# sourceMappingURL=[name].js.map`,
                filename: '../../../../../../sourceMap/[name].js.map'
            });
            config.plugin('SourceMapDevToolPlugin').use(customSourceMapDevToolPluginInstance);

            const customSentryWebpackPluginInstance = sentryWebpackPlugin({
                rewrite: true,
                release: {
                    name: `${appID}@${appVersion}+${buildNumber}`,
                    dist: `${buildNumber}.${platform}`,
                    setCommits: {
                        auto: true
                    }
                },
                ignoreFile: '.sentrycliignore',
                include: [join(__dirname, `platforms/sourceMap`)],
                telemetry: false
            });

            config.plugin('sentryWebpackPlugin').use(customSentryWebpackPluginInstance);
        });
    }

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the README and the shown Webpack configuration, especially SourceMapDevToolPlugin, the generated sourceMap directory, and sentryWebpackPlugin's release, dist, include, and rewrite settings. Verify that the uploaded artifacts match the event's release, dist, and source paths; done means Sentry renders the original source locations instead of the bundled stack.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript, webpack
Domain
build-system, observability
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.