Module instead of IIFE provided builds

[chaseWilliams]

Description

Our team can't use the IIFE build because they do not work in salesforce LWC, so instead we've just been internally building module builds with faro-web-sdk instead

Proposed solution

It would be nice if you could do something like this:

npm i @grafana/faro-web-sdk
npx faro-web-sdk build -- --output-format=module
echo ./node_modules/@grafana/faro-web-sdk/packages/web-sdk/dist/bundle/...

Context

The iife distribution does not work when either manually trying to load it as a <script> or when using loadScript, likely due to Salesforce's locker security constraints. This is because the Lightning Locker prevents third party scripts from setting global variables, which means even though the sdk loads, it isn't actually accessible at all for initializing in the application code.

[chaseWilliams]

Specifically this is how I changed the rollup.config.base.js to get a working build for us

-      file: `./dist/bundle/${module.bundleName}.iife.js`,
-      format: 'iife',
+      file: `./dist/bundle/${module.bundleName}.module.js`,
+      format: 'module',

[codecapitano]

Hey @chaseWilliams that's actually a nice enhancement.

Another option would be to include a module build by default.
Currently Faro includes cjs and esm builds and the IIFE bundle by default so users don't need to compile it themselves.

Wdyt about that option?

[chaseWilliams]

I think that sounds good, are you talking about also distributing a module build on the CDN as well? @codecapitano

[codecapitano]

Hey @chaseWilliams yes exactly.
We would have both, CDN and a sub dir in the NPM package.