Missing possibility to overwrite all nextjs keys to blitzjs in @sentry/nextjs

[prisis]

• [x] Review the documentation: https://docs.sentry.io/
• [x] Search for existing issues: https://github.com/getsentry/sentry-javascript/issues
• [x] Use the latest release: https://github.com/getsentry/sentry-javascript/releases
• [ ] Provide a link to the affected event from your Sentry account

Package + Version

• [ ] @sentry/browser
• [ ] @sentry/node
• [ ] raven-js
• [ ] raven-node (raven for node)
• [x] other:
  • [x] @sentry/nextjs

Version:

6.7.1

Description

Would i be possible to get a possibility to overwrite all .next keys with a option to .blitz?

[flybayer]

Fyi, we are changing some blitz internals, so likely this will just work as expected

[prisis]

Then this is not needed anymore?

const SentryWebpackPluginOptions = {
    include: ".blitz/",
    urlPrefix: "~/_blitz",
    // Additional config options for the Sentry Webpack plugin. Keep in mind that
    // the following options are set automatically, and overriding them is not
    // recommended:
    //   release, url, org, project, authToken, configFile, stripPrefix,
    //   urlPrefix, include, ignore
    // For all available options, see:
    // https://github.com/getsentry/sentry-webpack-plugin#options.
};

and in sentry.server.config.js

// This file configures the initialization of Sentry on the server.
// The config you add here will be used whenever the server handles a request.
// https://docs.sentry.io/platforms/javascript/guides/nextjs/

import * as Sentry from "@sentry/nextjs";
import getConfig from "next/config";
import { RewriteFrames } from "@sentry/integrations";
import serverEnvironment from "./config/server-environment";

const SENTRY_DSN = serverEnvironment.NEXT_PUBLIC_SENTRY_DSN;

const config = getConfig();
const distDir = `${config.serverRuntimeConfig.rootDir}/.blitz`;

Sentry.init({
    dsn: SENTRY_DSN,
....

[flybayer]

Yeah my goal is that it should would exactly the same as with next without additional config.

[lobsterkatie]

@flybayer - Any update on this from your end?

[flybayer]

@lobsterkatie we're progressing on our nextjs fork migration which is the blocker here I think. Making progress but not finished yet.

[lobsterkatie]

Great, thanks. Let us know!

[prisis]

With the latest v0.40 releases this should be fixed, correct me if im wrong @flybayer

[flybayer]

@prisis yes, 0.40 releases no longer use .blitz, only using .next. So please test and report back.

That said, there is also a possibility we'll change .next default to .blitz before 1.0.

[prisis]

Tested and it looks good, for my use cases