Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Powershell support
See original GitHub issueExpected Behavior
[REQUIRED] Describe expected behavior
npm run-script --silent build-app should not rely on unix commands as to stay cross-platform.
Describe the problem
‘rm’ is not recognized as an internal or external command, operable program or batch file.
[REQUIRED] Actual Behavior
npm run-script --silent build-app
‘rm’ is not recognized as an internal or external command,
operable program or batch file.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @openid/appauth@1.3.0 prepare: npm run-script --silent build-app
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the @openid/appauth@1.3.0 prepare script.
[REQUIRED] Steps to reproduce the behavior
clone the repository and run the script from a powershell environment.
[REQUIRED] Environment
- AppAuth-JS version: 1.3.0
- AppAuth-JS Environment (Node, Browser (UserAgent), …): Windows 10
- Source code snippts (inline or JSBin)
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:5
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
You can use WSL.
Workaround: In package.json find:
"clean": "rm -rf built"replace by:"clean": "rmdir /S /Q built"or instead use this line to be compatible with unix and windows:
"clean": "(rm -rf built || rmdir /S /Q built)"Windows users will see the rm not found error in console, but the command succeeds with the alternative command provided.