-
Notifications
You must be signed in to change notification settings - Fork 11
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
refactor: remove concept of pending resolution #57
Conversation
Huh, just rediscovered why it was done this way. I'll do a separate PR outlining why this is done. |
Actually, this makes sense. We just need to return back a result for each specifier and a result for the total npm install. Then we need to store the npm install error in the graph probably. This will help enable dynamic imports of npm specifiers to fail individually. |
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.
LGTM
No longer necessary because we resolve from deno_graph in a batch. This will simplify things.
I'll integrate this in the CLI before marking this as ready.