Uses one build for bower, npm, and global builds #26
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.
Take a look at this possible solution to the "one build to bind them" problem. The changes that matter are in
package.json
,bower.json
, andscript/build
. The rest is just committed generated source files.I think this should work, though without being able to properly release it, I can't really test it out.
The most controversial part of this may be that I changed the
main
attribute inpackage.json
to point to thedist/lib/index.js
file. If the release process callednpm publish dist
instead of justnpm publish
, we would not need to do that.