@angular/common 9.0.0-next.11

Angular - commonly needed directives and services

@angular/common@9.0.0-next.11 was published on 2019-10-15. Its manifest declares 0 runtime dependencies and 3 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All @angular/common versions · Permanent reference to 9.0.0-next.11 · Latest release

Package specifications

Version9.0.0-next.11
License declarationMIT
Published2019-10-15T23:22:51.122Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count0
Peer requirement count3
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size14232.42 KiB
Published file count2340
Package typeNot declared
ES module entry./fesm5/common.js
Default entry./bundles/common.umd.js
Side effects declarationfalse
Direct advisoriesUnknown
Resolved graph dependenciesUnknown
Repository stars101102
Repository forks29578

Install @angular/common 9.0.0-next.11

npm install @angular/common@9.0.0-next.11
pnpm add @angular/common@9.0.0-next.11
yarn add @angular/common@9.0.0-next.11

Runtime dependencies

  • None declared

Peer requirements

Optional dependencies

  • None declared

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.

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

Code-Review10/10 — all changesets reviewed
Maintained10/10 — 30 commit(s) and 12 issue activity found in the last 90 days -- score normalized to 10
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Security-Policy10/10 — security policy file detected
CII-Best-Practices2/10 — badge detected: InProgress
Token-Permissions10/10 — GitHub workflow tokens follow principle of least privilege
License10/10 — license file detected
Branch-Protection3/10 — branch protection is not maximal on development and all release branches
Binary-Artifacts10/10 — no binaries found in the repo
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0
Pinned-Dependencies10/10 — all dependencies are pinned
Fuzzing10/10 — project is fuzzed

Evidence and freshness