-
Notifications
You must be signed in to change notification settings - Fork 5
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
Publishing to npm #1
Comments
No I havent published it yet. I was waiting for jsfmt to stabilize a little first. We were talking about exposing options when using require. Has that made any progress yet? |
Yup, working on it now. Cool, good to know I didn't just miss it in npm. |
Yeah I wanted to make sure that I didn't publish something that would be broke a day later. I'll watch the repo to keep up to date. |
Do you think it has reached a stable point? Thanks for putting this task together. |
I just need to update it to the latest version, then implement the config options. When I first made this there was no such feature. |
Hey @james2doyle! I'm looking into using this for a project I'm working on; it seems really promising. Is there anything you could use a hand with for getting this on npm? |
Yeah actually. If you could update the project to the latest version of the On Tuesday, August 5, 2014, Brian Mock notifications@github.com wrote:
James Doyle t: @james2doyle https://twitter.com/james2doylew: ohdoylerules.com |
Hi, any progress on getting this to npm? |
Once I get this up-to-date it should be good to go |
Hey, I was wondering if this was already published and taken down or just not published yet. If jsfmt ends up using Grunt (there's some push to use Make instead) I was hoping to use this to format jsfmt.
The text was updated successfully, but these errors were encountered: