Skip to content
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

Could not resolve "node:path" - meow package #100

Closed
davidwinter opened this issue Aug 23, 2021 · 3 comments
Closed

Could not resolve "node:path" - meow package #100

davidwinter opened this issue Aug 23, 2021 · 3 comments

Comments

@davidwinter
Copy link

Hello! How should built-in node modules be handled? For example, trying to import the meow package, the following error happens:

/* esm.sh - error */
throw new Error("[esm.sh] " + "Could not resolve \"node:path\"  (Imported by \"meow\")");
export default null;

https://esm.sh/meow

I was trying to use import mapping with Deno to remap this, but looks like the package doesn't even reach me in order for Deno to be able to do this.

@ije
Copy link
Member

ije commented Aug 23, 2021

@davidwinter thanks, i will fix this asap!

@ije ije closed this as completed in 021448e Aug 23, 2021
@ije
Copy link
Member

ije commented Aug 23, 2021

fixed in 021448e, pls try again!

@davidwinter
Copy link
Author

Thanks, @ije - that resolved that issue. Though this might be unrelated, but another error I now encounter as a result of the dependency tree of meow is the following, where an export isn't correct:

error: Uncaught SyntaxError: The requested module '/v45/[email protected]/deno/path-browserify.js' does not provide an export named 'resolve'
    at <anonymous> (https://cdn.esm.sh/v45/[email protected]/deno/yargs-parser.js:1:343)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants