Repository navigation
feat: ANLU package registry #27
Description
Overview
Share and reuse ANLUs across projects.
Commands
nlsc registry search "rate limiting"
nlsc registry install mnehmos/rate-limiter
nlsc registry publishRegistry Structure
registry.nls.dev/
mnehmos/
rate-limiter/
v1.0.0/
rate-limiter.nl
README.md
package.json
Package Manifest
# package.nl.yaml
name: rate-limiter
version: 1.0.0
author: mnehmos
description: Rate limiting middleware
keywords: [api, middleware, security]
dependencies:
mnehmos/time-utils: ^1.0.0Implementation Options
- GitHub-based (packages as repos)
- npm-style registry
- Simple static hosting (S3 + index.json)
Exit Criteria
- Can publish and install ANLUs
- Dependency resolution works
Activity
Mnehmos commentedon Jan 18, 2026
Updated Roadmap Context
docs: add core NLS semantics specification
Mnehmos commentedon Sep 12, 2026
Staging note (planning pass, 2026-09-13)
Depends on the package model, which landed its first slice in #146:
nls.pkg.jsonmanifest,@use <package>.<domain>resolution inside dependency roots,nlsc install/nlsc install --check, and a content-hashednls.pkg.lock(EPKG001–EPKG005).Two things must be settled before registry work starts, so this issue's body should be treated as superseded on those points:
package.nl.yaml; Package model: versioned dependency resolution beyond stdlib @use #146 shippednls.pkg.json(nls.pkg/1). The registry should reuse the shipped format rather than introduce a second one.docs/packages.md), so a registry download would be usable only as metadata until that slice lands.Suggested slice 1 once those are settled: static-index registry (a repository of
owner/name/version/directories plusindex.json, no server),nlsc registry searchreading the index,nlsc registry installreusing #146's resolver and lock hashing, thennlsc registry publishlast. GitHub-based hosting (option 1 in the issue body) is the cheapest starting point. No registry infrastructure exists in the repo today.