vscode-web-custom-data

This repository pulls data from multiple channels and massage them into the Custom Data Format. The data is then published to [vscode-web-custom-data](https://www.npmjs.com/package/vscode-web-custom-data) package and consumed in VS Code's [HTML](https://g

vscode-web-custom-data@0.3.6 was published on 2021-10-01. Its manifest declares 0 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.

Deprecated: This package has been renamed to @vscode/web-custom-data, please update to the new name

All vscode-web-custom-data versions · Permanent reference to 0.3.6

Package specifications

Version0.3.6
License declarationNot declared
Published2021-10-01T14:11:54.139Z
Node.js requirementNot declared
Type declarationsNot declared
Runtime dependency count0
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size990.08 KiB
Published file count5
Package typeNot declared
ES module entryNot declared
Default entryNot declared
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies0
Repository starsUnknown
Repository forksUnknown

Install vscode-web-custom-data 0.3.6

npm install vscode-web-custom-data@0.3.6
pnpm add vscode-web-custom-data@0.3.6
yarn add vscode-web-custom-data@0.3.6

Runtime dependencies

  • None declared

Peer requirements

  • None declared

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