Use index.js as npm package entry point #11
Merged
Conversation
This file contains hidden or 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
michaelbromley
added a commit
that referenced
this pull request
Dec 10, 2015
Use index.js as npm package entry point
Owner
|
Thanks! |
Contributor
Author
|
Thanks for accepting the patch! Can you make a new release with the changes? |
Owner
|
Ok - just done and published 0.9.3 to npm! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
index.jswas presumably added to support CommonJS syntax; however,package.jsonwas not updated to point at this file. Thus, the name of the module was not being exported correctly if one were torequire()the package in theirangular.modulelist.This PR fixes that.