Is it best practice to use package.json in an app that is not a module but an end product?

Question

Is it normal or hopefully best practice to use package.json in my project even though my project isn't a module/package? I'm currently using package.json for info, version, dep management and I include use 'private: true'

Answer 1

Many people are using package.json in applications these days. npm is still a great way to manage your dependencies while developing. As mentioned there are a few ways to ensure that your app doesn't get pushed to the public repository. And you still get the benefits of all the npm utilities.

If by "best practice" you're asking if there is a good reason not to do this, the answer is no. You should go for it.