v3.2.1 has a breaking change

[ljharb]

Specifically, it uses the ?? operator, which doesn't work in node 12 (and breaks eslint-plugin-import tests).

It was added here: #81 (comment)

Please remove use of this operator and publish a v3.2.2?

(I'm happy to make a PR if that's needed)

[ljharb]

ping Martin Aeschlimann (@aeschli)

[aeschli]

We want to move forward and not commit to be backward compatible. We currently compile against es2020 and for that you need Node 14.
Node 12 has reached end of line status almost 2 years ago.

Is there maybe a packager that you can useto back-compile?

[ljharb]

Martin Aeschlimann (@aeschli) that’s now how semver works, and no, it’s not safe to transpile code one didn’t author.

The proper way to move forward is a breaking change whenever you drop support for a node version. This position means this package is not semver-compliant.

[aeschli]

We actually switched to es2020 already for 3.2.0. This is documented in the [CHANGELOG}( https://github.com/microsoft/node-jsonc-parser/blob/main/CHANGELOG.md)

Maybe what should have happend is to add an engine property. I will add that ASAP.

[ljharb]

ok, that’s still a breaking change in v3.2.0. You have to bump the major when you drop any platform/engine.