-
Notifications
You must be signed in to change notification settings - Fork 19
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
Publish to npm #3
Comments
Open
Hey @danfinlay, I don't believe there was a specific reason, I usually have private set to true when in development as a defensive measure to prevent an accidental publish. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This wasn't published to npm.
Posting this issue makes me nervous that someone else will squat it, so I'm registering it now.
If you'd like permission to update, hit me up and I'll share/hand it over.
I noticed it was marked
private: true
which blocks publication, but also licensed MIT, so I just forked it to publish. Let me know if there was a good reason for this, and I could unpubish.https://www.npmjs.com/package/ens-validation
The text was updated successfully, but these errors were encountered: