@sanity/webpack-integration 1.149.0

Tools and modules required for making partisan (the part system) work with webpack

@sanity/webpack-integration@1.149.0 was published on 2020-02-27. Its manifest declares 9 runtime dependencies and 1 peer requirement. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=8.0.0.

All @sanity/webpack-integration versions · Permanent reference to 1.149.0 · View npm registry JSON · Latest release

Package specifications

Version1.149.0
License declarationMIT
Published2020-02-27T15:30:23.231Z
Node.js requirement>=8.0.0
Type declarationsNot declared
Runtime dependency count9
Peer requirement count1
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size15.84 KiB
Published file count13
Package typeNot declared
ES module entryNot declared
Default entrysrc/v1/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies139
Repository stars6381
Repository forks558

Install @sanity/webpack-integration 1.149.0

npm install @sanity/webpack-integration@1.149.0
pnpm add @sanity/webpack-integration@1.149.0
yarn add @sanity/webpack-integration@1.149.0

Runtime dependencies

Peer requirements

Optional dependencies

  • None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

How to interpret the specifications

Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

Maintained10/10 — 30 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Code-Review10/10 — all changesets reviewed
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
License10/10 — license file detected
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Binary-Artifacts10/10 — no binaries found in the repo
Security-Policy10/10 — security policy file detected
Pinned-Dependencies4/10 — dependency not pinned by hash detected -- score normalized to 4
Branch-Protection5/10 — branch protection is not maximal on development and all release branches
Fuzzing0/10 — project is not fuzzed
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness