-
Notifications
You must be signed in to change notification settings - Fork 265
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
FYI: This project has been hard forked #259
Comments
This was referenced Jun 19, 2020
karfau
added a commit
to karfau/xmldom-legacy
that referenced
this issue
Jun 19, 2020
Since there hasn't been an update to the repo for a long time, [jindw#259](this project has been forked). I hope this PR helps increase the visibility (besides making it very easy for the original maintainer to make it a statement, e.g. before archiving the repo.)
This issue should be pinned. I guess. Thanks a lot. |
Closed
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If you are installing the
xmldom
package from npm, please note that it no longer comes from this repo (jindw/xmldom).The original maintainer has not had time to publish updates to the package in quite some time, thus why so many issues and pull requests are piling up in this repo.
A handful of us have resumed maintenance of this package at a hard fork here: https://github.com/xmldom/xmldom including new versions now being published to npm: https://www.npmjs.com/package/xmldom
If you have questions, concerns, or would like to contribute, please do so at the new repo. 😀
The text was updated successfully, but these errors were encountered: