Let's publish to npm #497
Merged
Let's publish to npm #497
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
|
@lukehorvat - The Wak script doesn't work because it sends the wrong parameters up to the google closure website. |
|
Has this been published to npm yet? |
|
👍 |
|
Thanks @MrRio! 😊 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Resolves #183.
Filled in the remaining package.json fields to allow this package to be published to npm, and added CommonJS support so people can use this package with Browserify. You'll need to re-generate the
distdirectory since I can't seem to run the build script on my machine.Please note that npm != Node.js, so I recommend publishing this package to npm as soon as possible. We can work on adding Node.js support at a later date.