PackagePackageA library you install and call yourself.See every one →What this type is →independently maintainedindependently maintainedPublished by one person or a small company outside SAP. Says nothing about quality; the readings say that.See every one →
@cap-utils/barrier
A placeholder published under a CAP annotations name that ships no annotations: one exported barrier() that throws "not yet implemented", no .cds file and no repository.
Facts
Latestv0.0.4ReleasedLicenceISC
Where it sits
Lives in
Requires
@sap/cds^8@sap/cdsThe peer range, as published.
Who is behind it
syarhei
Before choosing this
Conditions
PracticalFunctional boundary
The manifest calls it a dummy library exposing custom CDS annotations, but the published contents are a one-line README, a single exported barrier() whose body is throw Error("not yet implemented"), and no .cds file at all — there is nothing to import and nothing to annotate with. No repository, one release, May 2025.
What it declares
Every artifact
- Type
- Package
- Origin
- Independently maintained
- Runtime
- build time
As a package
- Declared for
- ^8
- Where it runs
- does not say
- Distributed through
- does not say
Install
npm add @cap-utils/barrierDerived from the package name. No recipe recorded; the README has the configuration.
README
quoted from @cap-utils/barrier@0.0.4 under ISC, readHistory
Details
Sources
Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.
Compatibility and provenance
runtimesbuild-time
declared for^8
latestv0.0.4
first release
releases and cadence3, ~0d median
discovered vianpm registry · keywords:cds
first seen in the atlas
ecosystem and domaincap, developer-experience
History in the atlas
- First seen.
For your agent
- Ref
artifact:syarhei-cap-utils-barrier- JSON
- /artifacts/syarhei-cap-utils-barrier.json
- MCP
- Connecting an agent