Skip to content

Update dependency xml-js to v1#122

Closed
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/xml-js-1.x
Closed

Update dependency xml-js to v1#122
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/xml-js-1.x

Conversation

@renovate

@renovate renovate Bot commented Jul 13, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
xml-js 0.9.71.6.11 age confidence

Release Notes

nashwaan/xml-js (xml-js)

v1.6.11

Compare Source

v1.6.10

Compare Source

v1.6.9

Compare Source

v1.6.8

Compare Source

v1.6.7

Compare Source

v1.6.6

Compare Source

v1.6.5

Compare Source

v1.6.4: Faster internal processing for js2xml and json2xml

Compare Source

Optimization done in js2xml routine that improves its performance for converting js object or json text to xml text.
Thanks for the efforts #​63 by @​AirCrisp

v1.6.3

Compare Source

v1.6.2

Compare Source

v1.6.1

Compare Source

v1.6.0: Additional Processing via Custom Functions

Compare Source

This release adds a major feature that allows to pass in custom functions for additional processing.

Example to make all parsed element names in upper case:

var js = convert.xml2js(xml, {compact: false, elementNameFn: function(name) {
    return name.toUpperCase();
}});

v1.5.2

Compare Source

v1.5.1: Support attributes indentation and few minor improvements

Compare Source

This release supports a new option indentAttributes to indent attributes in the xml. See below example from this thread:

<parent
  bar="1"
  baz="hello"
>
  <child
    attr1="a"
    attr2="b"
  />
</parent>

Also, support for converting js object of {a: 'hi'} rather than {a: {_text: 'hi'}} to <a>hi</a>.
I previously didn't want to support this for the reasons outlined here.
I am allowing this behavior in this library as it can be safe to handle this scenario when transforming js2xml only.
xml2js conversion from <a>hi</a> to {a: 'hi'} rather than {a: {_text: 'hi'}} is still not supported as this could be dangerous for the reasons explained here.

v1.5.0

Compare Source

v1.4.2

Compare Source

v1.4.1

Compare Source

v1.4.0: Better handling of basic xml entity codes

Compare Source

This release addresses some issues on escaping entity codes (e.g &amp;) in xml document.

The new implementation can cause a slight breaking change:

  • Converting from xml to js will decode the 5 entity codes &amp; &lt; &gt; &quot; &#&#8203;39; into & < > " '. For example, &amp; WILL be changed to & character (instead of keeping it &amp;). Also, {sanitize: true} option is deprecated.
  • Converting from js to xml will cause 3 characters & < > (instead of 5 characters) if found in node text to be transformed into &amp; &lt; &gt;. And will cause 1 character " (instead of 5 characters) if found in node attribute to be transformed into &quot;.

For more discussion, see this issue.

v1.3.4

Compare Source

v1.3.3

Compare Source

v1.3.2: Support parsing of Processing Instructions

Compare Source

Parsing of processing instructions such as <?go there?> and <?go to="there"?> are now supported. Note that for the second case, the parser by default will not generate attributes unless flag {instructionHasAttributes: true} is set. See discussion for more details.

v1.3.1

Compare Source

v1.3.0

Compare Source

v1.2.2

Compare Source

v1.2.1

Compare Source

v1.2.0: AlwaysArray and Multiple Comments & CData in Compact Mode

Compare Source

Setting {compact: true, alwaysArray: true} when converting from xml to js/json will always put sub-element (even if it is only one) into an array of objects. This can simplify the client code a little so that it can always expect the content of an element is an array rather than checking everytime whether it is an array or object.

Also, multiple comments and multiple CDatas are now supported in compact mode.

v1.1.0: Support for DOCTYPE and no indentation for CData

Compare Source

  • Parsing of DOCTYPE is now supported but in a simple way: its content will be a string and will not be parsed further (see discussion).
  • XML output of CData will not be proceeded by indentation by default (see discussion). However, to get old behavior where CData is indented in the output, use {indentCdata: true}.

v1.0.2: First Stable Release

Compare Source

First major and stable release.

v1.0.1

Compare Source

v1.0.0

Compare Source


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot requested review from a team and Copilot July 13, 2026 23:24

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot can't review bot-authored pull requests automatically. A user with Copilot access can request a review manually.

@fdevans fdevans closed this Jul 13, 2026
@renovate

renovate Bot commented Jul 13, 2026

Copy link
Copy Markdown
Contributor Author

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 1.x releases. But if you manually upgrade to 1.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

@renovate renovate Bot deleted the renovate/xml-js-1.x branch July 13, 2026 23:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants