Next-generation configuration loading #2629
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
novemberborn
force-pushed
the
async-config
branch
3 times, most recently
from
1f9aff2 to
d57d997
Compare
… loading in the ESLint plugin helper
And export as an individual member, rather than default.
novemberborn
force-pushed
the
async-config
branch
2 times, most recently
from
485f784 to
6250ad2
Compare
novemberborn
force-pushed
the
async-config
branch
from
6250ad2 to
95f739b
Compare
novemberborn
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Our desire to expose configuration to our ESLint plugin has stopped us from enabling asynchronous configuration loading. However, using Atomics and worker threads we can make this work!
This adds support for
.mjsfiles, fixing #2346. We can remove the special handling ofava.config.jsfiles, relying on Node.js to follow the package type instead. We can now also support asynchronous factories.This also lays groundwork for #2285.