Server not starting
See original GitHub issueDescribe the bug
I’m getting this issue last 2 days.
[ERR_REQUIRE_ESM]: require() of ES Module \node_modules\brilliant-errors\node_modules\callsites\index.js from \node_modules\brilliant-errors\dist\index.cjs not supported.
Reproduction
Vue
System Info
'envinfo' is not recognized as an internal or external command,
operable program or batch file.
Used Package Manager
npm
Validations
- Follow our Code of Conduct
- Read the Contributing Guide.
- Check that there isn’t already an issue that reports the same bug to avoid creating a duplicate.
- Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
- The provided reproduction is a minimal reproducible of the bug.
Issue Analytics
- State:
- Created 10 months ago
- Reactions:5
- Comments:6
Top Results From Across the Web
Unable to Start the Server Service - Microsoft Support
When you attempt to start the Server service from the Services tool in Control Panel, you may receive the following error message: Could...
Read more >My Server won't boot. What do I do? - Support Center
My Server won't boot. What do I do? · External Power - Check power source that it is able to actively power devices....
Read more >Dell PowerEdge: Troubleshooting a Server that does not start ...
Troubleshooting a No Boot on a Dell PowerEdge Server · Restart the system. · Press F2 during system start to enter the System...
Read more >Why Won't My Minecraft Server Start? - Apex Hosting
Your server not starting can be the result of a number of causes, in most cases, it can be resolved or at least...
Read more >[SOLVED] Help! Server won't start... - General Hardware Forum
Unplug the power supplies and then pull each power supply out and push it back in. No need to take the server apart....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This may be caused by
brilliant-errors
. See the related issue .@yankeeinlondon Thank you for your work! It seems that
v0.22.0
is not published to npm, is there any mistake?