-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: Provide es5 build for esm #1991
Conversation
cc @cromefire @vkrol |
But in this case it's hard/impossible to opt into es2015+ |
It's up to the bundler, if it decides to select |
I looked around and found that for webpack you can set this to disable importing of module.exports = {
//...
resolve: {
mainFields: ['module', 'main']
}
}; |
@cromefire |
I skimmed the code and it seems to ignore it, but the opposite works: module.exports = {
//...
resolve: {
mainFields: ["es2015", "browser", 'module', 'main']
}
}; |
@cromefire Yes, webpack ignores this field and we need to configure them manually. |
It would be good if this gets added to the documentation |
@cromefire webpack documentation or Sentry documentation? |
It's in the webpack dos, but quite hidden, so the sentry docs, because the specific field Something like:
|
Yes, @cromefire I found this too but I am still confused now So, we will do:
right? |
I decided not to emit |
|
I'm preparing a PR that implements everything |
Yes |
@cromefire I will still release |
@cromefire what do you think about this?
|
Well right now the es2015 builds are es2015+ right now |
@cromefire please, can you elaborate more on that? |
They are 1:1 the source code, so what ever the source is, is the result |
That means that you are in charge of what will be in the output and have to look that your code runs in the latest browsers |
We could also publish it under |
If got some basic builds working with only minor problems |
For today just for |
Because of the utils I also have to get my rewrite script up and running again |
@cromefire I don't want to have a rewrite script, we have to solve it differently even if it means to build utils different |
Then index cannot have deep imports |
I know, but we expose a |
Indeed that would be the solution, but this may make the bundle larger depending on tree shaking |
Fixes #1989
Fixes #1988
Fixes #1984
Fixes #1979