Node.js on TIBCO Cloud? Integration
- Getting started
- My first Node.js app
- Deploy your first Node.js app
- Test your Node.js app
- Manage your Node.js apps
- Adding dependencies to your app
- Run your app locally
- Understanding the generated code
- Advanced topics
- Best practices
Never modify the manifest.json
We?ve said it a few times before, but never modify the
manifest.json file unless you?re told to do so by the TIBCO Support team. Making changes might cause your app to fail during the deployment or build phase on TIBCO Cloud Integration.
Bottom-up or Top-down
Start every project with the choice if you want to start with the generation of code from an API specification or by generating the boilerplate code through Visual Studio Code. After that, you can make updates to the
package.json file to make sure it suits your needs.
A lot of programming languages would ?dictate? that you should have your class names and filenames start with an uppercase letter (like
SomeRandomGenerator should match with
SomeRandomGenerator.js). Node.js is a great cross-platform tool that makes it very easy to share code between developers on different platforms. For Windows and macOS
SomeRandomGenerator.js is equivalent to
somerandomgenerator.js, but Linux treats them as two very separate files. Sticking to lowercase filenames makes it so much easier to share code with your Linux friends.
Use .env files
By default Node.js apps have access to the
process.env context and with
.env files (for example by using Dotenv) you can easily extend that context to inject your variables as well. It also makes your app a lot more Twelve-Factor App compliant.