build folder is missing in 7.0 beta

[jmfrancois]

Is there an existing issue for this?

• I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
• I have reviewed the documentation https://docs.sentry.io/
• I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases

How do you use Sentry?

Sentry Saas (sentry.io)

Which package are you using?

@sentry/browser

SDK Version

7.0.0-beta.1

Framework Version

No response

Link to Sentry event

No response

Steps to Reproduce

1. Open https://unpkg.com/browse/@sentry/browser@7.0.0-beta.1/

Expected Result

I should see a build folder as in current stable release https://unpkg.com/browse/@sentry/browser@6.19.7/build/

Actual Result

only non UMD distribution are available as ism and cjs

[lobsterkatie]

Hi, @jmfrancois.

Thanks for writing in. To my knowledge, use of our SDK through CDNs other than our own has never been a supported use case. The SDK is available on our own CDN, and on npm. More information can be found here.

[jmfrancois]

@lobsterkatie unpkg.com is just exposing the content from npm so the one that is published.
I just want to be sure you will continue as before to publish the bundle on npm which is not the case with latest 7.0 :/

[lforst]

From version 7 onwards we stopped publishing CDN bundles on npm. Only cjs and esm code will live there. We recommend using the Sentry CDN or building the bundles yourself.

[lobsterkatie]

unpkg.com is just exposing the content from npm so the one that is published.

Yes, I understand, and I apologize, I should have been clearer. I know that it has worked in the past, and how, but it was never an officially-supported way of getting the SDK, and not one we're maintaining in v7.

[lobsterkatie]

I'm going to close this, as the SDK is working as it should, but please feel free to let us know if you're having trouble using the Sentry CDN or our npm packages.

[agarzola]

Hi! I would encourage the Sentry team to reconsider this decision. We rely pretty heavily on Dependabot keep dependencies up-to-date across all of our active client projects. This works because client-side library maintainers either include bundles in their published packages or use postinstall scripts to build them for you on installation.

The decision to omit bundle files from the published package puts teams who wish to use said bundles in the position of having to hard-code version numbers in a template or configuration file somewhere in their project, which in turn makes it harder to stay abreast of the latest/greatest features and bug/security patches Sentry has to offer.

Having said all of that, our team put together a best of both worlds solution that uses Sentry’s CDN using the version of @sentry/browser tracked in our project’s package.json. Sharing it here in case someone in a position similar to ours is, like us, not satisfied with having to hard-code a version number in a CDN URL.

[wfjsw]

I still find myself under an awkward situation where those classic web pages requires CDN version of Sentry and Sentry-provided CDN is not accessible at all. Previously a mirror of CDNJS was used which depends on serving the NPM build dir, and after the build dir is gone the CDNJS is down as well.

Hopefully Sentry team will reconsider this decision. I fail to get the principle behind this change when it is really a common practice demonstrated by other libraries to host built IIFE file on NPM.