chore: use Node.js 16.x for building package and tests

[ctavan]

Previously we were requiring Node 12.x to get somewhat reproducible npm builds. This now upgrades the requirement to the latests LTS version 16.x

[LinusU]

I think that these two tests should run on >= 12? That is, all that supports ESM

[ctavan]

Early versions of 12.x didn't support ESM IIRC… That's why historically we didn't test there.

But I guess nowadays it's safe to run these tests on Node 12+, so thanks for the catch!

[LinusU]

npm ERR! code EINVALIDPACKAGENAME
npm ERR! Invalid package name ".local": name cannot start with a period

Ran into this locally when using npm 7 as well, I didn't have time to look into why there was a .local folder though. It's a little annoying as it makes all files show up twice when searching in VS Code 😅

[ctavan]

npm ERR! code EINVALIDPACKAGENAME
npm ERR! Invalid package name ".local": name cannot start with a period

Ran into this locally when using npm 7 as well, I didn't have time to look into why there was a .local folder though. It's a little annoying as it makes all files show up twice when searching in VS Code 😅

The .local symlink is a workaround to make local file references work in the examples folder (so you can actually test local changes)… The error you mentioned should now be fixed. Not sure about vscode. Could it be added to some ignore file for the editor?

[ctavan]

I had to upgrade @wdio v6 -> v7 in order to get it to run with Node 16 and unfortunately that was a bit of a rabbit hole but it should be good again :).

I couldn't resist upgrading all other build deps as well.

[LinusU]

Should this be committed?

[ctavan]

Oops, of course not…. I was Troubleshooting eslint/prettier… will remove

[LinusU]

Nice! 👍

[LinusU]

Neat! 🙌