feat: migrate 4.x yarn 1 to yarn 2

[juanpicado]

master branch uses yarn 1, time to move to yarn 2 to benefit of new features.

note: 5.x uses pnpm and no plan to change it.

No big changes since I've not enabled pnp https://yarnpkg.com/configuration/yarnrc#nodeLinker

• update Dockerfile
• strict dependencies
• update release scripts
• update CI scripts
• remove Node 8 from CI (yarn 2 does work >=v10). Note: we still support v8.

nodeLinker: node-modules

[soulchild]

This just broke our automatic Verdaccio build to include custom plugins. Our Dockerfile looks similar to this:

FROM verdaccio/verdaccio:4

RUN yarn add --no-lockfile --production=true verdaccio-ldap verdaccio-aws-s3-storage

yarn2 removed the options --no-lockfile and --production. Running yarn add without them unnecessarily installs half of npm. I suppose this is because the final image of the multi-stage build of Verdaccio correctly doesn't include the devDependencies (used only in the builder stage) which are now installed again when we run yarn add.

I know next to nothing about yarn, so can you suggest a way around this?

[juanpicado]

Could you use previous tag in the meantime I research ?

[soulchild]

Yes, I already did that. 😄 Thanks for looking into it!

[juanpicado]

Could you create a ticket otherwise I will forget, please 🙏 add some examples.

[soulchild]

Thanks, @juanpicado! #2016