-
-
Notifications
You must be signed in to change notification settings - Fork 41
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: Use our data set to work out if a module is a node module #338
Conversation
const getConfiguredNodeVersion = require("../util/get-configured-node-version") | ||
const getSemverRange = require("../util/get-semver-range") | ||
const visitImport = require("../util/visit-import") | ||
const visitRequire = require("../util/visit-require") | ||
const mergeVisitorsInPlace = require("../util/merge-visitors-in-place") | ||
const { | ||
NodeBuiltinModules, | ||
} = require("../unsupported-features/node-builtins.js") |
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.
nits: we could move node-builtins.js
to outer - it's now not just used by those rules. :)
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.
Where do you think we should put the directory?
I was also thinking about going through and merging the no-deprecated-api
into the unsupported-features
so its all in one place as a consistent data set 🤔
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.
Where do you think we should put the directory?
maybe /lib/dataset/
?
I was also thinking about going through and merging the no-deprecated-api into the unsupported-features
It would be nice if these rules could share data, so we don't have to worry about updating one and forgetting the other.
closes #337