Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / cspotcode/npm-pwsh issues and pull requests
#26 - Global Install fails in node:lts container
Issue -
State: open - Opened by cdhunt almost 4 years ago
#25 - switch to @zkochan/cmd-shim
Pull Request -
State: open - Opened by cspotcode over 4 years ago
#24 - Support cross-drive installation (pwsh extracted to one drive, local npm project on another)
Issue -
State: open - Opened by cspotcode over 4 years ago
Labels: help wanted, good first issue
#23 - Add new pwsh versions
Pull Request -
State: closed - Opened by cspotcode over 4 years ago
#22 - Cannot install PWSH on Heroku Node.js dyno
Issue -
State: open - Opened by markb-trustifi over 4 years ago
- 4 comments
Labels: help wanted
#21 - Changes to publishing workflow
Pull Request -
State: closed - Opened by cspotcode over 4 years ago
#20 - pester->mocha, travis->githubactions
Pull Request -
State: closed - Opened by cspotcode over 4 years ago
#19 - the pwsh dependency cannot be used in Azure Pipeline on Windows hosts
Issue -
State: closed - Opened by Josverl over 5 years ago
- 2 comments
#18 - Pwsh.exe path linking fails if package directory is on a different disk to home directory
Issue -
State: closed - Opened by anthony-c-martin over 5 years ago
- 9 comments
#17 - preview releases as `pwsh-preview` instead of `pwsh`
Issue -
State: open - Opened by cspotcode over 6 years ago
Labels: good first issue
#16 - Implement pwsh-np that does not load profile
Issue -
State: open - Opened by cspotcode over 6 years ago
#15 - Changed to 'pwsh'
Pull Request -
State: closed - Opened by fearthecowboy over 6 years ago
- 2 comments
#14 - Doesn't work with pnpm package manager
Issue -
State: closed - Opened by fearthecowboy over 6 years ago
- 10 comments
#13 - Why not call this package 'pwsh' ?
Issue -
State: closed - Opened by fearthecowboy over 6 years ago
- 5 comments
#12 - Fix check for installed binary on windows
Pull Request -
State: closed - Opened by fearthecowboy over 6 years ago
- 1 comment
#11 - If an instance of pwsh is open in another window, installation fails [Windows]
Issue -
State: closed - Opened by fearthecowboy over 6 years ago
- 3 comments
#10 - Idea: have a single user-local install of the actual binary
Issue -
State: closed - Opened by fearthecowboy over 6 years ago
- 3 comments
#9 - Install Miscalculated pwsh.exe location on global install
Issue -
State: closed - Opened by fearthecowboy over 6 years ago
- 14 comments
#8 - Document PowerShell dependencies
Issue -
State: closed - Opened by cspotcode over 6 years ago
- 3 comments
#7 - Fix `npm install` failure for development
Issue -
State: closed - Opened by cspotcode over 6 years ago
#6 - spawnSync npm fails on Windows because it's `npm.cmd`
Issue -
State: closed - Opened by cspotcode over 6 years ago
- 1 comment
#5 - Trying to `npm uninstall` throws error because `.bin/pwsh` symlink points to a file outside of npm's control
Issue -
State: closed - Opened by cspotcode over 6 years ago
- 2 comments
#4 - Force install?
Issue -
State: closed - Opened by cspotcode over 7 years ago
- 1 comment
#3 - Install PowerShell core on Windows?
Issue -
State: closed - Opened by cspotcode over 7 years ago
- 1 comment
#2 - Mac support
Issue -
State: closed - Opened by cspotcode over 7 years ago
- 2 comments
#1 - Assumptions about location of ".bin" folder are wrong for global installation
Issue -
State: closed - Opened by cspotcode over 7 years ago
- 1 comment