run tests on built test files, test on all supported nodes

[ljharb]

This is effectively the same PR as A11yance/axobject-query#356.

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

[wojtekmaj]

This is a Trojan horse pull request. The PR title clearly states that the purpose is to "test built code". In reality, the PR:

• Sneaks in support for Node 0.4 (I was only able to track down an intention to support Node 6: Convert several maps to use objects #162 (comment))
• Replaces fundamental GitHub Actions with ones you control
• Changes the testing framework to one you control
• Adds a bunch of new dev dependencies that you control

If you're making changes like this, at least be honest about it. There's nothing to be ashamed of, or is there?

[AaronDewes]

To be fair, the actions are pinned to a commit. There isn't a risk of malicious code being added there. The deps are more dsngerous though, but there is always some trust in maintainers involved.

[yamiteru]

LGTM

[ljharb]

These are all dev deps, and as such, it doesn’t make sense for anyone but maintainers to have an opinion on them.

@wojtekmaj there’s nothing dishonest here, and accusing me of doing something “sneaky” is an absurd accusation.

[marcysutton]

Hey @ljharb, thanks for the PR. This looks good! There are still no dependencies and the changes are really for testing against a variety of Node engines. It follows the approach of axobject-query which seems fine to me.

[marcysutton]

@ljharb do you need deep-equal-json here or can you make a similar change to A11yance/axobject-query#357? (I see that it's only a devDependency)

[ljharb]

aria-query is definitely going to end up with zero deps, but since the replacement function isn't exposed (intentionally), i can either use the dev dep, or i can duplicate the code, and the dev dep felt simpler.