nodeSolidServer / nodeSolidServer/node-solid-server
Solid-test lacks an alternative on Windows.
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.8k
- Forks
- 308
- PR merge metrics
- No merged PRs in 30d
Description
I am try to run the solid server as a developer without formal CA. So I followed the Readme and tried to replace the std solid from "solid.cmd" to solid-test
"%~dp0\node.exe" "%~dp0\node_modules\solid-server\bin\solid" %*
"%~dp0\node.exe" "%~dp0\node_modules\solid-server\bin\solid-test" %*
But when I try to run solid,(I believe it should be running this solid.cmd) it will crash with below outputs:
$ solid
C:\Users\Jomu_\AppData\Roaming\npm\node_modules\solid-server\bin\solid-test:6
Disable rejectUnauthorized when starting the server
^
SyntaxError: Invalid or unexpected token
at createScript (vm.js:80:10)
at Object.runInThisContext (vm.js:139:10)
at Module._compile (module.js:617:28)
at Object.Module._extensions..js (module.js:664:10)
at Module.load (module.js:566:32)
at tryModuleLoad (module.js:506:12)
at Function.Module._load (module.js:498:3)
at Function.Module.runMain (module.js:694:10)
at startup (bootstrap_node.js:204:16)
at bootstrap_node.js:625:3
I am using the master branch, please suggest me what should I check, thanks.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read the README instructions, then reproduce the Windows failure using solid.cmd and the bin/solid-test entry point mentioned in the report. Compare how those two launchers are invoked on Windows and verify that the solid command starts without the reported syntax error while providing the no-formal-CA development behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- backend, cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 39/100