Follow apf

[cromefire]

• 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

Package + Version

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

Version:

5.0.2

Description

The Angular Package Format defines esm2015 as the field to use for esm + es2015 so that should be used to denote esm instead of module

Ref: #1973 (comment)
Angular Package Format

[HazAT]

Note, this was angular emits:

  "name": "@angular/core", 
  "module": "./fesm5/core.js", 
  "es2015": "./fesm2015/core.js", 
  "esm5": "./esm5/core.js",
  "esm2015": "./esm2015/core.js",
  "fesm5": "./fesm5/core.js",
  "fesm2015": "./fesm2015/core.js",
  "main": "bundles/core.umd.js", 
  "typings": "core.d.ts",
  "sideEffects": false

I would like to emit an additional build to fix this instead of replacing it, wdyt?

[cromefire]

It's hard to produce fesm

[HazAT]

Why is it hard, shouldn't it just be target es2015 and module es6?

[cromefire]

You have to put everything into a single module file

[cromefire]

That's the difference of fesm vs. esm, but you could think of producing the other things excluding fesm, but it would be good if we had a top level file in utils to enable resolution using that mechanism

[cromefire]

Okay I looked around a bit and it seems that people just use rollup in es mode for fesm so that's easy

[HazAT]

@cromefire I would really prefer to have this in addition to module instead of replacing it.
Thanks for investigating tho

[cromefire]

Module is also in the apm standard

[cromefire]

But provides (f)esm5

[HazAT]

@cromefire what do you think?
#1989 (comment)

[cromefire]

This is more that proposed in #1989