fix(nextjs): Catch exceptions when syncing plug-in's version

[iker-barriocanal]

Fixes #3441
Vercel's file system is read-only, so it throws an exception when trying to rewrite the plugin's version. This happens in runtime in every request in serverless environments.

Users are supposed to build the app before deploying it to Vercel (where the file system isn't read-only), since the plugin version must still be sync-ed.

[github-actions]

size-limit report

Path	Size
@sentry/browser - CDN Bundle (gzipped)	20.61 KB (+0.01% 🔺)
@sentry/browser - Webpack	21.49 KB (0%)
@sentry/react - Webpack	21.53 KB (0%)
@sentry/browser + @sentry/tracing - CDN Bundle (gzipped)	27.91 KB (0%)

[lobsterkatie]

Can you please summarize the issue in a sentence or two in the PR description, so someone coming here can have at least a little context without having to click through to the issue?

[pudgereyem]

Hey @iker-barriocanal, thanks for looking into this.

Users are supposed to build the app before deploying it to Vercel, since the plugin version must still be sync-ed.

Can you expand on what you mean here? What am I supposed to do here? I'm using Vercel's Github Integration which makes it so that Vercel builds the project for me and then deploys. There's nothing for me to do there. Will that work? I believe most people use Vercel that way.

[lobsterkatie]

Hey @iker-barriocanal, thanks for looking into this.

Users are supposed to build the app before deploying it to Vercel, since the plugin version must still be sync-ed.

Can you expand on what you mean here? What am I supposed to do here? I'm using Vercel's Github Integration which makes it so that Vercel builds the project for me and then deploys. There's nothing for me to do there. Will that work? I believe most people use Vercel that way.

I believe we're going to have to address this another way, given that workflow. We're working on it and will keep you posted.

[lobsterkatie]

Let's merge this - it's a good change just for safety's sake.

[kamilogorek]

Catching it is better than failing a deploy, although it's not clear what the user would need to do when this happens.

[pudgereyem]

I believe we're going to have to address this another way, given that workflow. We're working on it and will keep you posted.

@lobsterkatie cool, this is the only thing holding me back from using @sentry/nextjs as of now I believe. I'm not sure how easy it'd be for me to fork this repository and try to help out? My first attempt would be to see if it's possible to sync the versions through npm's postinstall script.

I'll do some other work in the meantime while waiting for this, since I think the (future) benefits of using @sentry/nextjs as you explained here sounds good.

All the best,
Victor

[iker-barriocanal]

Can you expand on what you mean here?

@pudgereyem

although it's not clear what the user would need to do when this happens.

@kamilogorek

If this happens, the plug-in's version doesn't match with the nextjs' version. Building the project locally, where the package.json can be modified, will sync these versions and then can be deployed to Vercel. This is not the best fix, but will stop breaking some apps for the moment.

[kamilogorek]

I know what will happen, but the user might not understand that based solely on that one console log :P

[iker-barriocanal]

@kamilogorek message updated.