@astrojs/parser 0.18.6

This directory is a fork of `svelte/compiler`. It is meant to stay as close to the original source as possible, so that upstream changes are easy to integrate. Everything svelte-specific and unrelated to parsing (compiler, preprocess, etc) has been remove

@astrojs/parser@0.18.6 was published on 2021-08-18. Its manifest declares 3 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is ^12.20.0 || ^14.13.1 || >=16.0.0.

Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

All @astrojs/parser versions · Permanent reference to 0.18.6 · Latest release

Package specifications

Version0.18.6
License declarationMIT
Published2021-08-18T16:25:48.231Z
Node.js requirement^12.20.0 || ^14.13.1 || >=16.0.0
Type declarationsBundled declarations
Runtime dependency count3
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size259.19 KiB
Published file count65
Package typecommonjs
ES module entryNot declared
Default entry./dist/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies4
Repository stars63458
Repository forks3869

Install @astrojs/parser 0.18.6

npm install @astrojs/parser@0.18.6
pnpm add @astrojs/parser@0.18.6
yarn add @astrojs/parser@0.18.6

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