Conversation
@sanjeevghimire can you update the commit message to describe how you fixed the bug? And also include the text |
* Since tsc is used as dev dependency, do the build locally as npm install wouldn't install dev dependency in IBM cloud * copy the package.json to the dist directory * ibm cloud cf push crm-server
…cial-crm into deploy-to-cloud-bug-fix
@stevemart commit message amended. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. But I don't see the commit message.
OK, I think the message is in one of the commits. |
This PR fixes/closes #55 . The issue is to do with dev dependencies not installed when pushing to cloudfoundry using The project use Typescript. Node.js doesn't understand typescript directly, so it has to be compiled into JavaScript first using The solution was to build the project before you push to IBM cloud. The steps are:
|
This PR closes: #55 . The issue is to do with dev dependencies not installed when pushing to cloudfoundry using ibmcloud cli.
The project use Typescript. Node.js doesn't understand typescript directly, so it has to be compiled into JavaScript first using tsc command and then run the built project. Since typescript is added as a devDependency in package.json, relying on Cloud Foundry to install the dependency didn't work.
The solution was to build the project before you push to IBM cloud. The steps are: