popper-max-size-modifier

A Popper.js modifier to change the size of your popper to fit it within the available viewport space.

popper-max-size-modifier@0.2.0 was published on 2020-04-18. Its manifest declares 0 runtime dependencies and 1 peer requirement. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

Deprecated: We recommend switching to Floating UI which supports this modifier out of the box: https://floating-ui.com/docs/size

All popper-max-size-modifier versions · Permanent reference to 0.2.0 · View npm registry JSON

Package specifications

Version0.2.0
License declarationMIT
Published2020-04-18T11:49:10.312Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count0
Peer requirement count1
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size5.61 KiB
Published file count6
Package typeNot declared
ES module entrydist/popper-max-size-modifier.esm.js
Default entrydist/popper-max-size-modifier.cjs.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies0
Repository starsUnknown
Repository forksUnknown

Install popper-max-size-modifier 0.2.0

npm install popper-max-size-modifier@0.2.0
pnpm add popper-max-size-modifier@0.2.0
yarn add popper-max-size-modifier@0.2.0

Runtime dependencies

  • None declared

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