Adds @foal/cli to package.json templates #1109
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue
When running the npm run build command locally, the foal binary is found because we have previously installed it globally using npm install -g @foal/cli . So the command works.
But when deploying to a PaaS provider (such a Heroku), the command fails because the CLI has not been installed globally. Only dependencies specified in package.json are installed.
Solution and steps
Added the @foal/cli of version 2.9.0 to the package.json templates in the folders:
To test this, set up the environment as stated in the Contributing Guidelines. You don't have to setup the Database, so skip the docker-start command.
node index.js createapp -G -I testApp
cd ./testApp
Checklist
No need to update the docs.
Test ran successfully
Generation checked using the index.js file inside the "packages\cli\lib" folder.