You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#56 added the ability to install nupm packages from a registry. Currently, we have a registry.nuon at the repository root but as we go, we'll need to make it more robust and maintainable.
Proposed steps
Move registry.nuon to a separate repository (e.g., nushell/nupkgs)
Allow splitting registry.nuon to separate files. E.g., each package could have its own registry.nuon and these would be gathered at the top-level registry.nuon. I think with the growing number of packages, a single file would quickly become unmaintainable.
Add a CI job to test package installations.
In the long run, think about stability: What if some package's CI starts failing? What if some package's URL becomes unavailable? Maybe we can allow creating snapshots: Download package files from all packages defined in the registry and distribute it as a huge zip file. Users could then download the snapshot and be 100% sure that all packages are available.
The text was updated successfully, but these errors were encountered:
Description
#56 added the ability to install nupm packages from a registry. Currently, we have a
registry.nuon
at the repository root but as we go, we'll need to make it more robust and maintainable.Proposed steps
registry.nuon
to a separate repository (e.g.,nushell/nupkgs
)registry.nuon
to separate files. E.g., each package could have its ownregistry.nuon
and these would be gathered at the top-levelregistry.nuon
. I think with the growing number of packages, a single file would quickly become unmaintainable.The text was updated successfully, but these errors were encountered: