-
Notifications
You must be signed in to change notification settings - Fork 68
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: update package.json files #367
Conversation
packages/eslint-config/package.json
Outdated
"exports": { | ||
".": { | ||
"import": "./dist/legacy.mjs", | ||
"require": "./dist/legacy.cjs" | ||
}, | ||
"./flat": { | ||
"types": "./dist/flat.d.ts", | ||
"import": "./dist/flat.mjs", | ||
"require": "./dist/flat.cjs" | ||
}, | ||
"./legacy": { | ||
"types": "./dist/legacy.d.ts", | ||
"import": "./dist/legacy.mjs", | ||
"require": "./dist/legacy.cjs" |
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.
Legacy first is intentionally here to keep backward compatibility (also the legacy format can't load sub modules)
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.
Are we planning to eventually change it (e.g. when ESLint v9 gets out of RC)? Flat config will be the 'new default' at that stage.
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.
No, as I said, it's not compatible with the legacy format, so we have to keep the default export to the legacy - at some point, we could emit a warning message and ask to change over, but not right now as the ecosystem is still catching up. With the nuxt module, users don't usually need to care about this anyway
No description provided.