-
Notifications
You must be signed in to change notification settings - Fork 227
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
chore: avoid nodejs modules #487
base: master
Are you sure you want to change the base?
Conversation
@@ -2,7 +2,9 @@ | |||
|
|||
import eslint from '@eslint/js' | |||
import prettierRecommended from 'eslint-plugin-prettier/recommended' | |||
// eslint-disable-next-line import/no-unresolved |
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 this is due to import-js/eslint-plugin-import#1485 which includes a fix that works for me (locally) but produces a couple extra warnings.
@@ -11,6 +13,9 @@ export default tseslint.config( | |||
}, | |||
eslint.configs.recommended, | |||
...tseslint.configs.strictTypeChecked, | |||
pluginImport.recommended, | |||
// @ts-expect-error not sure why the plugin isn't type correctly, but it works... |
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 removed this after including the fix mentioned above and did not see any errors.
Nice! This was the plugin I was looking at last night when trying to figure out how we can best avoid breaking non-Node runtimes. |
Only maintainers should be approving PRs.
This adds a new eslint plugin to avoid node's built in modules, and hopefully help keep our package more cross-platform compatible.