We currently have failures on all our scenario runs because of an npm install problem. This happens because we need to clone and npm install the entire synapse repo to get scripts to run from there. But, we should be treating synapse as a dependency and running scripts locally.
So the task here is to extract what we need from Synapse (just example-e2e I think?) locally, treat synapse as a direct dependency, npm instal it from there. Any failures from a dependency npm install are important to pay attention to because they point to downstream problems impacting actual Synapse users, unlike the broader range of failure modes we get from doing an npm install and getting all of the subpackages installed and all of their devDependencies.
We currently have failures on all our scenario runs because of an npm install problem. This happens because we need to clone and
npm installthe entire synapse repo to get scripts to run from there. But, we should be treating synapse as a dependency and running scripts locally.So the task here is to extract what we need from Synapse (just example-e2e I think?) locally, treat synapse as a direct dependency,
npm instalit from there. Any failures from a dependencynpm installare important to pay attention to because they point to downstream problems impacting actual Synapse users, unlike the broader range of failure modes we get from doing annpm installand getting all of the subpackages installed and all of their devDependencies.