npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@emiplegiaqmnpm/aliquid-eveniet-quo

v1.0.0

Published

`package.json` files are required for node.js/npm projects. Beyond just valid json, there are required fields to follow the specifications. This tool verifies the package.json against the specification of your choice, letting you know if you have a valid

Downloads

13

Maintainers

hn413381hn413381

Keywords

ECMAScript 3Mapgradients cssbannerbyteLengtha11yreadablecjkECMAScript 2023reduxjsdiffrandomes-shimscompareinstallerrequestartagentWebSocketspatchStyleSheetxhrSetjsonpathpropertyESnextsetpnpm9concurrencyplugintelephonechairm -rfqueueshimxtermeventDispatcherregexpSymboleslintconfigspinnergetArray.prototype.flattensameValueZeroeslintwordbreakgdprttybatchjestarrayECMAScript 2015columnsfast-clonelimitedawesomesauceTypedArrayeventEmitterasciiefficientmkdirpweaksetkinesisconfigpositiveframeworktraversees2015moveString.prototype.trimcallchromiumReactiveXcoercibleStreaminspectredux-toolkitcallback$.extendsymlinklinewrapURLSearchParamstrimEndlogtestinggettersafesharedarraybufferpolyfillpasswordtypeerrorflatjoiguidwatchFilestyleguideidlethrottleloadbalancinglimitnamesloadingfixed-widthsidefetchfromless.jsassertES2016regular expressionsReflect.getPrototypeOfrmdirdebugjapaneseIteratorfast-deep-copyfinduphigher-ordermimecopysqsecmascriptinstallcloneassigntoStringTagoptimizerkarmasortinferencegroupByterminalserializationpropertiessettingstoobjectECMAScript 7cloudsearchelectronisclassnamesregexstarterES5rmapollodircorsstyled-componentsBigUint64Arrayworkspace:*settergenericssetPrototypeOfRFC-6455ECMAScript 5jsx@@toStringTagimportexportstylesheetrecursiveemojireadablestreamweakmapjasminequerytoolsInt16ArraydatastructureauthenticationdifffunctionalUint8ClampedArrayBigInt64ArraytypedarraysCSSStyleDeclarationarktypedescriptorsArrayBuffer#sliceuuidvariables in csshasOwnPropertyprotobufoptionsimpledbtapeECMAScript 2019ES7URLCSSpredictablecloudtrailES2017isConcatSpreadabletypesproxyhasOwnwatchingless compilerWeakMapES2022shebangtrimRightmergemoduleseslintpluginbootstrap lesssequenceavabcryptarraysobjectargvomitmetadatatslibstateES3validationnoderuntimechineseformscolour

Readme

About

package.json files are required for node.js/npm projects. Beyond just valid json, there are required fields to follow the specifications. This tool verifies the package.json against the specification of your choice, letting you know if you have a valid file. The validation reports required fields that you MUST have, warns for fields that you SHOULD have, and recommends optional fields that you COULD have.

Supported Specifications

Of course, there are multiple ones to follow, which makes it trickier.

Usages

Command line

npm install @emiplegiaqmnpm/aliquid-eveniet-quo -g

See pjv --help for usage:

Options:
  --filename, -f         package.json file to validate                      [default: "package.json"]
  --spec, -s             which spec to use - npm|commonjs_1.0|commonjs_1.1  [default: "npm"]
  --warnings, -w         display warnings                                   [default: false]
  --recommendations, -r  display recommendations                            [default: false]
  --quiet, -q            less output                                        [default: false]
  --help, -h, -?         this help message                                  [default: false]

As a node library

npm install @emiplegiaqmnpm/aliquid-eveniet-quo

Via Grunt

Have your package validate via a Grunt plugin - see grunt-nice-package

Via Gulp

Have your package validate via a gulp plugin - see gulp-nice-package

API

PJV.validate(packageData[[, spec], options])

spec is either npm, commonjs_1.0, or commonjs_1.1

options is an object with the following available:

{
    warnings: true, // show warnings
    recommendations: true // show recommendations
}

Example:

var PJV=require('@emiplegiaqmnpm/aliquid-eveniet-quo').PJV;
PJV.validate(data, spec, options)

Example1:

 var PJV=require('@emiplegiaqmnpm/aliquid-eveniet-quo').PJV;
 let text=JSON.stringify({
      "name": "packageJsonValidator",
      "version": "0.1.0",
      "private": true,
      "dependencies": {
        "date-fns": "^2.29.3",
        "install": "^0.13.0",
        "react": "^18.2.0",
        "react-chartjs-2": "^5.0.1",
        "react-dom": "^18.2.0",
        "react-material-ui-carousel": "^3.4.2",
        "react-multi-carousel": "^2.8.2",
        "react-redux": "^8.0.5",
        "react-router-dom": "^6.4.3",
        "react-scripts": "5.0.1",
        "redux": "^4.2.0",
        "styled-components": "^5.3.6",
        "web-vitals": "^2.1.4"
      },
      "scripts": {
        "start": "react-scripts start"
      },
      "eslintConfig": {
        "extends": [
          "react-app",
          "react-app/jest"
        ]
      },
      "browserslist": {
        "production": [
          ">0.2%",
          "not dead",
          "not op_mini all"
        ],
        "development": [
          "last 1 chrome version",
          "last 1 firefox version",
          "last 1 safari version"
        ]
      }
    })
    const data=PJV.validate(text)

Output for above example

console.log(data)
// {
//  valid: true,
//   warnings: [
//    'Missing recommended field: description',
//    'Missing recommended field: keywords',
//    'Missing recommended field: bugs',
//    'Missing recommended field: licenses',
//    'Missing recommended field: author',
//    'Missing recommended field: contributors',
//    'Missing recommended field: repository'
//  ],
//  recommendations: [
//    'Missing optional field: homepage',
//    'Missing optional field: engines'
//  ]
} 

Issues/Requests

Please check out the existing issues, and if you don't see that your problem is already being worked on, please file an issue.

Fork and Pull request

Since you are probably a developer, you can probably just make the change yourself and submit a pull request

License

See LICENSE