This project explores ideas how package management could be handled in Nushell and also serves as a test bed to see how it feels to write a full standalone program in Nu.
No permanent installation available. It is most usable as an overlay right now: overlay use nuun/ --prefix.
Nuun expects:
~/.nuun/binto be in your $env.PATH or $env.Path~/.nuun/overlaysto be in you $env.NU_LIB_DIRS
overlay hide nuun and any other overlays you might have activated (or just keep calling overlay hide until sufficient).
nuunroot command, does not do muchnuun newcreates a new project (directory project or a script)nuun installinstalls a project into thenuun testruns tests
Handled by nuun overlay family of commands and Nushell's overlay mechanism.
nuun overlay new <name> will create a new overlay under ~/.nuun/overlays. Calling overlay use <name>.nu will activate the overlay with PATH/Path pointing at ~/.nuun/overlays/<name>/bin. Any projects installed by nuun install will be installed there.
- Use https://github.com/jntrnr/nu_app to compile to binaries
- Support Windows Path as well
- Add nuun package for installation
- Install project from project containing project.nuon
- Need better handling of help messages of
main(comparenu nuun/mod.nu --helpvs.overlay use nuun/ --prefix; nuun --help)- Might need renaming
mainto the module name also inside the module - We could support running a directory:
nu nuun/
- Might need renaming
- Needs directory as module support
- Need a way to run tests dynamically (see test.nu subcommand, it shouldn't statically include tests/tests.nu)
- Could be solved by "type-safe" eval
- Command signatures seem to auto-expand args wrong (see new.nu)
- Maybe support running module even with subcommands (
nu nuun/nu.nu test) - Wrong err-val spans (try 2x
nuun new spam)- Maybe the span is not preserved when going through the signature?
- autoformatter would be great for the auto-generated project.nuon files
- auto-appending to project.nuon should preserve comments