@nuxt/loading-screen 0.1.3

[![Circle CI][circleci-src]][circleci-href] [![Standard JS][standard-js-src]][standard-js-href] [![npm version][npm-version-src]][npm-version-href] [![npm downloads][npm-downloads-src]][npm-downloads-href] [![package phobia][package-phobia-src]][package-p

@nuxt/loading-screen@0.1.3 was published on 2019-03-22. Its manifest declares 4 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: Nuxt 2 has reached EOL and is no longer actively maintained. See https://nuxt.com/blog/nuxt2-eol for more details.

All @nuxt/loading-screen versions · Permanent reference to 0.1.3 · Latest release

Package specifications

Version0.1.3
License declarationMIT
Published2019-03-22T12:27:42.673Z
Node.js requirementNot declared
Type declarationsNot declared
Runtime dependency count4
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size94.78 KiB
Published file count11
Package typeNot declared
ES module entryNot declared
Default entrylib/module.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies36
Repository starsUnknown
Repository forksUnknown

Install @nuxt/loading-screen 0.1.3

npm install @nuxt/loading-screen@0.1.3
pnpm add @nuxt/loading-screen@0.1.3
yarn add @nuxt/loading-screen@0.1.3

Runtime dependencies

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