A Node v18 monorepo with one package that requires Node v14

[grossbart]

We are trying to consolidate several packages into a Lerna monorepo. One of these is a Meteor application that requires Node 14, while the others require Node 18. Meteor additionally requires a node_modules directory within the project, which is why we settled on Yarn because it allows us to disable hoisting to the root. The file system layout looks something like this:

• apps
  • meteor (Node 14)
  • app2 (Node 18)
  • app3 (Node 18)
• packages
  • lib1
  • lib2

We are now pondering what the best way to approach this would be, because it occurred to us that we can't use Yarn workspaces, as Yarn would install Node modules that have been built against Node 18, which could break the Meteor application. Meteor bundles Node 14, so we do have access to Node 14 within the Meteor app.

Should we treat the Meteor app as completely separate and handle the others with Yarn? Or leave Yarn completely out of the picture and lean on the Nx part of Lerna more? Or are there other techniques in the Lerna/Nx ecosystem we could leverage?