@sentry/ember

[jherdman]

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

Package + Version

• @sentry/browser
• @sentry/node
• raven-js
• raven-node (raven for node)
• other: @sentry/ember

Version:

6.6.0

Description

After upgrading to ember-auto-import 2.0.1 we see the following error:

Something is askew, but I'm not really sure what's required given that this package works fine with ember-auto-import v1.

[netes]

Bumping, same here after upgrading to ember-auto-import v2.

[k-fish]

Hey @jherdman, @netes, thanks for mentioning it. I just tried with an example app using @sentry/ember and it seems to work, I see the chunk auto-importing the browser esm. Can either of you share how you are setting up your config so I can try to repro (omitting anything private)?

A few more questions to help me narrow this down; do you see this immediately on app load? Are you using Fastboot? Embroider?

For reference, my working branch of an example app with auto import v2 here: k-fish/ember-sentry-performance-example@769affa

[jherdman]

Your example is pretty much what we're doing. We see this immediately upon deploy to production, and NOT in development or testing.

[netes]

I can confirm what @jherdman wrote, it's happening only on production.

[k-fish]

Great, more info to build a repro case helps.

Is it just having the app built with the production environment (ember s --environment production) or is it actually deploying to production that causes it to break? Can you repro locally? The example app in production mode works and the module exists in the generated chunk.

Are any of the chunks failing to load before this error?

If you're having errors and it's the deploying (to a CDN) that is causing an issue, it might be something to do with the publicAssetURL, looking through the recent auto-import issues, embroider-build/ember-auto-import#415

[jherdman]

I tried tweaking our publicAssetURL settings per the linked issue, and the issue persists.

We are indeed using broccoli-asset-prepend, broccoli-asset-rev, and broccoli-asset-rewrite, but are not uploading to a CDN.

Are you on the Ember Discord under this username? I could give you the URL of a private staging server with this error if that helps.

[k-fish]

Yup, same username. I'll log in.

[jherdman]

@netes something @k-fish and I just noticed is that all of the generated chunk files for my app are 404'ing. This is likely due to this: https://github.com/ef4/ember-auto-import/blob/master/docs/upgrade-guide-2.0.md#inject-entry-chunks-directly-in-indexhtml. Are you able to confirm this is the case for you too?

[k-fish]

👍 Closing for now as it looks like it's been fixed (or at least addressed) in 2.0.2 of auto-import.

[lougreenwood]

@netes and myself also tried V2.0.2, but this didn't make a difference for us. We were using the prepend field mentioned in the release notes, but only with the value of /.

[k-fish]

@lougreenwood check the network tab to see if the chunk is loading properly, if you have any errors in loading the chunks it's likely something to do with your asset url as mentioned above. If not, let me know.