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
Npm.require
submodule for packages loaded with Npm.depend()
#3526
Closed
Closed
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
51d5d07
Merge pull request #1 from meteor/devel
gsuess e7351ae
Merge branch 'devel' of github.com:CulturalMe/meteor into devel
b00bda6
Merge branch 'devel' of github.com:meteor/meteor into devel
gsuess 651e541
Fix Npm.require() package sub-modules.
gsuess e6788b9
Npm.require load correct submodule
gsuess File filter
Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
This seems wrong? Why are we only looking at the first part of
name.split("/")
? And what ifname
has no slash in it?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.
No, I think this looks like it could be right. Isn't the point that
Npm.require("foo/bar")
should be resolved by saying "if this package usesfoo
, then we should be trying to resolve"foo/bar"
as within this module's foo"?Node require has a bunch of different options; for example,
require('foo/bar')
can pull in a file that's calledbar.js
inside thefoo
package. Or that's calledbar/index.js
insidefoo
.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.
If
name
has no slash thenname.split('/')[0] === name
.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.
Ah, I now understand. Agreed.