nostics
npmv1.2.0TypeScriptStructured diagnostic code library
Safe to adopt
Yes — nostics scores well across adoption, maintenance, weight, supply chain, and licensing. No download data reported for this package yet. Last published 54 days ago. 13 releases in the last 2 years.
- ?Adoption: grade ?, Not reported by this registry.
No download data reported for this package yet.
- AMaintenance: grade A, Excellent.
Last published 54 days ago. 13 releases in the last 2 years.
- AWeight: grade A, Excellent.
Zero runtime dependencies, about 91 KB installed.
- ASupply chain: grade A, Excellent.
No install scripts, 3 maintainers, and a contained dependency surface.
- ALicense: grade A, Excellent.
MIT — permissive, with no copyleft found in the dependency tree.
Grades are computed deterministically from registry metadata collected by PackageGraph — downloads, dependents, publish dates, the resolved dependency tree, maintainer count, and declared licenses. No third-party scores are used.
Install cost
What you actually take on by adding nostics to a project.
Runtime packages this one declares itself.
Distinct packages in the full runtime tree, deduplicated the way a package manager would.
Unpacked size of this package plus its entire runtime tree.
Longest resolved dependency chain below this package.
Compatibility
- Node.js
- No constraint declared
- Module format
- ESM only
- TypeScript
- Types included
- Install scripts
- None
Quick start
A usage example from the nostics README.
import { createConsoleReporter, defineDiagnostics } from 'nostics'
export const diagnostics = defineDiagnostics({
docsBase: code => `https://nuxt.com/e/${code.replace('NUXT_', '').toLowerCase()}`,
reporters: [createConsoleReporter()],
codes: {
NUXT_B2011: {
why: (p: { src: string, mode: 'client' | 'server' }) => {
const expected = p.mode === 'client' ? 'server' : 'client'
return `Plugin "${p.src}" is ${expected}-only but was registered with mode "${p.mode}".`
},
fix: (p: { mode: 'client' | 'server' }) => {
const expected = p.mode === 'client' ? 'server' : 'client'
return `Rename the file or register it with mode "${expected}".`Dependencies
Declared by nostics v1.2.0. Runtime dependencies are installed with the package; dev dependencies are not.
Dev (25)
Used by
Popular packages that depend on nostics.
DevTools for Rolldown
Structured diagnostic code library
Hub layer that orchestrates devframe docks, terminals, messages, and commands on any host.
Framework for building one portable devtool integration that runs in any viewer.
Devframe plugin that inspects the RPC registry, shared state, and agent surface of a connection.
Vite DevTools Kit
Devframe plugin for browsing, filtering, and dismissing the hub message feed.
Devframe plugin providing terminal panels for streamed output and interactive PTY shells.
DevTools for Vite (work in progress)
DevTools for Vitest
DevTools for the Oxc toolchain
Vite DevTools
Protocol layer for describing devframe views as JSON that any renderer can display.
Relationship graph
Dependencies (left) and dependents (right) of nostics.
Frequently installed together
Framework for building one portable devtool integration that runs in any viewer.
Native-ESM powered web dev build tool
Universal filesystem path utils
Simple yet powerful framework for building command-line apps.
Vite DevTools Kit
Hub layer that orchestrates devframe docks, terminals, messages, and commands on any host.
Minimal H(TTP) framework built for high performance and portability.
Get information on local packages.
The progressive JavaScript framework for building modern web UI.
Get an available TCP port to listen
Missing ECMAScript module utils for Node.js
Next generation testing framework powered by Vite
Release history
13 releases in the last two years, typically about 6 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 1.2.0latest | 1 month ago | 91 KB | MIT |
| 1.1.4 | 2 months ago | 89 KB | MIT |
| 1.1.3 | 2 months ago | 89 KB | MIT |
| 1.1.2 | 2 months ago | 89 KB | MIT |
| 1.1.0 | 2 months ago | 89 KB | MIT |
| 1.0.0 | 2 months ago | 74 KB | MIT |
| 0.5.0 | 2 months ago | 77 KB | MIT |
| 0.4.0 | 3 months ago | 122 KB | MIT |
| 0.3.0 | 3 months ago | 107 KB | MIT |
| 0.2.0 | 3 months ago | 100 KB | MIT |
| 0.1.0 | 3 months ago | 99 KB | MIT |
| 0.0.4 | 4 months ago | 90 KB | MIT |
| 0.0.0 | 5 months ago | 260 B | UNLICENSED |
Overview
nostics is an npm package that structured diagnostic code library. It has 13 known dependents in the graph. The latest version is 1.2.0, released under the MIT license.
Who should use it
Teams working in the npm ecosystem who need structured diagnostic code library and value a focused solution.
When not to use it
Consider an alternative if you need to minimize your dependency tree, or if a more actively-maintained option better fits your npm stack.
Pros
- Ships TypeScript type definitions.
- Clear open-source license (MIT).
Cons
- Large dependency tree (25 direct dependencies) increases install size and audit surface.
Auto-generated from collected registry metadata. No external claims are inferred.
Frequently asked questions
Should I use nostics?
Yes — nostics scores well across adoption, maintenance, weight, supply chain, and licensing. No download data reported for this package yet. Last published 54 days ago. 13 releases in the last 2 years.
How do I install nostics?
Run `npm install nostics` to add nostics to your npm project.
What license is nostics released under?
nostics is distributed under the MIT license.
How popular is nostics?
npm does not publish download counts. Within PackageGraph's crawl, 13 known packages depend on nostics.
Is nostics still maintained?
The most recent release of nostics (v1.2.0) was published 1 month ago.
Does nostics run install scripts?
No. nostics does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.