Hello lovely humans,

xmlserializer just published its new version 0.6.0.

This version is not covered by your current version range.

Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.

I recommend you look into these changes and try to get onto the latest version of xmlserializer.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.

Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?

There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.

Good luck with your project ✨

You rock!

🌴

The new version differs by 15 commits .

• c4e23da Bump version
• f2b8160 Fix license entry in package.json
• a086400 Fix example
• 10803bf Move test file into test dir
• b7eb06b Move main distributable into main dir, breaks integration for people sourcing this file directly
• 63e7ffd Bump version
• 4cd7e44 Sync back with changes uptream
• 5b50d9f Upgrade to Jasmine2 from npm, fix waitFor statement
• 2eb4a2f Upgrade to Jasmine2 from npm
• 288092a Bump dev dependencies
• e730e26 Provide missing phantomjs as dependency
• 540238d Byb bye jake
• 6be2c82 Update travis config, newer node, reset api key just to be on the safe side
• 2d77a18 One UMD header for all environments. Simplify build, make npm module requirable via script tag
• da3683b Add license file, #9

See the full diff.

This pull request was created by greenkeeper.io.

_{Tired of seeing this sponsor message? ⚡ greenkeeper upgrade}