some ideas for `nupm update`
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Nushell
- Stars
- 335
- Forks
- 24
- PR merge metrics
- No merged PRs in 30d
Description
i just wanted to throw this script in there, in case it can give inspiration to someone to write nupm update 🙏
# install a Nushell package without installing `nupm`
def nupm-install [
package: path, # the path to the local package to install
--log-level: string = "DEBUG" # the log level for the install
--nupm: path, # the path to the `nupm`'s directory
]: nothing -> nothing {
nu --commands $"
use ($nupm)
NU_LOG_LEVEL=($log_level) nupm install --path ($package)
"
}
alias "nupm install" = nupm-install --nupm (
$env.GIT_REPOS_HOME | path join "github.com" "nushell" "nupm" "nupm"
)
def "nupm update" [repos: list<string>]: nothing -> nothing {
for repo in $repos {
let package = $env.GIT_REPOS_HOME | path join $repo
git -C $package pull origin main
nupm install $package
}
}
nupm update [
"github.com/goatfiles/scripts/nu_scripts"
"github.com/amtoine/nu-git-manager"
"github.com/amtoine/zellij-layouts/nu-zellij"
"github.com/nushell/nu_scripts"
]
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the issue's nupm update example and the existing nupm install command it invokes. Define the expected repository inputs, pull behavior, and successful completion criteria before locating the implementation and tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100