Skip to content
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

Merged
merged 4 commits into from
Apr 23, 2020

Conversation

mistic
Copy link
Member

@mistic mistic commented Apr 17, 2020

That adds the same mainFields resolution we were using in the legacy optimizer in order to make the disallow syntax rule to work correctly.

@mistic mistic added chore Team:Operations Team label for Operations Team build v8.0.0 release_note:skip Skip the PR/issue when compiling release notes v7.8.0 v7.7.1 labels Apr 17, 2020
@mistic mistic requested a review from spalger April 17, 2020 17:47
@mistic mistic requested a review from a team as a code owner April 17, 2020 17:47
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-operations (Team:Operations)

Copy link
Contributor

@spalger spalger left a 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.

@mistic
Copy link
Member Author

mistic commented Apr 17, 2020

@spalger I don't think we need the browserify mainField I've just added to match the settings we were using, but I'll remove it for now in the kbn-optimizer. We can re add it later if we need it

@flash1293 flash1293 mentioned this pull request Apr 20, 2020
@mistic
Copy link
Member Author

mistic commented Apr 20, 2020

@elasticmachine merge upstream

@mistic
Copy link
Member Author

mistic commented Apr 22, 2020

@elasticmachine merge upstream

@kibanamachine
Copy link
Contributor

💚 Build Succeeded

History

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

@mistic mistic merged commit ebf5503 into elastic:master Apr 23, 2020
@mistic
Copy link
Member Author

mistic commented Apr 23, 2020

7.x: 07c7ee2
7.7: 5746c66

mistic added a commit to mistic/kibana that referenced this pull request Apr 23, 2020
…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]>
mistic added a commit to mistic/kibana that referenced this pull request Apr 23, 2020
…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]>
mistic added a commit that referenced this pull request Apr 23, 2020
…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]>
mistic added a commit that referenced this pull request Apr 24, 2020
…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]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
build chore release_note:skip Skip the PR/issue when compiling release notes Team:Operations Team label for Operations Team v7.7.1 v7.8.0 v8.0.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants