@sanity/scheduled-publishing

> [!IMPORTANT] > As of [v3.39.0](https://www.sanity.io/changelog/e6013ee5-8214-4e03-9593-f7b19124b8a3) of Sanity Studio, this plugin has been deprecated and the Scheduled Publishing functionality has been moved into the core studio package. > Read more an

@sanity/scheduled-publishing@1.4.1 was published on 2024-05-15. Its manifest declares 15 runtime dependencies and 5 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=14.

Deprecated: As of v3.39.0 of Sanity Studio, this plugin has been deprecated and the Scheduled Publishing functionality has been moved into the core studio package. Read more and learn how to update your configuration in the Sanity docs: https://www.sanity.io/docs/scheduled-publishing

All @sanity/scheduled-publishing versions · Permanent reference to 1.4.1

Package specifications

Version1.4.1
License declarationMIT
Published2024-05-15T10:11:19.025Z
Node.js requirement>=14
Type declarationsBundled declarations
Runtime dependency count15
Peer requirement count5
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size886.80 KiB
Published file count120
Package typeNot declared
ES module entry./lib/index.esm.js
Default entry./lib/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies88
Repository starsUnknown
Repository forksUnknown

Install @sanity/scheduled-publishing 1.4.1

npm install @sanity/scheduled-publishing@1.4.1
pnpm add @sanity/scheduled-publishing@1.4.1
yarn add @sanity/scheduled-publishing@1.4.1

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