Unit tests in venia can run against stale peregrine code

[DrewML]

This issue is for the following packages:

[X] venia-concept
[ ] pwa-buildpack
[ ] peregrine
[ ] pwa-module

This issue is a:

[X] Bug
[ ] Feature suggestion
[ ] Other (Please Specify)

Environment

Question	Answer
Magento version
Operating System + version
node.js version (node -v)
npm version (npm -v)

Description

Steps to Replicate

1. Run npm install in the root of the repository to bootstrap
2. Run rm -rf packages/peregrine/dist in the root of the repository
3. Run npm test in the root of the repository

Tests in venia-concept should fail with Cannot find module '@magento/peregrine' from 'foobar.js'. This means tests in venia-concept that consume @magento/peregrine are pulling in the last built version of the lib locally, which may not be up-to-date with the src files in @magento/peregrine.

Expected result:

Cross-package unit/integration tests always consume from src, not dist. The dist artifact should only ever be used for publishing to npm, and nothing else.

Cross-package unit/integration tests always consume from src, not dist.

Possible solutions:

Use Jest's configuration to re-write paths for libs in this monorepo, to ensure that:

1. Jest handles transpiling the src of the libs in this repo with Babel
2. Jest pulls files from src, rather than the dist it finds in the package's main entry in package.json.