Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Switching from package `xmldom` to `@xmldom/xmldom`, which resolves the security issue present in latest xmldom version 0.6.0: GHSA-5fg8-2547-mr8q The reason is that the maintainers were forced to switch to a scoped package since 0.7.0: xmldom/xmldom#271 - I only changed all occurences of `xmldom`, I didn't execute `npm install` or any other scripts. - Since there is no package-lock.json, I have no idea what version of xmldom people were actually using (depends on the time of running `npm install`), so I'm just assuming everybody was using 0.6.0 - fixes #41 I'm one of the xmldom maintainers. Don't hesitate to ask me questions about it.
- Loading branch information