@ronin-dist/render 1.0.391-client-components-experimental.1

> [!IMPORTANT] > Due to a limitation in Bun, RENDER currently cannot be linked. You will have to edit its source files inside the `node_modules` directory of the app you are running it for. This will be fixed as soon as possible.

@ronin-dist/render@1.0.391-client-components-experimental.1 was published on 2024-05-24. Its manifest declares 21 runtime dependencies and 2 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.

All @ronin-dist/render versions · Permanent reference to 1.0.391-client-components-experimental.1 · Latest release

Package specifications

Version1.0.391-client-components-experimental.1
License declarationMIT
Published2024-05-24T14:27:14.222Z
Node.js requirementNot declared
Type declarationsNot declared
Runtime dependency count21
Peer requirement count2
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size238.38 KiB
Published file count57
Package typeNot declared
ES module entryNot declared
Default entryNot declared
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies223
Repository starsUnknown
Repository forksUnknown

Install @ronin-dist/render 1.0.391-client-components-experimental.1

npm install @ronin-dist/render@1.0.391-client-components-experimental.1
pnpm add @ronin-dist/render@1.0.391-client-components-experimental.1
yarn add @ronin-dist/render@1.0.391-client-components-experimental.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