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’
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
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’
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.