Skip to content

Consider replacing deprecated xml-js #3471

Description

@amitguptagwl

Hi team,

I noticed that this package currently relies on xml-js as a dependency. Unfortunately, xml-js is no longer being actively maintained—it hasn't seen an update in over 7 years, and currently has 80+ unattended issues and 30+ open PRs.

I completely understand that replacing a core dependency takes time and resources. However, if you are looking to improve security, performance, and memory efficiency, I highly recommend looking into fast-xml-parser or its modern, modular successor @nodable/flexible-xml-parser.

Why the migration would be straightforward:
Both libraries natively support both compact and non-compact (ordered/sequential) responses, meaning you can closely replicate the exact data structures xml-js currently outputs for your application without having to rewrite heavy downstream logic. Additionally, @nodable/flexible-xml-parser supports custom output build that can match the response your app needs so migration can go smooth.

Full disclosure: I am the author of both libraries, but I’m suggesting this purely to help modernize the dependency stack here.

Thanks for your time and for maintaining this project!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions