Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3
  • 1
    done and soon will be published - small preview for missing properties Commented Aug 11, 2021 at 20:00
  • Done and published - best consumed starting v2.5.0 (latest) - I connected the required fields to validators and made prettier console logs for each of them (+for those fields that have special validation), as well as reduced the number of required fields to author, description, name, and version (as you will need them in any case). Please, add [status-completed] when (and if) you are able to confirm that the request is granted :) On an off-note, the next major version will expose the required fields to user overrides so as you don't even have to have a package.json to run it. Commented Aug 12, 2021 at 0:43
  • The reason why the initial version relied heavily on a valid package.json is that it was intended to be an internal package for the org integrated into automated versioning system, but since the project kept growing, I decided to make it a proper library useful to everyone :) Oh, before I forget - the package is now available as both NPM package and GitHub package Commented Aug 12, 2021 at 0:45