As others have explained, the “black hole” is because throwing inside a .catch continues the chain with a rejected promise, and you have no more catches, leading to an unterminated chain, which swallows errors (bad!) Add one more catch to see what’s happening: do1().then(do2).catch(function(err) { //console.log(err.stack); // This is the only way to see the … Read more
Yes, throwing an exception from the failed constructor is the standard way of doing this. Read this FAQ about Handling a constructor that fails for more information. Having a init() method will also work, but everybody who creates the object of mutex has to remember that init() has to be called. I feel it goes … Read more
The difference between ‘throw new Error’ and ‘throw someObject’ in javascript is that throw new Error wraps the error passed to it in the following format − { name: ‘Error’, message: ‘String you pass in the constructor’ } The throw someObject will throw the object as is and will not allow any further code execution … Read more