-
-
Notifications
You must be signed in to change notification settings - Fork 185
fails to resolve packages with the same name as core modules #25
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
Comments
michaelficarra
referenced
this issue
in michaelficarra/commonjs-everywhere
Jul 20, 2013
this is important because the versions are all loosely specified using *
merged in 0.6.0 |
4 tasks
searls
added a commit
to searls/resolve
that referenced
this issue
Mar 23, 2018
These are obviated by the shadowed_core test added in browserify#148
ljharb
pushed a commit
to searls/resolve
that referenced
this issue
Apr 5, 2018
These are obviated by the shadowed_core test added in browserify#148
ljharb
pushed a commit
to searls/resolve
that referenced
this issue
Apr 5, 2018
These are obviated by the shadowed_core test added in browserify#148
ljharb
pushed a commit
to searls/resolve
that referenced
this issue
Apr 5, 2018
These are obviated by the shadowed_core test added in browserify#148
ljharb
pushed a commit
to searls/resolve
that referenced
this issue
Apr 7, 2018
These are obviated by the shadowed_core test added in browserify#148
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This causes problems when trying to resolve the
punycode
orquerystring
modules, which are both also node core modules.The text was updated successfully, but these errors were encountered: