All notable changes to this project will be documented in this file.

This project adheres to Semantic Versioning.

• Security: XMLSerializer.serializeToString() (and Node.toString(), NodeList.toString()) now accept a requireWellFormed option. When { requireWellFormed: true } is passed, the serializer throws InvalidStateError for injection-prone node content, preventing XML injection via attacker-controlled node data. GHSA-j759-j44w-7fr8 GHSA-x6wf-f3px-wcqx GHSA-f6ww-3ggp-fr8h
  • Comment: throws when data contains -- anywhere, ends with -, or contains characters outside the XML Char production
  • ProcessingInstruction: throws when target contains : or matches xml (case-insensitive), or data contains characters outside the XML Char production or contains ?>
  • DocumentType: throws when publicId fails PubidLiteral, systemId fails SystemLiteral, or internalSubset contains ]>
• Security: DOM traversal operations (XMLSerializer.serializeToString(), Node.prototype.normalize(), Node.prototype.cloneNode(true), Document.prototype.importNode(node, true), node.textContent getter, getElementsByTagName() / getElementsByTagNameNS() / getElementsByClassName() / getElementById(), Node.prototype.isEqualNode()) are now iterative. Previously, deeply nested DOM trees would exhaust the JavaScript call stack and throw an unrecoverable RangeError. GHSA-2v35-w6hq-6mfw
• isEqualNode now correctly returns false for CDATASection nodes with different data

• The splitCDATASections serializer option is deprecated and will be removed in the next breaking release. The automatic splitting of "]]>" in CDATASection data was introduced as a workaround; use requireWellFormed: true or ensure CDATASection data does not contain "]]>" before serialization.

• updated dependencies

Thank you, @Jvr2022, @praveen-kv, @TharVid, @decsecre583, @tlsbollei, @KarimTantawey, for your contributions

• Security: XMLSerializer.serializeToString() (and Node.toString(), NodeList.toString()) now accept a requireWellFormed option (fourth argument, after isHtml and nodeFilter). When { requireWellFormed: true } is passed, the serializer throws InvalidStateError for injection-prone node content, preventing XML injection via attacker-controlled node data. GHSA-j759-j44w-7fr8 GHSA-x6wf-f3px-wcqx GHSA-f6ww-3ggp-fr8h
  • Comment: throws when data contains -->
  • ProcessingInstruction: throws when data contains ?>
  • DocumentType: throws when publicId fails PubidLiteral, systemId fails SystemLiteral, or internalSubset contains ]>
• Security: DOM traversal operations (XMLSerializer.serializeToString(), Node.prototype.normalize(), Node.prototype.cloneNode(true), Document.prototype.importNode(node, true), node.textContent getter, getElementsByTagName() / getElementsByTagNameNS() / getElementsByClassName() / getElementById()) are now iterative. Previously, deeply nested DOM trees would exhaust the JavaScript call stack and throw an unrecoverable RangeError. GHSA-2v35-w6hq-6mfw

Thank you, @Jvr2022, @praveen-kv, @TharVid, @decsecre583, @tlsbollei, @KarimTantawey, for your contributions

• implement ParentNode.children getter #960 / #410

• Security: createCDATASection now throws InvalidCharacterError when data contains "]]>", as required by the WHATWG DOM spec. GHSA-wh4c-j3r5-mjhp
• Security: XMLSerializer now splits CDATASection nodes whose data contains "]]>" into adjacent CDATA sections at serialization time, preventing XML injection via mutation methods (appendData, replaceData, .data =, .textContent =). GHSA-wh4c-j3r5-mjhp
• correctly traverse ancestor chain in Node.contains #931

Code that passes a string containing "]]>" to createCDATASection and relied on the previously unsafe behavior will now receive InvalidCharacterError. Use a mutation method such as appendData if you intentionally need "]]>" in a CDATASection node's data.

• updated dependencies

Thank you, @stevenobiajulu, @yoshi389111, @thesmartshadow, for your contributions

• preserve trailing whitespace in ProcessingInstruction data #962 / #42
• Security: createCDATASection now throws InvalidCharacterError when data contains "]]>", as required by the WHATWG DOM spec. GHSA-wh4c-j3r5-mjhp
• Security: XMLSerializer now splits CDATASection nodes whose data contains "]]>" into adjacent CDATA sections at serialization time, preventing XML injection via mutation methods (appendData, replaceData, .data =, .textContent =). GHSA-wh4c-j3r5-mjhp

Code that passes a string containing "]]>" to createCDATASection and relied on the previously unsafe behavior will now receive InvalidCharacterError. Use a mutation method such as appendData if you intentionally need "]]>" in a CDATASection node's data.

Thank you, @thesmartshadow, @stevenobiajulu, for your contributions

• update ownerDocument when moving nodes between documents #933 / #932

Thank you, @shunkica, for your contributions

• fix: replace \u2029 as part of normalizeLineEndings #839 / #838
• perf: speed up line detection #847 / #838

• updated dependencies
• drop jazzer and rxjs devDependencies #845

Thank you, @kboshold, @Ponynjaa, for your contributions.

• Implementation of hasAttributes #804

• locator is now true even when other options are being used for the DOMParser #802 / #803
• allow case-insensitive DOCTYPE in HTML #817 / #819

• simplify DOM.compareDocumentPosition #805

• updated devDependencies

Thank you, @zorkow, @Ponynjaa, @WesselKroos, for your contributions.

• lower error level for unicode replacement character #790 / #794 / #797

• updated devDependencies
• migrate renovate config #792

Thank you, @eglitise, for your contributions.

• fix: re-index childNodes on insertBefore #763 / #766

Thank you, @mureinik, for your contributions.

• restore performance for large amount of child nodes #748 / #760
• types: correct error handler level to warning (#759) #754 / #759

• test: verify BOM handling #758

Thank you, @luffynando, @mattiasw, @JoinerDev, for your contributions.

• restore more Node and ProcessingInstruction types #725 / #726
• getElements* methods return LiveNodeList<Element> #731 / #734
• Add more missing Node props #728, triggered by unclosed #724

• Update supported runtimes in readme (NodeJS >= 14.6 and other ES5 compatible runtimes)

• updates devDependencies

Thank you, @Ponynjaa, @ayZagen, @sserdyuk, @wydengyre, @mykola-mokhnach, @benkroeger, for your contributions.

• add Element.getElementsByClassName #722

• add missing types for Document.documentElement and Element.tagName #721 #720

Thank you, @censujiang, @Mathias-S, for your contributions

• DOMParser.parseFromString requires mimeType as second argument #713
• correct spelling of isHTMLMimeType in type definition #715 / #712
• sync types with exports #717 / #285 / #695

• minimum tested node version is 14 #710

Thank you, @krystofwoldrich, @marvinruder, @amacneil, @defunctzombie, @tjhorner, @danon, for your contributions

• Discussion
• Summary on dev.to

• feat: expose all DOM level 2 element prototypes #637 / #40
• feat: add iterator function to NodeList and NamedNodeMap #634 / #633

• parse empty/whitspace only doctype internal subset #692
• avoid prototype clash in namespace prefix #554
• report fatalError when doctype is inside elements #550

• test: add fuzz target and regression tests #556
• chore: improve .gitignore and provide .envrc.template #697
• chore: Apply security best practices #546
• ci: check test coverage in PRs #524
• docs: add missing commas to readme #566
• docs: click to copy install command in readme #644
• docs: enhance jsdoc comments #511

Thank you, @kboshold, @edi9999, @apupier, @shunkica, @homer0, @jhauga, @UdayKharatmol, for your contributions

• report more non well-formed cases #519 / #45 / #125 / #467 BREAKING-CHANGE: Reports more not well-formed documents as fatalError and drop broken support for optional and unclosed tags in HTML.

• Translate/drop non English comments #518
• use node v16 for development #517

Thank you, @brodybits, @cbettinger, @josecarlosrx, for your contributions

• dom: prevent iteration over deleted items #514/ #499

• use prettier plugin for jsdoc #513

Thank you, @qtow, @shunkica, @homer0, for your contributions

• dom: prevent iteration over deleted items #514/ #499

Thank you, @qtow, for your contributions

• dom: prevent iteration over deleted items #514/ #499

Thank you, @qtow, for your contributions

• Set nodeName property in ProcessingInstruction #509 / #505
• preserve DOCTYPE internal subset #498 / #497 / #117
  BREAKING CHANGES: Many documents that were previously accepted by xmldom, esecially non well-formed ones are no longer accepted. Some issues that were formerly reported as errors are now a fatalError.
• DOMParser: Align parseFromString errors with specs #454

• stop running mutation tests using stryker #496
• make toErrorSnapshot windows compatible #503

Thank you, @cjbarth, @shunkica, @pmahend1, @niklasl, for your contributions

• Set nodeName property in ProcessingInstruction #509 / #505

Thank you, @cjbarth, for your contributions

• Set nodeName property in ProcessingInstruction #509 / #505

Thank you, @cjbarth, for your contributions

• Throw DOMException when calling removeChild with invalid parameter #494 / #135

BREAKING CHANGE: Previously it was possible (but not documented) to call Node.removeChild with any node in the tree, and with certain exceptions, it would work. This is no longer the case: calling Node.removeChild with an argument that is not a direct child of the node that it is called from, will throw a NotFoundError DOMException, as it is described by the specs.

Thank you, @noseworthy, @davidmc24, for your contributions

• Add compareDocumentPosition method from level 3 spec. #488

• getAttribute and getAttributeNS should return null (#477) #46
• several issues in NamedNodeMap and Element (#482) #46
• properly parse closing where the last attribute has no value #485 / #486
• extend list of HTML entities #489

BREAKING CHANGE: Iteration over attributes now happens in the right order and non-existing attributes now return null instead of undefined. THe same is true for the namepsaceURI and prefix of Attr nodes. All of the changes are fixing misalignment with the DOM specs, so if you expected it to work as specified, nothing should break for you.

• update multiple devDependencies
• Configure jest (correctly) and wallaby #481 / #483

Thank you, @bulandent, @zorkow, for your contributions

• extend list of HTML entities #489

Thank you, @zorkow, for your contributions

• extend list of HTML entities #489

Thank you, @zorkow, for your contributions

• properly parse closing where the last attribute has no value #485 / #486

Thank you, @bulandent, for your contributions

• properly parse closing where the last attribute has no value #485 / #486

Thank you, @bulandent, for your contributions

• Properly check nodes before replacement #457 / #455 / #456

Thank you, @edemaine, @pedro-l9, for your contributions

• Properly check nodes before replacement #457 / #455 / #456

Thank you, @edemaine, @pedro-l9, for your contributions

• Properly check nodes before replacement #457 / #455 / #456

Thank you, @edemaine, @pedro-l9, for your contributions

• fix: Restore ES5 compatibility #452 / #453

Thank you, @fengxinming, for your contributions

• fix: Restore ES5 compatibility #452 / #453

Thank you, @fengxinming, for your contributions

• fix: Restore ES5 compatibility #452 / #453

Thank you, @fengxinming, for your contributions

• Security: Prevent inserting DOM nodes when they are not well-formed CVE-2022-39353 In case such a DOM would be created, the part that is not well-formed will be transformed into text nodes, in which xml specific characters like < and > are encoded accordingly. In the upcoming version 0.9.0 those text nodes will no longer be added and an error will be thrown instead. This change can break your code, if you relied on this behavior, e.g. multiple root elements in the past. We consider it more important to align with the specs that we want to be aligned with, considering the potential security issues that might derive from people not being aware of the difference in behavior. Related Spec: https://dom.spec.whatwg.org/#concept-node-ensure-pre-insertion-validity

• update multiple devDependencies
• Add eslint-plugin-node for lib #448 / #190
• style: Apply prettier to all code #447 / #29 / #130

Thank you, @XhmikosR, @awwright, @frumioj, @cjbarth, @markgollnick for your contributions

• Security: Prevent inserting DOM nodes when they are not well-formed CVE-2022-39353 In case such a DOM would be created, the part that is not well-formed will be transformed into text nodes, in which xml specific characters like < and > are encoded accordingly. In the upcoming version 0.9.0 those text nodes will no longer be added and an error will be thrown instead. This change can break your code, if you relied on this behavior, e.g. multiple root elements in the past. We consider it more important to align with the specs that we want to be aligned with, considering the potential security issues that might derive from people not being aware of the difference in behavior. Related Spec: https://dom.spec.whatwg.org/#concept-node-ensure-pre-insertion-validity

Thank you, @frumioj, @cjbarth, @markgollnick for your contributions

• Security: Prevent inserting DOM nodes when they are not well-formed CVE-2022-39353 In case such a DOM would be created, the part that is not well-formed will be transformed into text nodes, in which xml specific characters like < and > are encoded accordingly. In the upcoming version 0.9.0 those text nodes will no longer be added and an error will be thrown instead. This change can break your code, if you relied on this behavior, e.g. multiple root elements in the past. We consider it more important to align with the specs that we want to be aligned with, considering the potential security issues that might derive from people not being aware of the difference in behavior. Related Spec: https://dom.spec.whatwg.org/#concept-node-ensure-pre-insertion-validity

Thank you, @frumioj, @cjbarth, @markgollnick for your contributions

• fix: Stop adding tags after incomplete closing tag #445 / #416 BREAKING CHANGE: It no longer reports an error when parsing HTML containing incomplete closing tags, to align the behavior with the one in the browser. BREAKING CHANGE: If your code relied on not well-formed XML to be parsed and include subsequent tags, this will no longer work.
• fix: Avoid bidirectional characters in source code #440

• ci: Add CodeQL scan #444

Thank you, @ACN-kck, @mgerlach for your contributions

• Avoid iterating over prototype properties #441 / #437 / #436

Thank you, @jftanner, @Supraja9726 for your contributions

• Avoid iterating over prototype properties #437 / #436

Thank you, @Supraja9726 for your contributions

• Avoid iterating over prototype properties #437 / #436

Thank you, @Supraja9726 for your contributions

Only use HTML rules if mimeType matches #338, fixes #203

In the living specs for parsing XML and HTML, that this library is trying to implement, there is a distinction between the different types of documents being parsed: There are quite some rules that are different for parsing, constructing and serializing XML vs HTML documents.

So far xmldom was always "detecting" whether "the HTML rules should be applied" by looking at the current namespace. So from the first time an the HTML default namespace (http://www.w3.org/1999/xhtml) was found, every node was treated as being part of an HTML document. This misconception is the root cause for quite some reported bugs.

BREAKING CHANGE: HTML rules are no longer applied just because of the namespace, but require the mimeType argument passed to DOMParser.parseFromString(source, mimeType) to match 'text/html'. Doing so implies all rules for handling casing for tag and attribute names when parsing, creation of nodes and searching nodes.

BREAKING CHANGE: Correct the return type of DOMParser.parseFromString to Document | undefined. In case of parsing errors it was always possible that "the returned Document" has not been created. In case you are using Typescript you now need to handle those cases.

BREAKING CHANGE: The instance property DOMParser.options is no longer available, instead use the individual readonly property per option (assign, domHandler, errorHandler, normalizeLineEndings, locator, xmlns). Those also provides the default value if the option was not passed. The 'locator' option is now just a boolean (default remains true).

BREAKING CHANGE: The following methods no longer allow a (non spec compliant) boolean argument to toggle "HTML rules":

• XMLSerializer.serializeToString
• Node.toString
• Document.toString

The following interfaces have been implemented: DOMImplementation now implements all methods defined in the DOM spec, but not all of the behavior is implemented (see docstring):

• createDocument creates an "XML Document" (prototype: Document, property type is 'xml')
• createHTMLDocument creates an "HTML Document" (type/prototype: Document, property type is 'html').
  • when no argument is passed or the first argument is a string, the basic nodes for an HTML structure are created, as specified
  • when the first argument is false no child nodes are created

Document now has two new readonly properties as specified in the DOM spec:

• contentType which is the mime-type that was used to create the document
• type which is either the string literal 'xml' or 'html'

MIME_TYPE (/lib/conventions.js):

• hasDefaultHTMLNamespace test if the provided string is one of the miem types that implies the default HTML namespace: text/html or application/xhtml+xml

Thank you @weiwu-zhang for your contributions

• update multiple devDependencies

• fix(dom): Serialize > as specified (#395) #58

• docs: Add nodeType values to public interface description #396
• test: Add executable examples for node and typescript #317
• fix(dom): Serialize > as specified #395
• chore: Add minimal Object.assign ponyfill #379
• docs: Refine release documentation #378
• chore: update various dev dependencies

Thank you @niklasl, @cburatto, @SheetJSDev, @pyrsmk for your contributions

• Only use own properties in entityMap #374

• Add security policy #365
• changelog: Correct contributor name and link #366
• Describe release/publish steps #358, #376
• Add snyk package health badge #360

• Normalize all line endings according to XML specs 1.0 and 1.1
  BREAKING CHANGE: Certain combination of line break characters are normalized to a single \n before parsing takes place and will no longer be preserved.
  • #303 / #307
  • #49, #97, #324 / #314
• XMLSerializer: Preserve whitespace character references #284 / #310
  BREAKING CHANGE: If you relied on the not spec compliant preservation of literal \t, \n or \r in attribute values. To preserve those you will have to create XML that instead contains the correct numerical (or hexadecimal) equivalent (e.g. 	, 
, 
).
• Drop deprecated exports DOMImplementation and XMLSerializer from lib/dom-parser.js #53 / #309 BREAKING CHANGE: Use the one provided by the main package export.
• dom: Remove all links as part of removeChild #343 / #355

• ci: Restore latest tested node version to 16.x #325
• ci: Split test and lint steps into jobs #111 / #304
• Pinned and updated devDependencies

Thank you @marrus-sh, @victorandree, @mdierolf, @tsabbay, @fatihpense for your contributions

• Preserve default namespace when serializing #319 / #321 Thank you, @lupestro

• Restore ability to parse __prototype__ attributes #315 Thank you, @dsimpsonOMF

• Add doctype when parsing from string #277 / #301
• Correct typo in error message #294 Thank you, @rrthomas

• Improve exports & require statements, new main package entry #233

• Fix Stryker badge #298
• Fix link to help-wanted issues #299

• Execute stryker:dry-run on branches #302
• Fix stryker config #300
• Split test and lint scripts #297
• Switch to stryker dashboard owned by org #292

• Types: Add index.d.ts to packaged files #288 Thank you, @forty

• Types: Copy types from DefinitelyTyped #283 Thank you, @kachkaev

• package.json: remove author, maintainers, etc. #279

Due to #271 this version was published as

• unscoped xmldom package to github (git tags 0.7.0 and 0.7.0+unscoped)
• scoped @xmldom/xmldom package to npm (git tag 0.7.0+scoped) For more details look at #278

• Security: Misinterpretation of malicious XML input CVE-2021-32796
• Implement Document.getElementsByClassName as specified #213, thank you, @ChALkeR
• Inherit namespace prefix from parent when required #268
• Handle whitespace in closing tags #267
• Update DOMImplementation according to recent specs #210
  BREAKING CHANGE: Only if you "passed features to be marked as available as a constructor arguments" and expected it to "magically work".
• No longer serializes any namespaces with an empty URI #244
  (related to #168 released in 0.6.0)
  BREAKING CHANGE: Only if you rely on "unsetting" a namespace prefix by setting it to an empty string
• Set localName as part of Document.createElement #229, thank you, @rrthomas

• We are now additionally running tests against node v16
• Stryker tests on the master branch now run against node v14

• Describe relations with and between specs: #211, #247

Published to npm: 2021-04-17 16:41 UTC by @karfau as xmldom

• Stop serializing empty namespace values like xmlns:ds="" #168
  BREAKING CHANGE: If your code expected empty namespaces attributes to be serialized.
  Thank you, @pdecat and @FranckDepoortere
• Escape < to < when serializing attribute values #198 / #199

Published to npm: 2021-03-09 03:59 UTC by @brodybits as xmldom

• Avoid misinterpretation of malicious XML input - GHSA-h6q6-9hqw-rwfv (CVE-2021-21366)

  • Improve error reporting; throw on duplicate attribute
    BREAKING CHANGE: It is currently not clear how to consistently deal with duplicate attributes, so it's also safer for our users to fail when detecting them. It's possible to configure the DOMParser.errorHandler before parsing, to handle those errors differently.

    To accomplish this and also be able to verify it in tests I needed to

    • create a new Error type ParseError and export it
    • Throw ParseError from errorHandler.fatalError and prevent those from being caught in XMLReader.
    • export DOMHandler constructor as __DOMHandler

  • Preserve quotes in DOCTYPE declaration Since the only purpose of parsing the DOCTYPE is to be able to restore it when serializing, we decided that it would be best to leave the parsed publicId and systemId as is, including any quotes. BREAKING CHANGE: If somebody relies on the actual unquoted values of those ids, they will need to take care of either single or double quotes and the right escaping. (Without this change this would not have been possible because the SAX parser already dropped the information about the quotes that have been used in the source.)

    https://www.w3.org/TR/2006/REC-xml11-20060816/#dtd https://www.w3.org/TR/2006/REC-xml11-20060816/#IDAX1KS (External Entity Declaration)

• Fix breaking preprocessors' directives when parsing attributes #171

• fix(dom): Escape ]]> when serializing CharData #181

• Switch to (only) MIT license (drop problematic LGPL license option) #178

• Export DOMException; remove custom assertions; etc. #174

• Update MDN links in readme.md #188

Published to npm: 2020-10-27 00:44 UTC by @brodybits as xmldom

• BREAKING Restore   behavior from v0.1.27 #67
• BREAKING Typecheck source param before parsing #113
• Include documents in package files list #156
• Preserve doctype with sysid #144
• Remove ES6 syntax from getElementsByClassName #91
• Revert "Add lowercase of åäö in entityMap" due to duplicate entries #84
• fix: Convert all line separators to LF #66

• Update CHANGELOG.md through version 0.3.0 #63
• Update badges #78
• Add .editorconfig file #104
• Add note about import #79
• Modernize & improve the example in readme.md #81

• Add Stryker Mutator #70
• Add Stryker action to update dashboard #77
• Add Node GitHub action workflow #64
• add & enable eslint #106
• Use eslint-plugin-es5 to enforce ES5 syntax #107
• Recover vows tests, drop proof tests #59
• Add jest tessuite and first tests #114
• Add jest testsuite with xmltest cases #112
• Configure Renovate #108
• Test European HTML entities #86
• Updated devDependencies

• Remove files that are not of any use #131, #65, #33

Published to npm: 2020-03-04 16:32 UTC by @kethinov as xmldom

• BREAKING Node >=10.x is now required.
• BREAKING Remove component.json (deprecated package manager https://github.com/componentjs/guide)
• BREAKING Move existing sources into lib subdirectory.
• POSSIBLY BREAKING Introduce files entry in package.json and remove use of .npmignore.
• Add Document.getElementsByClassName.
• Add Node to the list of exports
• Add lowercase of åäö in entityMap.
• Move CHANGELOG to markdown file.
• Move LICENSE to markdown file.

Published to npm: 2019-12-20 00:40 UTC by @brodybits as xmldom

• Correct homepage, repository and bugs URLs in package.json.

Published to npm: 2019-12-20 00:19 UTC by @brodybits as xmldom

• Includes all BREAKING changes introduced in xmldom-alpha@v0.1.28 by the original authors.
• POSSIBLY BREAKING remove the Object.create check from the _extends method of dom.js that added a __proto__ property ().
• POSSIBLY BREAKING remove code that added a __proto__ property
• formatting/corrections in package.json

Published to npm: 2019-12-19 22:34 UTC by @brodybits as xmldom

Published to npm: 2019-12-19 22:30 UTC by @brodybits as xmldom

Published to npm: 2019-12-19 22:26 UTC by @brodybits as xmldom

The patch versions (0.1.29 - 0.1.31) that have been released on the v0.1.x branch, to reflect the changed maintainers, are branched off from 0.1.27 so they don't include the breaking changes introduced in xmldom-alpha@v0.1.28:

After the last commit to the original repository https://github.com/jindw/xmldom on the 9th of May 2017, the first commit to https://github.com/xmldom/xmldom is from the 19th of December 2019. The fork has been announced in the original repository on the 2nd of March 2020.

The versions listed below have been published to one or both of the following packages:

• https://www.npmjs.com/package/xmldom-alpha
• https://www.npmjs.com/package/xmldom

It is currently not planned to continue publishing the xmldom-alpha package.

The new maintainers did not invest time to understand changes that led to the last xmldom version 0.1.27 published by the original maintainer, but consider it the basis for their work. A timeline of all the changes that happened from that version until 0.3.0 is available in #62. Any related questions should be asked there.

Published to npm: 2017-05-08 02:51 UTC by @jindw as xmldom-alpha

• BREAKING includes regression regarding   (issue #57)
• Fix license field in package.json
• Conditional converting of HTML entities
• Fix dom.js serialization issue for missing document element (example that failed on toString() before this change)
• Add new module entities.js

Published to npm: 2016-11-28 03:56 UTC by @jindw as xmldom and xmldom-alpha

Tags 0.1.24, 0.1.25, 0.1.26, and 0.1.27 all point to the same git commit (b53aa82). These four versions were published within 24 hours in November 2016 with version bumps applied only to the working directory, not committed to git.

• Various bug fixes.

Published to npm: 2016-11-28 03:47 UTC by @jindw as xmldom

Tags 0.1.24, 0.1.25, 0.1.26, and 0.1.27 all point to the same git commit (b53aa82). These four versions were published within 24 hours in November 2016 with version bumps applied only to the working directory, not committed to git.

• Details unknown

Published to npm: 2016-11-28 03:35 UTC by @jindw as xmldom

Tags 0.1.24, 0.1.25, 0.1.26, and 0.1.27 all point to the same git commit (b53aa82). These four versions were published within 24 hours in November 2016 with version bumps applied only to the working directory, not committed to git.

• Details unknown

Published to npm: 2016-11-27 14:00 UTC by @jindw as xmldom and xmldom-alpha

Tags 0.1.24, 0.1.25, 0.1.26, and 0.1.27 all point to the same git commit (b53aa82). These four versions were published within 24 hours in November 2016 with version bumps applied only to the working directory, not committed to git.

• Added node filter.

Published to npm: 2016-05-20 04:24 UTC by @jindw as xmldom-alpha

• Add namespace support for nest node serialize.
• Various other bug fixes.

Published to npm: 2016-01-30 11:50 UTC by @jindw as xmldom

• Merge XMLNS serialization.
• Remove \r from source string.
• Print namespaces for child elements.
• Switch references to nodeType to use named constants.
• Add nodelist toString support.

Published to npm: 2016-01-13 11:41 UTC by @jindw as xmldom

• Fix serialize bug.

Published to npm: 2016-01-10 08:23 UTC by @jindw as xmldom

• Optimize invalid XML support.
• Add toString sorter for attributes output.
• Add html self closed node button.
• Add * NS support for getElementsByTagNameNS.
• Convert attribute's value to string in setAttributeNS.
• Add support for HTML entities for HTML docs only.
• Fix TypeError when Document is created with DocumentType.

Published to npm: 2014-01-28 15:15 UTC by @jindw as xmldom

• Fix infinite loop on unclosed comment (jindw/xmldom#68)
• Add error report for unclosed tag.
• Various other fixes.

Published to npm: 2014-01-17 06:59 UTC by @bigeasy as xmldom

• Add default ns support.
• parseFromString now renders entirely plain text documents as textNode.
• Enable option to ignore white space on parsing.

Published to npm: 2013-12-16 03:07 UTC by @jindw as xmldom

No version bump commit for 0.1.17 was found in git history. The tag 0.1.17 points to the commit immediately preceding the 0.1.18 version bump (87f63e6, parent of 9ddac14), which is the last committed state before the next version.

Published to npm: 2013-05-04 15:00 UTC by @bigeasy as xmldom

• Correctly handle multibyte Unicode greater than two byts. #57. #56.
• Initial unit testing and test coverage. #53. #46. #19.
• Create Bower component.json #52.

Published to npm: 2013-04-03 02:41 UTC by @bigeasy as xmldom

Published to npm: 2013-03-31 15:31 UTC by @bigeasy as xmldom

Published to npm: 2012-10-02 11:35 UTC by @jindw as xmldom

Published to npm: 2012-09-03 15:02 UTC as xmldom

No version bump commit for 0.1.12 was found in git history. The tag 0.1.12 points to the commit immediately preceding the 0.1.13 version bump (47fa9b8, parent of eb17b3a), which is the last committed state before the next version.

Published to npm: 2012-06-18 10:45 UTC by @jindw as xmldom

Published to npm: 2012-06-14 02:54 UTC by @jindw as xmldom

Published to npm: 2012-06-08 06:18 UTC by @jindw as xmldom

Published to npm: 2012-05-29 13:30 UTC by @jindw as xmldom

• Add: some test case from node-o3-xml(excludes xpath support)
• Fix: remove existed attribute before setting (bug introduced in v0.1.5)
• Fix: index direct access for childNodes and any NodeList collection(not w3c standard)
• Fix: remove last child bug

Published to npm: 2012-05-29 03:05 UTC by @jindw as xmldom

Published to npm: 2012-05-28 12:49 UTC by @jindw as xmldom

Published to npm: 2012-05-25 17:43 UTC by @jindw as xmldom

Published to npm: 2012-05-22 16:41 UTC by @jindw as xmldom

Published to npm: 2012-05-22 16:39 UTC by @jindw as xmldom

Published to npm: 2012-02-03 10:49 UTC by @jindw as xmldom

Published to npm: 2012-01-10 07:18 UTC by @jindw as xmldom

Published to npm: 2012-01-06 09:49 UTC by @jindw as xmldom