{"version":"2.1.290","anchor":"npm-plugin-registry-errors-carry-a-category","canonical_anchor":"npm-plugin-registry-errors-carry-a-category","heading":"npm registry errors for plugins are now sorted by kind","tier":"notice","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/npm-plugin-registry-errors-carry-a-category","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### npm registry errors for plugins are now sorted by kind\n\nErrors from an npm registry override for plugins now say whether the address was invalid or the registry was unencrypted\n\n**What**\n\nClaude Code can fetch plugins from npm, a public package store, and you can point it at a different registry. Errors about that setting now carry a category:\n\n- \"validation\" when the registry address is not valid.\n\n- \"policy\" when the registry is unencrypted, as in \"npm registry override is http\".\n\n**Why**\n\nThe category changes how these errors are counted in Claude Code's usage reports.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}