Getting Started with Node & Kinvey

Getting Started with Node & Kinvey

Posted on April 18, 2019 0 Comments
Getting Started with Node Kinvey_870x450

This is a quick post to help you get up and running with a new Node project connected to a Kinvey backend. Let's just jump right in!

Creating a Node Project

I make a lot of Node projects, some even see the light of day πŸ˜›, so I have a script to spin one up. I got the idea from this tweet from Tierney Cyren and learned even more from this post by Phil Nash.

Tierney Cyren Tweet

As the tweet says, to get a Node project started you can just type this in your terminal :

npx license mit > LICENSE
npx gitignore node
npx covgen <your email address>
npm init -y

What all is happening here? We're using npx to use an npm module whether we have it installed or not. First, license to generate the MIT license, gitignore to fetch a Node.js .gitignore file, and covgen to generate the Contributor Covenant inside your project directory using your email as the contact info. Finally, we run npm init -y to spin up a package.json file for the project. The -y or --yes flag uses the defualt values or the configs you can set using npm.set.

npm set ""
npm set "example_user"
npm set init.license "MIT"

That's it! I have a shortcut in my ~/.bashrc file so that I can just type node-project in an empty directory and it spins all this up plus initializes git in the directory and makes the first commit. Nash explains it in-detail in his post I listed above. Here's what my function looks like:

function node-project {
  git init
  npx license mit>LICENSE
  npx gitignore node
  npx covgen "$(npm get"
  npm init -y
  git add .
  git commit -m 'initial commit'

πŸ™ you can check out this project's repo to see what we have so far.

Connecting to Kinvey

Now that we have our base project we get to connect it to our Kinvey backend. First things first, we'll want to install the Kinvey SDK, which is open source πŸ˜ƒ.

npm i kinvey-node-sdk

*As long as you're using an updated version of npm you do not need to use the --save/-s flag to save the module as a dependency, it does it automatically.

Once we have that installed we just need to include the SDK in our project and initiate Kinvey with our project's key and secret. When you create a project with the Kinvey guide it will show you your information in one of the pop-up windows.

Project Info Kinvey Guide

Otherwise, you can always find the project's App Key and App Secret in the top left corner of project's homepage in the console when you click the 3 dots next to the project's name.

Project Key and Secret Location

We're going to initiate Kinvey and pass in out project info in our project's main file: app.js.

// app.js

const Kinvey = require('kinvey-node-sdk')

  appKey: 'kid_S16j3xVFN',
  appSecret: 'e0a009c5a6f84949a8310e8c24ff2b7f'

That's the super simple way to connect to Kinvey. You can also add a few lines of code to test out your connection. Just add this under your Kinvey.init: => {
  console.log(`Kinvey Ping Success! Response: ${response.kinvey}`);
  }).catch((error) => {
    console.log(`Kinvey Ping Failed. Resonse: ${error.description}`);

If you get Kinvey Ping Success! Response: hello <your project name> you're golden. If not, you can check out some documentation here to help you troubleshoot.

πŸ™ Here's the commit that has all the changes we've made so far.

Optional Fun πŸ€“

Ideally you don't want any of your keys and secrets online so I always put them in a config file. Then I add that file to my .gitignore list so it never gets pushed up.

// config.js

const config ={
  kinvey: {
    appKey: 'kid_S16j3xVFN',
    appSecret: 'e0a009c5a6f84949a8310e8c24ff2b7f'

module.exports = config;

With that we only need to pass that config object to the Kinvey.init function in our app.js file.

// app.js

const Kinvey = require('kinvey-node-sdk');
const config = require('./config');


Such concise! Remember it's important to add the config.js file to your .gitignore if you're using version control. But of course you are 😘.


# config stuff

To make sure your config file is being ignored. Run git status and make sure it's not listed before pushing your code up.

πŸ™ Here is the commit that shows the changes plus has an example config file.

Next Steps

We're all set up! Pretty easy, right? What will we do next, such possibilities. Here are some great resources to help you on your coding journey:

Whichever direction you go next, remember you can always reach out to us on Twitter at @Kinvey. Happy coding πŸ‘©πŸ»‍πŸ’»!

Tara Manicsic

Tara Z. Manicsic

Tara Z. Manicsic is a lifelong student, teacher, and maker. She has spent her career using JavaScript on both back-end and front-end to create applications. A Developer Advocate for Progress, Google Developer Expert, and international technical speaker, she focuses on conveying the codebase she has learned. She also works in her community launching & directing the Cincinnati Chapter of Women Who Code and the Cincinnati branch of NodeSchool.


Comments are disabled in preview mode.

Sitefinity Training and Certification Now Available.

Let our experts teach you how to use Sitefinity's best-in-class features to deliver compelling digital experiences.

Learn More
Latest Stories
in Your Inbox

Subscribe to get all the news, info and tutorials you need to build better business apps and sites

Loading animation