Introducing the all-new TIBCO Community site!

For current users, please click "Sign In" to reset your password and access the enhanced features. If you're a first-time visitor, we extend a warm welcome—click "Sign Up" to become a part of the TIBCO Community!

If you're seeking alternative community sites, explore ibi, Jaspersoft, and Spotfire.

Jump to content
  • Best practices for Node.js apps on TIBCO Cloud? Integration


    Deepesh Tiwari

    Node.js on TIBCO Cloud? Integration

    1. Getting started
    2. Prerequisites
    3. My first Node.js app
    4. Deploy your first Node.js app
    5. Test your Node.js app
    6. Manage your Node.js apps
    7. Adding dependencies to your app
    8. Run your app locally
    9. Understanding the generated code
    10. Advanced topics
    11. Best practices
    12. Resources

    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.

    Lowercase filenames

    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.


    User Feedback

    Recommended Comments

    There are no comments to display.



    Create an account or sign in to comment

    You need to be a member in order to leave a comment

    Create an account

    Sign up for a new account in our community. It's easy!

    Register a new account

    Sign in

    Already have an account? Sign in here.

    Sign In Now

×
×
  • Create New...