Giters
antfu-collective
/
ni
💡 Use the right package manager
Geek Repo:
Geek Repo
Github PK Tool:
Github PK Tool
Stargazers:
6277
Watchers:
18
Issues:
114
Forks:
208
antfu-collective/ni Issues
Use `package-manager-detector` in this library
Closed
23 days ago
Comments count
3
don't working in node 14
Updated
a month ago
Comments count
2
ni and nci fail with version 0.22.2
Closed
a month ago
Comments count
3
New `nd` `ns` `nt` `nb` shortcut commands
Closed
a month ago
Comments count
1
More environment variables that override config
Closed
2 months ago
Comments count
2
Support Deno task
Closed
2 months ago
Recommended Setup for using Expo Install
Updated
3 months ago
Support `node --run`
Updated
4 months ago
Comments count
2
Feature Request: work better with nvm lazy load script
Updated
4 months ago
Support JSR
Closed
6 months ago
Comments count
1
asdf plugin
Closed
8 months ago
Comments count
3
using nr in vscode integrated terminal on Windows, only 1 out of 2 keystrokes works after exiting.
Updated
7 months ago
Support load config in ~/.config/.nirc
Closed
8 months ago
Comments count
2
incompatible with nushell
Updated
8 months ago
Comments count
4
Export command generators
Updated
8 months ago
Comments count
1
Introduce `-w` global flag for running commands in workspaces
Updated
9 months ago
Comments count
1
EPERM: operation not permitted
Updated
9 months ago
Comments count
1
Should probably run `corepack` to avoid installing package manager globally
Updated
9 months ago
Comments count
1
the node version is 14.17.6
Closed
9 months ago
Comments count
2
Error on node16 when using the latest version 0.21.9
Closed
10 months ago
Comments count
5
Global installation of detected `yarn@>1` and `pnpm@<7` is broken
Closed
10 months ago
Comments count
1
If configured a global agent in `~/.nirc` and run `ni -g` inside a workspace, the global agent became `npm`.
Closed
10 months ago
Comments count
1
Error when I use ni
Closed
10 months ago
Comments count
3
Crash on first install
Closed
10 months ago
Is globalAgent always use npm when run 'ni -g xxx' in project workspace?
Closed
10 months ago
Comments count
1
New installation method that does not rely on NPM, can be installed and upgraded independently.
Closed
10 months ago
Comments count
2
Enhancement for non-interactive use cases
Closed
a year ago
Comments count
4
Release a docker image especially for the CI situation
Closed
a year ago
Comments count
2
Command "ni" does not work in Windows 11
Closed
a year ago
Comments count
1
Support interactive updates to npm projects
Closed
a year ago
Comments count
1
Support detect node version and change to the specified node version
Closed
a year ago
Comments count
1
doesn't work with pnpm env
Closed
a year ago
Comments count
2
Incorrect handling for quoted arguments
Closed
a year ago
Consider adding "nin" command as an alias to "ni"
Closed
a year ago
Comments count
1
how to upgrade package manager itself
Closed
a year ago
Comments count
4
Prompt the user if it is not currently a valid node project
Closed
a year ago
Comments count
1
Adding support for Bit workspace
Updated
a year ago
Comments count
2
Make it smart/compatible with rushjs
Closed
a year ago
Comments count
1
关于 `Trouble shooting` 修复 window PowerShell 冲突的脚本
Updated
a year ago
Comments count
1
About `nix` - really reconsider renaming it
Closed
a year ago
Comments count
5
When `nr` is run concurrently, `nr` may not work
Closed
a year ago
Comments count
1
Suggestion: please make the command name compatible with most environments.
Closed
a year ago
Comments count
2
Ban likely-to-be-a-typo packages from being installed by `ni`
Closed
2 years ago
Comments count
1
the command not found after updated macos
Closed
2 years ago
Comments count
2
nr stop working in wsl
Closed
2 years ago
Comments count
2
ni should not assume I want to create new project always
Closed
2 years ago
Comments count
3
nx alias conflict with nx workspaces
Closed
2 years ago
Comments count
4
Feature request: Strip unneeded `--` added by user by mistake when using nr
Closed
2 years ago
Comments count
2
Bug: ni 's package is wrong
Closed
2 years ago
Comments count
4
Conflict with the `New-Item` command of powershell 7
Closed
2 years ago
Previous
Next