-
-
Notifications
You must be signed in to change notification settings - Fork 60
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
Strict mode? #37
Comments
If it simplifies the maintenance burden on your end @defunctzombie - how would you feel about moving this repo to the |
@jprichardson I'd be open to that (clearly I have let this module go by the wayside) - what would that require logistically? |
I think you'd have to grant ownership of the project to somebody who is an admin in the browserify org, which would include both me and @jprichardson |
@calvinmetcalf you are already listed as a collaborator on the repo - is there some other action that "grants ownership" ? |
i just invited you into the browserify org |
@calvinmetcalf Should I see a notification somewhere for that? I received no email about it. |
I tried to invite you again @defunctzombie. Looks like you were invited by Substack awhile ago. See if you can visit this link: https://github.com/organizations/browserify/settings/profile and if there is something about accepting the invite. |
@jprichardson I get a 404 when I visit that link. |
@defunctzombie I canceled the invite, and then invited you again. Any email now...? |
@jprichardson @calvinmetcalf repository transferred. Feel free to remove me from the browserify organization. |
Wow! I've come here at the right moment... 😄 👍 |
@jprichardson It would be very nice if we'll get a NodeJS-compatibility. I.e. |
Any updates on this issue? |
Node v9.9.0 introduced some changes into the
assert
package. Most notably the introduction ofstrict
mode.Would you accept a PR introducing this new functionality and bringing this module up to date?
The text was updated successfully, but these errors were encountered: