Closed rubiesonthesky closed 6 days ago
To clarify this is just a warning right? It does not cause the build to fail?
I think we should not vendor the offline
integration like we do with the rest because of this problem. Opening a PR!
Well nvm we don't vendor offline
at all, but I guess webpack complains about it. I think we have to alias the localforage
import with a dynamic require, or vendor in localforage
to get around this problem.
@mydea could you take a look on Monday?
Yeah luckily it's just warning, so it does not block building the application. :)
I can see that in package.json, packages immediate
, lie
and localforage
are now added when they weren't present earlier.
These are the only Sentry packages that we have installed
"@sentry/browser": "7.112.0",
"@sentry/types": "7.112.2",
There's another solution here we can do which sucks, but is better than nothing to unblock us.
@sentry-internal/integrations
package, and put all of the integrations other than offline into that package.@sentry/integrations
depend on @sentry-internal/integrations
, and then have it use offline
integration@sentry-internal/integrations
Sorry for the trouble @rubiesonthesky - appreciate your patience while we get a fix out!
We've released v8.0.0 which dropped the offline integration overall - so updating to this should get rid of this warning! I'll close this issue, if you still run into this on the latest version of the SDK, please re-open the issue - thank you!
Is there an existing issue for this?
How do you use Sentry?
Sentry Saas (sentry.io)
Which SDK are you using?
@sentry/browser
SDK Version
7.112.0
Framework Version
No response
Link to Sentry event
No response
SDK Setup
Steps to Reproduce
This is Angular app, using Angular 16. (And using
@sentry/browser
)ng build
Expected Result
Not to log any warnings
If I want earlier functionality, do I need to set
integrations: []
ininit
? This was not covered in the release notes.Actual Result
Warning printed