ESM Configuration Tracking #824
Closed
thescientist13
started this conversation in
General
Replies: 3 comments
-
|
Good news, CosmicConfig now supports ESM! - cosmiconfig/cosmiconfig#224 (comment) |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I think as far as first party config files go, we'll be covered after #1312 which should be released in an alpha soon so closing this one out. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Looks like Import Attributes are now supported as of ESLint v9.14.0 🎉 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Overview
Coming out of the migration to ESM in #532, one of the "lagging" aspects of the migration is how tools handle their configuration files. Most of them actually do not support an ESM configuration file, so for these cases, you would have to use an extension of .cjs and still use CommonJS.
The below is a list of them, broken down between
dependenciesanddevDependenciesdependenciesThe impact configuration files related to our plugins, like Babel, PostCSS, etc
mjsextensions out of box cosmiconfig/cosmiconfig#224devDependenciesThese impact configuration files for Greenwood's own development, like ESLint, StyleLint, etc
import.metaMisc
Random stuff related to the ESM migration worth keeping loose track of
importjson support in NodesJS in cli/src/index.js, like for reading package.jsonrequireforrequire.resolve.paths, does there exist a similar convention for ESM, e.g.import.meta.resolve.pathspath=>new URL, more of a chore, and could be done postBeta Was this translation helpful? Give feedback.
All reactions