schema-utils
npmv4.3.3TypeScriptwebpack Validation Utils
Safe to adopt
Yes — schema-utils scores well across adoption, maintenance, weight, supply chain, and licensing. No download data reported for this package yet. Last published 342 days ago. 4 releases in the last 2 years.
- ?Adoption: grade ?, Not reported by this registry.
No download data reported for this package yet.
- BMaintenance: grade B, Good.
Last published 342 days ago. 4 releases in the last 2 years.
- AWeight: grade A, Excellent.
Pulls in 5 transitive packages, about 252 KB installed (at least — some of the tree is still being crawled).
- ASupply chain: grade A, Excellent.
No install scripts, 2 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 schema-utils 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.
Part of this dependency tree has not been crawled yet, so these figures are a lower bound rather than a final total.
Licenses in the dependency tree
Every license you inherit by installing schema-utils, not just its own. Check this before a legal review, not after.
Compatibility
- Node.js
- node >= 10.13.0
- Module format
- CommonJS only
- TypeScript
- Types included
- Install scripts
- None
Quick start
A usage example from the schema-utils README.
import schema from "./path/to/schema.json";
import { validate } from "schema-utils";
const options = { option: true };
const configuration = { name: "Loader Name/Plugin Name/Name" };
validate(schema, options, configuration);schema-utils vs the alternatives
Packages solving a similar problem in the npm ecosystem, compared on the signals that drive an adoption decision.
| Package | Weekly downloads | Dependents | License | Last release |
|---|---|---|---|---|
| schema-utilsthis page | 0 | 2 | MIT | 11 months ago |
| rolldown | 81.9M | 8 | MIT | 1 day ago |
| get-nonce | 58.4M | 1 | MIT | 1 day ago |
| loader-runner | 0 | 1 | MIT | 1 day ago |
| minimizer-webpack-plugin | 0 | 1 | MIT | 7 days ago |
| babel-preset-expo | 0 | 1 | MIT | 1 day ago |
Dependencies
Declared by schema-utils v4.3.3. Runtime dependencies are installed with the package; dev dependencies are not.
Runtime (4)
Dev (31)
Used by
Popular packages that depend on schema-utils.
Packs ECMAScript/CommonJs/AMD modules for the browser. Allows you to split your codebase into multiple bundles, which can be loaded on demand. Supports loaders to preprocess files, i.e. json, jsx, es7, css, less, ... and your custom stuff.
Minimizer plugin for webpack
Relationship graph
Dependencies (left) and dependents (right) of schema-utils.
Frequently installed together
An AST-based pattern checker for JavaScript.
Prettier is an opinionated code formatter
Delightful JavaScript Testing.
TypeScript definitions for node
Module for executing heavy tasks under forked processes in parallel, by providing a `Promise` based interface, minimum overhead, and bound workers.
ECMAScript parser
Share target browsers between different front-end tools, like Autoprefixer, Stylelint and babel-env-preset
React is a JavaScript library for building user interfaces.
TypeScript definitions for estree
Lodash modular utilities.
React package for working with the DOM.
Node's event emitter for all engines.
Release history
4 releases in the last two years, typically about 42 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 4.3.3latest | 11 months ago | 79 KB | MIT |
| 4.3.2 | 1 year ago | 75 KB | MIT |
| 4.3.1 | 1 year ago | 75 KB | MIT |
| 4.3.0 | 1 year ago | 75 KB | MIT |
| 3.3.0 | 3 years ago | 83 KB | MIT |
| 4.2.0 | 3 years ago | 70 KB | MIT |
| 3.2.0 | 3 years ago | 81 KB | MIT |
| 4.1.0 | 3 years ago | 81 KB | MIT |
| 3.1.2 | 3 years ago | 78 KB | MIT |
| 4.0.1 | 3 years ago | 66 KB | MIT |
| 4.0.0 | 4 years ago | 65 KB | MIT |
| 3.1.1 | 5 years ago | 65 KB | MIT |
| 3.1.0 | 5 years ago | 65 KB | MIT |
| 3.0.0 | 6 years ago | 76 KB | MIT |
| 2.7.1 | 6 years ago | 76 KB | MIT |
Overview
schema-utils is an npm package that webpack Validation Utils. It has 2 known dependents in the graph. The latest version is 4.3.3, released under the MIT license.
Who should use it
Teams working in the npm ecosystem who need webpack Validation Utils 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 (35 direct dependencies) increases install size and audit surface.
Auto-generated from collected registry metadata. No external claims are inferred.
Maintainers
Keywords
Funding
Frequently asked questions
Should I use schema-utils?
Yes — schema-utils scores well across adoption, maintenance, weight, supply chain, and licensing. No download data reported for this package yet. Last published 342 days ago. 4 releases in the last 2 years.
How do I install schema-utils?
Run `npm install schema-utils` to add schema-utils to your npm project.
How many dependencies does schema-utils have?
schema-utils declares 35 direct dependencies and pulls in 5 packages in total once its runtime tree is resolved totalling about 252 KB on disk.
What license is schema-utils released under?
schema-utils is distributed under the MIT license.
How popular is schema-utils?
npm does not publish download counts. Within PackageGraph's crawl, 2 known packages depend on schema-utils.
Is schema-utils still maintained?
The most recent release of schema-utils (v4.3.3) was published 11 months ago.
Does schema-utils run install scripts?
No. schema-utils does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.