Rakhymbek

> [@Rakhymbek](https://github.com/Rakhymbek) additionally I also noticed that in your dockerfile you are using `yarn install` but keep referencing `package-lock.json`. Setting this to `yarn.lock` did result in a successful build with...

> Hey [@Rakhymbek](https://github.com/Rakhymbek) thanks for writing in! > > There's a lot going on in this issue description which makes it a bit hard to identify the concrete ask. Just...

> [@Rakhymbek](https://github.com/Rakhymbek) disabling `instrumentationHook` will basically disable all server-side instrumentation for your next.js app, you want to keep that to `true` and initialize sentry in the `instrumentation.ts` file Do you...

> [@Rakhymbek](https://github.com/Rakhymbek) Yes, if you need server-side performance instrumentation you will need to keep `instrumentationHook: true` As I understand it, there’s no direct solution from Sentry for my issue with...

> [@Rakhymbek](https://github.com/Rakhymbek) if the domain is not available, by default an error will be thrown. > > You can however handle build errors in your `withSentryConfig` via: > > unstable_sentryWebpackPluginOptions:...

> Good to hear! I think the only documentation for that is probably [here](https://www.npmjs.com/package/@sentry/webpack-plugin#errorhandler) – this should also be available in v7. Thanks for the help, @chargome ! I’ll try...

> > Same here but without `getInitialProps` in`_app.tsx` but with initialProps related code in `_error.tsx`: > > Pages router and SSR only (ServerSideProps everywhere) > > ``` > > Error.getInitialProps...

> Same here but without `getInitialProps` in`_app.tsx` but with initialProps related code in `_error.tsx`: > > Pages router and SSR only (ServerSideProps everywhere) > > ``` > Error.getInitialProps = ({...