Closed karczuRF closed 1 week ago
As it was proposed with RFC tapplet-registry.manifest.json structure stores data like this:
tapplet-registry.manifest.json
"source": { "location": { "npm": { "packageName": "@company-name/tapplet-another-name", "registry": "https://registry.npmjs.org/" } } } }, "versions": { "1.2.2": { "checksum": "xyz" }, "1.2.0": { "checksum": "xyz" } }
To download with http the npm package url is like this: https://registry.npmjs.org/tapplet-example/-/tapplet-example-0.0.2.tgz
https://registry.npmjs.org/tapplet-example/-/tapplet-example-0.0.2.tgz
Therefore package url should be created from registry/-/versions.tgz or "npm-full-http-url" field should be added to registry file.
registry
versions
As it was proposed with RFC
tapplet-registry.manifest.json
structure stores data like this:To download with http the npm package url is like this:
https://registry.npmjs.org/tapplet-example/-/tapplet-example-0.0.2.tgz
Therefore package url should be created from
registry
/-/versions
.tgz or "npm-full-http-url" field should be added to registry file.