-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Release a new version to npm to solve the "node: latest" issue #853
Comments
Hello maintainers! This issue (and the associated PR #854) can be closed, since #865 was merged and 3.7.0 was released on NPM. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi muaz-khan!
Any chance you could release a new version of RTCMultiConnection to npm? We're using it in our project but are getting yarn install errors due to 3.6.9's requirement of node: latest.
I see that you've already fixed this problem on the repo, but it just hasn't hit npm yet.
So, would you mind releasing a new version of npm so that we don't need to use the
--no-engines
flag to install your package? Also, if you could also do one minor tweak to include Node 12 (unless there is actually an incompatibility problem).The text was updated successfully, but these errors were encountered: