npm run devEnvUp not working
ajohnson1031 opened this issue · 1 comments
Expected Behavior
Expect implementation reference server to start up. As of this writing, as I have not seen it in action, I cannot speak to specifics.
Actual Behavior
A soft error is spit out.
> payid@1.4.0 devEnvUp
> run-script-os
This is meant to be run from within npm script. See https://github.com/charlesguse/run-script-os
The bug is simply that the server does not start up.
Context
I would like to be able to test the Paystring functionality within an enclosed testing environment. Unfortunately, because the server has not started up, I cannot. I'm also wanting to run stress tests on the functionality for medium to enterprise level applications, however, it's a non-starter unless the server actually runs.
Potential Solution
Steps to Reproduce
- Step one
Clone the Paystring reference implementation github repo locally. - Step two
Runnpm install
to download all of the necessary dependencies. - Step three
Runnpm run devEnvUp
to start the server locally.
Environment
- Node version:
v15.4.0
- NPM version:
7.0.15
- Operating System and version:
macOS Mojave 10.14.6
- PayID server version: Public API Version: 1.1 Admin API Version: 2020-08-28
- PayID Version header (if applicable):
Screenshots
If applicable, add screenshots to help explain your problem.
Bonus
Are you willing to submit a pull request to fix this bug?
Yes, if I am told what to do.
Additional Information 1/5/21
I attempted to set up an implementation on an AWS instance, and was successful in getting everything nicely installed. However, when attempting to get it up and running, I ran into the same exact issue issue.
[ec2-user@ip-172-31-16-253 paystring]$ npm run devEnvUp
> payid@1.4.0 devEnvUp
> run-script-os
This is meant to be run from within npm script. See https://github.com/charlesguse/run-script-os
There appears to be a problem with the run-script-os
package. Linking to the issue on npmjs: charlesguse/run-script-os#38
For now, I was able to get the dev server up and running by downgrading npm to version 6.14.10 using the below command.
npm install -g npm@6.14.10
Closing issue as this is not a Paystring issue. Please track progress on the above linked repo issue page.