-
Notifications
You must be signed in to change notification settings - Fork 223
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
git repository dependence #233
Comments
Yeah, totally. |
@bago it looks like you are maintaining the github repository for mensch. Do you have access to the npm package, or do you know how to contact the collaborator? If not, it looks like the original author of that package hasn't contributed in years, perhaps a new fork is in order? Cheers, |
@jrit THANK YOU! |
closing as fixed |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
I would like to use Juice on a work project, but my prod server is erroring due the dependence on mensch. Specifically, because it references the mensch github repository instead of npm (company policy prohibits fetching git repository dependencies). I have requested that they publish the latest release (0.3.3) to npm. If they do so, would it be okay to reflect this change in the juice package.json?
Thanks for the awesome library. I would love to use it in production!
Cheers,
Max
The text was updated successfully, but these errors were encountered: