-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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(NA): node module main field resolution for new platform #63886
fix(NA): node module main field resolution for new platform #63886
Conversation
Pinging @elastic/kibana-operations (Team:Operations) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is the setting we've been using in the base optimizer, so I'm fine using it, and the default is ['browser', 'module', 'main']
, I'm wondering if we actually need the browserify
entry but LGTM either way.
@spalger I don't think we need the |
@elasticmachine merge upstream |
@elasticmachine merge upstream |
💚 Build SucceededHistory
To update your PR or re-run it, just comment with: |
7.x: 07c7ee2 |
…63886) * fix(NA): node module main field resolution for new platform * chore(NA): remove browserify from kbn optimizer main fields Co-authored-by: Elastic Machine <[email protected]>
…63886) * fix(NA): node module main field resolution for new platform * chore(NA): remove browserify from kbn optimizer main fields Co-authored-by: Elastic Machine <[email protected]>
…64302) * fix(NA): node module main field resolution for new platform * chore(NA): remove browserify from kbn optimizer main fields Co-authored-by: Elastic Machine <[email protected]> Co-authored-by: Elastic Machine <[email protected]>
…64304) * fix(NA): node module main field resolution for new platform * chore(NA): remove browserify from kbn optimizer main fields Co-authored-by: Elastic Machine <[email protected]> Co-authored-by: Elastic Machine <[email protected]>
That adds the same mainFields resolution we were using in the legacy optimizer in order to make the
disallow syntax rule
to work correctly.