-
-
Notifications
You must be signed in to change notification settings - Fork 598
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
detecting builtins #1048
Comments
If you are sure this is a bug or documentation issue, please take the time to refile this issue using the issue template. Hey there, thanks for opening an issue - Unfortunately you missed (or may have disregarded) the message about issue templates being required. Because our issue template was removed, we assume that this is a support request, and that's not something we offer here. Also, if you refile, please don't ignore Issue sections. They're in the template because they're useful to the maintainers of this project. |
yea, missed it cuz i used "references in a new issue"... |
That's the second time that's bit us. Major GitHub fail there. Do me a solid and plop an appropriate template in there. |
Hey folks. This issue hasn't received any traction for 60 days, so we're going to close this for housekeeping. If this is still an ongoing issue, please do consider contributing a Pull Request to resolve it. Further discussion is always welcome even with the issue closed. If anything actionable is posted in the comments, we'll consider reopening it. ⓘ |
plugins/packages/node-resolve/src/index.js
Line 167 in 12e1fee
i see that you are using sindres
builtin-modules
package to detect if something is builtinOne thing it dose not handle is sub modules and the node protocol, that's what his other related package: is-builtin-module is for... it handles things like
node:fs
,fs/promises
andnode:fs/promises
Maybe you want to use is-builtin-module instead?
The text was updated successfully, but these errors were encountered: