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

fix(builtin): fix for issue 834 #847

Merged
merged 1 commit into from
Jun 11, 2019

Conversation

gregmagolan
Copy link
Collaborator

Skip module root resolution in node resolver if main entry point. Also don't throw on resolve failure so that resolve does cascade down incase the module_root conflicts with the workspace name for fully resolved requires

Fixes #834

Skip module root resolution in node resolver if main entry point. Also don't throw on resolve failure so that resolve does cascade down incase the module_root conflicts with the workspace name for fully resolved requires
@gregmagolan gregmagolan merged commit c0fe512 into bazel-contrib:master Jun 11, 2019
siberex pushed a commit to siberex/rules_nodejs that referenced this pull request Jun 11, 2019
Skip module root resolution in node resolver if main entry point. Also don't throw on resolve failure so that resolve does cascade down incase the module_root conflicts with the workspace name for fully resolved requires
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Issue with nodejs_binary typescript entry_point defined as label (0.31.1 release)
3 participants