Migrate from npm to yarn (3.2.2) using the node-modules linker. (I know I kept saying "yarn 2", but 3.2.2 is the most recent version, and I think there were more significant changes between 1.x to 2.x than from 2.x to 3.x, at least for the purposes of this work.)
This changes the dev build (Dockerfile.dev) and production build (Dockerfile) to use yarn. In addition, the way that the yarn version and configuration is managed, this also guarantees that running yarn on a local workstation will use the same version as the docker image builds. This was definitely not true when using npm, making it more difficult to assess local changes to dependencies; I've had to run npm install (and npm-why or npm explain) in a docker container just to make sure I was seeing consistent results.
I also made a couple of additions to the Terra quickstart doc.
I tried several routes to get to a yarn.lock. With any version of yarn, yarn install will resolve dependencies described in package.json. In addition, yarn 1.x has a yarn import command (missing from yarn 3.x) that also considers package-lock.json in an effort to create a more accurate reproduction of that. I think they removed yarn import because they've improved the dependency resolution logic enough to make import redundant. However, I didn't find that to be 100% true. The best path I found was to run yarn import with yarn 1.x to make use of package-lock.json, then yarn install with yarn 3.x to bring the yarn.lock up-to-date with the latest yarn version.
I did not attempt to adapt PnP. That can be something to consider for the future.
Migrate from npm to yarn (3.2.2) using the node-modules linker. (I know I kept saying "yarn 2", but 3.2.2 is the most recent version, and I think there were more significant changes between 1.x to 2.x than from 2.x to 3.x, at least for the purposes of this work.)
This changes the dev build (
Dockerfile.dev) and production build (Dockerfile) to use yarn. In addition, the way that the yarn version and configuration is managed, this also guarantees that runningyarnon a local workstation will use the same version as the docker image builds. This was definitely not true when using npm, making it more difficult to assess local changes to dependencies; I've had to runnpm install(andnpm-whyornpm explain) in a docker container just to make sure I was seeing consistent results.I also made a couple of additions to the Terra quickstart doc.
I tried several routes to get to a
yarn.lock. With any version of yarn,yarn installwill resolve dependencies described inpackage.json. In addition, yarn 1.x has ayarn importcommand (missing from yarn 3.x) that also considerspackage-lock.jsonin an effort to create a more accurate reproduction of that. I think they removedyarn importbecause they've improved the dependency resolution logic enough to makeimportredundant. However, I didn't find that to be 100% true. The best path I found was to runyarn importwith yarn 1.x to make use ofpackage-lock.json, thenyarn installwith yarn 3.x to bring theyarn.lockup-to-date with the latest yarn version.I did not attempt to adapt PnP. That can be something to consider for the future.