Last 12 weeks · 0 commits
4 of 6 standards met
Hi, So I was getting the following error: and, after trying some things out, I finally decided to comment out the on line 31 of and replace it with a call, after doing that I could see that the cause of the error was an undefined function, so it was an application problem not a server, or configuration one. I believe the error message is misleading and that errors of this type should still resolve the promise instead of reject it. Maybe I'm missing the reason why you're checking for and calling instead of just resolving and letting the user see the error for themselves. Please let me know your thoughts on this and thank you for your time and effort 🙌.
Repository: sindresorhus/php-server. Description: Start a PHP server Stars: 138, Forks: 8. Primary language: JavaScript. Languages: JavaScript (94.5%), TypeScript (5.5%). License: MIT. Topics: development, nodejs, npm-package, php, php-server, webserver. Latest release: v3.0.0 (9mo ago). Open PRs: 0, open issues: 0. Last activity: 9mo ago. Community health: 71%. Top contributors: sindresorhus, Richienb.