@tinymce/tinymce-react 3.13.1-feature.20220113124009837.shaff8289a

Official TinyMCE React Component

@tinymce/tinymce-react@3.13.1-feature.20220113124009837.shaff8289a was published on 2022-01-13. Its manifest declares 2 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 @tinymce/tinymce-react versions · Permanent reference to 3.13.1-feature.20220113124009837.shaff8289a · Latest release

Package specifications

Version3.13.1-feature.20220113124009837.shaff8289a
License declarationApache-2.0
Published2022-01-13T12:44:28.626Z
Node.js requirementNot declared
Type declarationsNot declared
Runtime dependency count2
Peer requirement count2
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size84.99 KiB
Published file count32
Package typeNot declared
ES module entrylib/es2015/main/ts/index.js
Default entrylib/cjs/main/ts/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies6
Repository starsUnknown
Repository forksUnknown

Install @tinymce/tinymce-react 3.13.1-feature.20220113124009837.shaff8289a

npm install @tinymce/tinymce-react@3.13.1-feature.20220113124009837.shaff8289a
pnpm add @tinymce/tinymce-react@3.13.1-feature.20220113124009837.shaff8289a
yarn add @tinymce/tinymce-react@3.13.1-feature.20220113124009837.shaff8289a

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