xml2js

This project publishes no release notes. Between 0.6.1 and 0.6.2 there were 2 commits, 2 of them substantive:

• Fix read-only constraint via mistyped key name
• New release, 0.6.2

This project publishes no release notes. Between 0.6.0 and 0.6.1 there were 3 commits, 2 of them substantive:

• Update package lock
• Replace filtering of names with defineProperty

This project publishes no release notes. Between 0.5.0 and 0.6.0 there were 15 commits, 12 of them substantive:

• Bump dependency versions to fix security issues
• Add upper bound for coffeescript (for now)
• chore: revert previous CVE fix
• fix: explicitly ignore vulnerable properties
• refactor: extract function for key check
• fix: revert incorrectly adapted code
• fix: include missed key check
• Undo API changes from #603
• Compile changed coffeescript code
• Fix zap to be the original dependency
• Remove old unused files
• Release new version

This project publishes no release notes. Between 0.4.22 and 0.5.0 there were 21 commits, 13 of them substantive:

• Call function for emptyTag if specified
• cr fixes (will be squashed after another cr)
• readme updated with default empty tag as function
• package: Remove temporary util.promisify dep
• src: Inline util.promisify
• regenerate lib/parser.js
• fix issue554
• append example to README for issue #552
• Update README.md
• Add documentation for explicitCharkey option
• use Object.create(null) to create all parsed objects (prevent prototype replacement)
• Update README.md
• Update package.json with latest PR

This project publishes no release notes. Between 0.4.21 and 0.4.22 there were 6 commits, 4 of them substantive:

• Attempt to restore Node 4 compatibility
• Use xmlbuilder that works with Node 4
• Add compatibility shim for Node < 8
• Use promise shim instead of actual Node function

This project publishes no release notes. Between 0.4.20 and 0.4.21 there were 3 commits, 2 of them substantive:

• Update xmlbuilder dependency to 13.x
• New release 0.4.21

This project publishes no release notes. Between 0.4.19 and 0.4.20 there were 30 commits, 18 of them substantive:

• Builder with attributes example
• Remove unused require() from example
• Drop support for EOL versions
• Update dev dependency (closes #457)
• Update outdated dependency
• Going to remove package-lock for now
• README.md: how to add xmlns attributes
• README.md: builder options attrkey and charkey
• parser.test.coffee: regression tests for #356
• parser test: "valueProcessor" -> "valueProcessors"
• Fix nonsensical phrase in documentation.
• Update README.md
• Bump nodejs versions to ones that are still maintained
• Create a promise-specific version of parseString
• Minimal version is Node 8
• Add lockfile
• updated events
• New release, 0.4.20

This project publishes no release notes. Between 0.4.18 and 0.4.19 there were 1 commits, 1 of them substantive:

• Revert "Empty strings now returns error cause its not valid XML"

This project publishes no release notes. Between 0.4.17 and 0.4.18 there were 28 commits, 21 of them substantive:

• Verify entry type in requiresCDATA function
• Compile coffee into javascript
• Added test to check cData on array values
• Update xmlbuilder-js dependency
• move defaults to own file
• move builder to own file
• move parser to own file
• commit built javascript files (for tests)
• tests for node / attribute name non-agnostic processor functions
• this was a bit of a misnomer; it gets names and values. I'm about to make it worse of a misnomer if I don't change it now
• pass the attribute/node names into the parser function
• update readme for attribute/node name aware processors
• Wrap try/catch with function to allow V8 to optimise onclosetag
• Credit Lovell
• Empty strings now returns error cause its not valid XML
• Credit d3adc0d3
• Fix issue #119.
• Add test for the fix of issue #119
• Follow XML 1.1 spec for valid chars instead of 1.0
• Do not upgrade to new major versions unasked

…and 1 more.