You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Of course import() is only available on Node.js 13. This should fail gracefully on Node.js 10 and 12.
import() is asynchronous. The loadConfig() method should still return synchronously when loading other files.
The documentation needs to be updated to explain when .mjs config files make sense and when users should use .cjs or .js files. Mostly this is to do with ESLint compatibility (since rules must currently be synchronous).
The text was updated successfully, but these errors were encountered:
* When worker threads are available, support asynchronous configuration loading in the ESLint plugin helper
* Experimental implementation of next-generation configuration loading. This adds support for `.mjs` files, fixing #2346. I've removed the special handling of `ava.config.js` files, relying on Node.js to follow the package type instead. We now also support asynchronous factories.
AVA recognizes
ava.config.mjs
files but refuses to load them. Let's fix this!See the code here:
ava/lib/load-config.js
Line 109 in 7f99aef
Of course
import()
is only available on Node.js 13. This should fail gracefully on Node.js 10 and 12.import()
is asynchronous. TheloadConfig()
method should still return synchronously when loading other files.The documentation needs to be updated to explain when
.mjs
config files make sense and when users should use.cjs
or.js
files. Mostly this is to do with ESLint compatibility (since rules must currently be synchronous).The text was updated successfully, but these errors were encountered: