-
-
Notifications
You must be signed in to change notification settings - Fork 73
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
Support loading ECMAScript modules, but drop sync API (#230) #234
Conversation
src/index.js
Outdated
} | ||
} | ||
|
||
// prefers import, which won't work in sync mode |
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.
Will it better to check Node.js version?
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.
I think feature detection is a bit cleaner, as it might support different runtimes (like Deno). Although in this case, the feature-detection is quite Node-specific and I don't find documentation for it in the Node 10 docs.
3475c1c
to
0a96011
Compare
c8a7e26
to
fac2e53
Compare
I will put this task on a little hold until Node.js 12 EOL |
@ai That time has come. See the release chart. |
Released in 4.0 |
Notable Changes
This PR implements support for
.mjs
config files (and.js
config files within"type": "modules"
projects). To support that without much hassle, support for synchronously loading configs is dropped, as ECMAScript Modules are loaded inherently async.Commit Message Summary (CHANGELOG)
Type
SemVer
Issues
#230
Checklist