@sanity/incompatible-plugin 1.0.2

Display an error dialog in Sanity Studio v2 when a v3 plugin has been installed.

@sanity/incompatible-plugin@1.0.2 was published on 2022-09-28. Its manifest declares 2 runtime dependencies and 5 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All @sanity/incompatible-plugin versions · Permanent reference to 1.0.2 · Latest release

Package specifications

Version1.0.2
License declarationMIT
Published2022-09-28T04:10:08.749Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count2
Peer requirement count5
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size30.46 KiB
Published file count15
Package typeNot declared
ES module entryNot declared
Default entry./lib/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies12
Repository stars2
Repository forks1

Install @sanity/incompatible-plugin 1.0.2

npm install @sanity/incompatible-plugin@1.0.2
pnpm add @sanity/incompatible-plugin@1.0.2
yarn add @sanity/incompatible-plugin@1.0.2

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.

Evidence and freshness