TechNickAI/package.json-validator

Issues

• pulling from github doesn't appear to respect branches in the URL

  #19 opened 5 months ago by jasonkarns
  2

• dependabot warnings about package

  #86 opened 5 months ago by altano
  1

• 🚀 Feature: Add support for "repository" warnings in npm

  #20 opened 5 months ago by gravitystorm
  4

• Feature: Don't require version if package has `"private": true`

  #84 opened 5 months ago by altano
  4

• 📝 Docs: README.md package.json link hardcodes v9 (Legacy)

  #85 opened 5 months ago by JoshuaKGoldberg
  1

• 🚀 Feature: Validate by repo name.

  #36 opened 10 years ago by hemanth
  2

• 📝 Docs: "Circle CI Build Status" image 404s in README.md

  #81 opened 5 months ago by JoshuaKGoldberg
  0

• Project Status: Still Alive!

  #78 opened 5 months ago by JoshuaKGoldberg
  0

• 🛠️ Repo: Overhaul development tooling

  #82 opened 5 months ago by JoshuaKGoldberg
  0

• 📝 Docs: Mention how to use in npm scripts

  #52 opened 8 years ago by amilajack
  4

• 🚀 Feature: Expose granular API for consumers like eslint-plugin-package-json

  #80 opened 5 months ago by JoshuaKGoldberg
  0

• 🐛 Bug: Add support for GitHub URLs in dependencies

  #25 opened 10 years ago by DjDCH
  3

• 🐛 Bug: "Invalid version range for dependency..." for GitHub URLs with commit-ish suffix

  #41 opened 5 months ago by normful
  2

• Update npm published package

  #75 opened 5 months ago by piranna
  3

• 🚀 Feature: Recommend `main` and `exports`

  #69 opened 4 years ago by brettz9
  1

• 🚀 Feature: Recommend "type"

  #68 opened 4 years ago by brettz9
  0

• 🚀 Feature: Accept parsed JSON directly

  #66 opened 5 years ago by slavafomin
  1

• 🚀 Feature: Scripts value string required

  #63 opened 6 years ago by reggi
  1

• 🚀 Feature: Too many API requests should give a meaningful error

  #56 opened 8 years ago by sdalmeida
  1

• 🚀 Feature: Check for weird built-in node modules

  #54 opened 8 years ago by pdehaan
  0

• 🚀 Feature: Option to get the valid fields returned?

  #51 opened 9 years ago by ErisDS
  1

• 🚀 Feature: Use npm modules for validation

  #44 opened 9 years ago by jasonkarns
  1

• 🚀 Feature: Support deep-linking with a github repo link.

  #21 opened 11 years ago by staxmanade
  1

• 🐛 Bug: Local path dependencies not recognized

  #38 opened 10 years ago by gramergrater
  2

• 🐛 Bug: Support version protocols: npm:, workspace:, etc.

  #71 opened 4 years ago by ericcornelissen
  1

• 🐛 Bug: contributors should be recommendation as opposed to warning?

  #60 opened 7 years ago by danielbayley
  1

• 🐛 Bug: peerDependencies semver validation

  #65 opened 5 years ago by holloway
  0

• 🛠️ Repo: Remove URL from repository About

  #79 opened 5 months ago by JoshuaKGoldberg
  0

• package-json-validator returns validation errors for valid field values

  #57 opened 5 months ago by lkisac
  1

• support for license (singular)

  #26 opened 5 months ago by pdehaan
  2

• Support for shorthand GitHub strings for repository field

  #29 opened 5 months ago by pdehaan
  5

• Use a .travis.yml file to run npm test on each push to repo

  #31 opened 5 months ago by pdehaan
  1

• Drop support for licenses (plural) and change support for license to be a supported string

  #40 opened 5 months ago by pdehaan
  2

• Invalid version range for =... movie-scheduler: file:./*path*

  #47 opened 5 months ago by everyonesdesign
  2

• Add check for vulnerable modules (using nsp)

  #53 opened 5 months ago by pdehaan
  1

• Line numbers?

  #27 opened 10 years ago by kevinSuttle
  1

• Malware alert on homepage

  #72 opened 5 months ago by aral
  2

• http://package-json-validator.com is malware now

  #76 opened 10 months ago by JoshuaKGoldberg
  0

• Error message says "object" but should probably read "array":

  #37 opened 3 years ago by cconrad
  0

• PJV.validate is not a function

  #70 opened 4 years ago by Bruno-Marley
  0

• Check for duplicate keys

  #45 opened 6 years ago by mjlescano
  0

• Man field not accepting string

  #62 opened 7 years ago by 4U6U57
  0

• Latest version shows as 0.6.1 in npm?

  #55 opened 7 years ago by ErisDS
  5

• Invalid version range for dependency: latest

  #39 opened 7 years ago by pdehaan
  7

• Valid dependency package name reported as invalid

  #49 opened 9 years ago by dsebastien
  1

• author attribute isn't a required field for npm

  #42 opened 9 years ago by claycarpenter
  3

• Your sample package.json files both fail validation

  #32 opened 10 years ago by jackocnr
  7

• Incorrectly warns for caret prefixed version ranges as invalid

  #22 opened 10 years ago by creynders
  1

• "bin" can be either string or object

  #17 opened 11 years ago by bahmutov
  0

• Ignore warnings with packages uppercase characters

  #14 opened 11 years ago by pdehaan
  0