Webpack caching with sentry release

[alex-kharchenko-moc]

Hello, I'm trying setup webpack cache in my project, and when I was added this configs

cache: {
        type: 'filesystem',
        cacheDirectory: process.env.CACHE_DIRECTORY
}

webpack caching works fine (first build => 146s / second build => 60s).

But when I am changing sentry release number and start build she is always takes 146s or more.

Please help me understand what I am doing wrong...

P.S. This is my SentryWebpackPlugin configs

sentry: {
        url: SENTRY_SERVICE_URL,
        urlPrefix: `~/${SOURCE_DIRECTORY}`,
        authToken: SENTRY_AUTH_TOKEN,
        org: 'sentry',
        project: SENTRY_FRONTEND_PROJECT,
        release: [SENTRY_FRONTEND_PROJECT, SENTRY_RELEASE].join('-'),
        include: output,
        silent: true,

        // Do not block deploy when sentry is not available
        errorHandler: (err, invokeErr, compilation) => {
            compilation.warnings.push(`Sentry CLI Plugin: ${err.message}`);
        }
    }

[lforst]

Hi, thanks for writing in.

I think what you're describing is working more or less as designed. The webpack plugin will inject the provided release into your bundles. As a logical consequence, when you change the release number, it will invalidate the cache and the build takes longer again.

I don't really know if this is something we can fix. Do you have any suggestions?

[alex-kharchenko-moc]

@lforst Thanks for getting back to me so quickly. Currently I don't have any suggestions

[andreyvolokitin]

@lforst here's a related issue: getsentry/sentry-webpack-plugin#93

AFAIU, we need to have a release info existing in our JS code, so we need to inject it somewhere. Runtime chunk is always present and small, so it's optimal for injecting frequently changing release info, while other code won't invalidate cache.

The problem is that introduced entries option only handles entries, and runtime chunk is not an entry, but a chunk

So suggestion is to allow using runtime chunk for release injection. But I guess as a workaround we could create an empty entry just to inject a release?

[lforst]

Attempt to fix this going out in the next release: getsentry/sentry-javascript#7870

[github-actions]

This issue has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you label it Status: Backlog or Status: In Progress, I will leave it alone ... forever!

---

"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀