An error is emitted when you try to run 'taq compile' from a repo like 'hello-tacos' without having run npm install first.
This problem is apparent when you checkout a repo that has a .taq/state.json file.
Perhaps as a solution at the very least, when we taq init a project, we also add ".taq/state.json" to the .gitignore file if one exists, and if not, generate one.
In additional, because state.json is also aware of whether a plugin is distributed using NPM, we should be able to determine whether npm install has been run by executing npm ls before attempting to proxy a task.
An error is emitted when you try to run 'taq compile' from a repo like 'hello-tacos' without having run
npm install
first.This problem is apparent when you checkout a repo that has a .taq/state.json file.
Perhaps as a solution at the very least, when we
taq init
a project, we also add ".taq/state.json" to the .gitignore file if one exists, and if not, generate one.In additional, because state.json is also aware of whether a plugin is distributed using NPM, we should be able to determine whether npm install has been run by executing
npm ls
before attempting to proxy a task.