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

Handle ERR_PACKAGE_PATH_NOT_EXPORTED gracefully #109

Closed

Conversation

ctavan
Copy link

@ctavan ctavan commented May 18, 2020

Fixes nodejs/modules#104
Closes nodejs/modules#108


I think that this is a more appropriate solution to nodejs/modules#104 than nodejs/modules#108

For more context see uuidjs/uuid#444 (comment) and nodejs/node#33460

@ctavan ctavan force-pushed the handle-missing-exports-gracefully branch from 22a941e to 9da2f9c Compare May 19, 2020 11:20
@pngwn
Copy link
Member

pngwn commented Jul 31, 2020

I have been using your branch with one of my projects and while it is definitely a good fix and working well, it is incredibly noisy. I'm not sure what the best approach is here. When I say noisy, I mean a screen full of warnings.

@benmccann
Copy link
Member

FYI, it was just mentioned in nodejs/node#33460 that nodejs/node#49445 is being considered as the intended solution to grabbing the package.json

@benmccann
Copy link
Member

Thanks for proposing a fix for this! I'm going to close this one for now in favor of #119, which reduces the amount of screen output a bit

@benmccann benmccann closed this Aug 3, 2020
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

Successfully merging this pull request may close these issues.

Feature: Browser-compatible build that includes CommonJS Feature: Retrievable module metadata
3 participants