Multiple fixes

[nonara]

Issues Corrected

• "SyntaxError: The requested module 'node-html-parser' does not provide an export named 'parse'" #160
• [Feature] Add / improve ESM support #139
• xml support? #124
• Something strange with premises tag and querySelector() / querySelectorAll() #156
• Update querySelector type definition to return null #157
• Prototype pollution #129
• Ensure ESM support. Fixes #149 #150
• Bug in node-html-parser. #164

Extras

• Added CI workflow to ensure pull requests and pushes get tested
• Added workflow to automate publishing to NPM and creating GH release when version tag is pushed (ie. v4.0.0)

⚠️ NOTICE ⚠️

This can be technically considered a breaking change for some, as affording proper ESM support requires adding an exports field to package.json.

This is the proper way to handle such support, but it should be released as a new major version, regardless.

For more detail on the approach used and why it's optimal, see:

• https://redfin.engineering/node-modules-at-war-why-commonjs-and-es-modules-cant-get-along-9617135eeca1

Note: If a user needs a certain export that is not exported in the main index, he or she can file an issue requesting it, and we try to accommodate

[nonara]

Hi @taoqf!

Hope you're doing well. I fixed most of the open issues. I will be addressing the outstanding soon.

I will merge the changes, myself, but I need your help with one thing.

I'd like to enable automatic publishing when a version tag is pushed

This will allow me to publish releases when I fix issues.

I've added github actions for testing & publishing. It also automatically creates a release, as long as we follow Conventional Commits style commits.

With this setup, all we need to do when we have a new version is to run standard-version and it will:

1. Create an updated changelog,
2. Increment the version number properly (according to conventional commit title)
3. Create a tag commit

After this, when we push that commit, github actions will create a release and publish the package to NPM.

I just need you to add an NPM token to the repository, which is very easy to setup!

What I need from you is for you to:

1. Create a publish NPM token
   • Follow these instructions & choose Automation for the type:
     https://docs.npmjs.com/creating-and-viewing-access-tokens
2. Add the token to this repositories secrets
   • Add the token as a secret named NPM_TOKEN
     https://docs.github.com/en/actions/security-guides/encrypted-secrets#creating-encrypted-secrets-for-a-repository

When you've got that added, please let me know, and I will publish all of these fixes.

[taoqf]

@nonara Done. Thanks so much for all your work.

[nonara]

No problem! Happy to help!

[milahu]

why remove the npm run build prepare script?
this is required for "install from git" (#125), cd test && yarn install is not

fixed in #253