Develop Reference

yarn start-https failed with error Command failed with exit code 1

I am working on a project that I downloaded, but having trouble setting up and getting the enviroment started.
After yarn install, yarn build, and then yarn start-https, I get this error message:
Error: error:0909006C:PEM routines:get_name:no start line
at node:internal/tls/secure-context:65:13
at Array.forEach (<anonymous>)
at setCerts (node:internal/tls/secure-context:63:3)
at configSecureContext (node:internal/tls/secure-context:152:5)
at Object.createSecureContext (node:_tls_common:116:3)
at Server.setSecureContext (node:_tls_wrap:1344:27)
at Server (node:_tls_wrap:1203:8)
at new Server (node:https:69:3)
at Object.createServer (node:https:105:10)
at Server.createServer (.../node_modules/webpack-dev-server/lib/Server.js:677:35)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
I am have followed the set for the readMe file... and I tried googling each line of error message but nothing had helped solved this issue of exiting out.
I feel, that I must be missing something... somthing that was not documented in the readme file...
Any help would be greatly appreciated.

I think you need to check your package.json file and especially the script file
if you share more references of your start file it will grate to understand more
happy to help you

This error showing that you have a problem around ssl settings, you have to prepare self-signed SSL Certificate.

ECONNRESET while installing Angular CLI with npm

While trying to install Angular CLI on a machine with no proxy set and flawless internet I get a following error:
4727 silly extract micromatch#^3.1.4 extracted to C:\Users\User\AppData
\Roaming\npm\node_modules\.staging\micromatch-7d604bf4 (38763ms)
4728 timing action:extract Completed in 265532ms
4729 verbose unlock done using C:\Users\User\AppData\Roaming\npm-cache\_locks\staging-eb8de851d6fef93d.lock for C:\Users\User\AppData\Roaming\npm\node_modules\.staging
4730 timing stage:rollbackFailedOptional Completed in 0ms
4731 timing stage:runTopLevelLifecycles Completed in 277531ms
4732 verbose type system
4733 verbose stack FetchError: request to https://registry.npmjs.org/mime-types/-/mime-types-2.1.18.tgz failed, reason: read ECONNRESET
4733 verbose stack at ClientRequest.req.on.err
[...]
4739 error code ECONNRESET
4740 error errno ECONNRESET
4741 error network request to https://registry.npmjs.org/mime-types/-/mime-types-2.1.18.tgz failed, reason: read ECONNRESET
4742 error network This is a problem related to network connectivity.
4742 error network In most cases you are behind a proxy or have bad network settings.
4742 error network
4742 error network If you are behind a proxy, please make sure that the
4742 error network 'proxy' config is set properly. See: 'npm help config'
4743 verbose exit [ 1, true ]
It usually fails on extracting rxjs package. So far I've tried:
Setting registry to a http:// version, but then it fails earlier, every time on is-number package
reinstalling and updating npm/node
clearing the cache after every single operation
disabling the windows firewall
starting the command line with administrator rights
checked that proxy config is null
Nothing seems to be working. Do you have any ideas?
Edit: Maybe this will help, but when I've tried to update npm itself, it would hang itself immediately on rollbackFailedOptional, it managed to update itself only after changing the registry to the http:// version

Downgrade towards a more stable version of node/npm.
To install a specific version of npm, e.g, 5.6.0:
npm install -g npm#5.6.0

meteor fails to start server in events.js with write EOF exception

When I try to start a meteor project I always get this error message (on my machine only, the project is working fine on my colleague's machines):
=> Started proxy.
=> Started MongoDB.
events.js:141
throw er; // Unhandled 'error' event
^
Error: write EOF
at exports._errnoException (util.js:907:11)
at WriteWrap.afterWrite (net.js:785:14)
Sometimes the error already shows up before mongo is stared.
In fact, I cannot start any project anymore ... :-(
It seems that I have a serious problem with my meteor installation.
I tried re-installing meteor, but no effect.
meteor reset --> no effect
Could it be a problem with a downloaded package? Where does meteor store the packages?
I really would appreaiate any hint what I can try to make it work again.
I'm using meteor on windows.

Node-Inspector unable to open chrome browser throwing Error ENOENT

I would like to know why am I getting the following error when I try to debug node app using node inspector.
Debugger listening on port 5858
events.js:154
throw er; //unhandled 'error' event
Error: spawn C:\Users\Dell\AppData\Local\Google\Chrome\Application\Chrome.exe ENOENT
at exports._errnoException (util.js:890:11)
at Process.ChildProcess._handle.inexit(internal/child_process.js:182:32)
at onErrorNT (internal/child_process.js:348:16)
at _combinedTickCallback (node.js:383:13)
at process._tickCallback (node.js:407:11)
I believe this error was similar to the error reported at https://github.com/node-inspector/node-inspector/issues/732. But however I didn't get as new_chrome.exe.
Any help is appreciated
node version is 5.9.1
node debug version is 0.12.7
EDIT: Actually the problem is chrome.exe file is inside "Program Files(86)" , but while running node-debug it is searching in user folder. So it is something to do with node-module browser-launcher When I run detect.js, in browser-launcher2/examples , its returning me the correct chrome.exe path, but when I run launch.js, it is returning me the above error, since it was trying to find chrome.exe inside user folder. Any thoughts on this?
UPDATE: Added the temporary solution. It worked for me.
NOTE: This is a temporary solution. I am keeping this question open, so as to get a permanent solution for this error. Happy coding :)

I solved the above issue temporarily using James-Browser-Launcher module. Just install the module and run examples/launch.js in the terminal. Once launched, your default browser would open. Now run
node-debug
it launched the browser without error for me. Thats it. It would work now. Hope it works for you too

This works for me:
Go to C:\Users\youruser\ .config\browser-launcher2
open config.json
If there are more than two instances of Chrome, uninstall the error instance first and delete the error entry at file and his associated folder in this path. In my case, the error was Chrome Canary :
Example
And then, node-inspector works with Standar Chrome!!!

Meteor reset not working in vagrant

I'm trying to get meteor reset to work in vagrant box. However I kept getting errors. This is my error message:
/home/vagrant/.meteor/packages/meteor-tool/.1.1.10.8ogiso++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/lib/node_modules/fibers/future.js:278
throw(ex);
^ Error: EBUSY, rmdir '/vagrant/foosboom-meteor/.meteor/local'
at Object.Future.wait (/home/vagrant/.meteor/packages/meteor-tool/.1.1.10.8ogiso++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/lib/node_modules/fibers/future.js:398:15)
at Object.rm_recursive (/tools/fs/files.js:270:9)
at Command.main.registerCommand.name [as func] (/tools/cli/commands.js:1211:9)
at /tools/cli/main.js:1378:23
I'm using hashicorp Otto as my development environment.
I have performed a mount on the local folder as suggested by one of the user here.
Any idea what seems to be the problem? Thanks.

After mounting you can't reset your mongo so do this
sudo umount -f /vagrant/foosboom-meteor/.meteor/local