-
-
Notifications
You must be signed in to change notification settings - Fork 22
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
Unexpected result NotFound('node:http')
with imports
field and builtins: true
option
#164
Comments
Rolldown currently will handles Rolldown treats |
I don't understand one thing though: what's the issue? Why should it return this result? What does it return instead? |
For resolving |
… imports and exports closes #164 According to the ESM specification https://nodejs.org/api/esm.html#resolution-and-loading-algorithm ``` // PACKAGE_RESOLVE(packageSpecifier, parentURL) // 3. If packageSpecifier is a Node.js builtin module name, then // 1. Return the string "node:" concatenated with packageSpecifier. ``` The returned value should be prefixed by `node:`
… imports and exports closes #164 According to the ESM specification https://nodejs.org/api/esm.html#resolution-and-loading-algorithm ``` // PACKAGE_RESOLVE(packageSpecifier, parentURL) // 3. If packageSpecifier is a Node.js builtin module name, then // 1. Return the string "node:" concatenated with packageSpecifier. ``` The returned value should be prefixed by `node:`
… imports and exports (#165) closes #164 According to the ESM specification https://nodejs.org/api/esm.html#resolution-and-loading-algorithm ``` // PACKAGE_RESOLVE(packageSpecifier, parentURL) // 3. If packageSpecifier is a Node.js builtin module name, then // 1. Return the string "node:" concatenated with packageSpecifier. ``` The returned value should be prefixed by `node:`
While resolving
#fs
, oxc-resolver correctly maps#fs
tofs
. Then oxc-resolver returnsNotFound("fs")
, which is also correct withbuiltins: false
.However, with
builtin: true
, oxc-resolver should returnBuiltin('fs')
orBuiltins('node:http')
.The text was updated successfully, but these errors were encountered: