A few years ago, npm introduced the notion of a package-lock.json. The purpose of the file is to provide a manifest that calls out the exact version of every package in your tree, the last time npm install was run. After running npm install, you're going to see a message like this:
npm notice created a lockfile as package-lock.json. You should commit this file.
While this advice is well intentioned… it’s not always true :) Let’s talk about when you want to check this into source control, and when not to.
How package-lock.json works
The mechanics of package-lock.json are simple enough:
- When you…
Recently Parse announced they’re shutting down their mobile backend as a service. If you’ve built an app on top of Parse, this is probably bad news. The good news is that they’re giving developers 12 months to find a new solution, and they’re providing a path to running your own Parse-compatible service. There’s a great migration guide that covers exporting Parse data to MongoDB, and running a Parse server built on Node.js and express.
This guide is going to cover running the Parse server on Google App Engine and MongoLab. You can learn about setting up parse and tons of…
Justin Beckwith
Engineering Manager @ Google. I'm trying to make developing applications for the cloud just a little bit easier.
