fix: removed node v12 from the pipe

[prisis]

Because vitest is not supporting this version.

[Shinigami92]

We should do this end of march

https://nodejs.org/en/about/releases/

[prisis]

Please check https://github.com/faker-js/faker/runs/4947011110?check_suite_focus=true as example the pipe never runs and vitest is returning 0 as error code

[ST-DDT]

The test pipeline does not work with node 12 and AFAICT the releases aren't build with node 12 either, so there is no point in keeping it.
If you wish to ensure that it can be build with node 12, then we should at least explicit turn of the test runs.

But I don't have a strong opinion on when to remove this.

Is there anything compatibility wise we have to consider when removing it?
(Aka does our build process ensure node 12 compatibility regardless of our build setup?)

[Shinigami92]

@damienwebdev @JessicaSachs Please point out in next release notes that we officially drop node 12 support

[Shinigami92]

This line needs to be updated to v14

faker/package.json

Line 99 in 3242dfc

"node": ">=12.0.0",

[ST-DDT]

Couldn't we just drop official support for node 12 but give the users at least the chance to use it?
AFAICT we don't use any node 14+ features.

[Shinigami92]

https://docs.npmjs.com/cli/v8/configuring-npm/package-json#engines
As far as we don't set engine-strict, only a warning will show up