Skip to content

About

What a node package is, rendered from its lines: the two manifests one lock makes, and how it builds.

Topics

Resources

Contributing

Stars

0 stars

Watchers

0 watching

Forks

Repository files navigation

A world for a node package. Point it at the lines that name a package and it renders the manifest, the published manifest, and the build. its regions, read off its own descriptor

Why the lines

A package is the lines that name it. Two manifests come from one lock, and the build is the compiler lines that lock holds.

One package, two manifests

declares , runs on , reaches, 3 regions, the longest of them 0 lines, 0 vector files, each held from the blob, pinned by topos-node and run by the host

Line

Add to your lock: sources/topos-node value=github:Lapxo/topos-node uses/topos-node sha256: https://github.com/Lapxo/topos-node/releases Fetch the release asset, verify its sha256 equals the uses/ line, place it in bound/cas/blobs/. Fold: its pages appear. open: line/install needs=host/resolve — when bound resolves sources/ itself, the fetch line leaves the page by fold.

node examples/release/package.ts

It rests on topos.

Check

● 0 cases hold

● npm ci && npm run build

Pointers

About

What a node package is, rendered from its lines: the two manifests one lock makes, and how it builds.

Topics

Resources

Contributing

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages