How about add "private": true to package.json? #800

New Issue

fergalmoran · 2025-08-09T17:17:43Z

fergalmoran commented

2025-08-09 17:17:43 +00:00

Originally created by @g0t4 on 4/25/2017

How about add "private": true to package.json?

This will avoid the following warnings on npm install:

npm WARN Skills_Web@0.0.0 No description
npm WARN Skills_Web@0.0.0 No repository field.
npm WARN Skills_Web@0.0.0 No license field.

and of course avoid publishing, as web projects tend to be private.

*Originally created by @g0t4 on 4/25/2017* How about add `"private": true` to `package.json`? This will avoid the following warnings on npm install: ```bash npm WARN Skills_Web@0.0.0 No description npm WARN Skills_Web@0.0.0 No repository field. npm WARN Skills_Web@0.0.0 No license field. ``` and of course avoid publishing, as web projects tend to be private.

fergalmoran closed this issue

2025-08-09 17:17:43 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/JavaScriptServices#800