Fuck node. Learn to get some real fucking error messages. Ain't nobody got time for that shit

If you Can't solve your problem that doesn't mean something is Sucks or Bad , Try Reading the Docs , Error Messages arw completely Obvious in Nodejs

@AliSawari hey dude, this is a safe place for ranters. We come here to let out our frustration.
And I guess you're living in lucky land. I've experienced quite a lot of node modules that spit out non specific error messages. It's frustrating and having to trial and error everything is annoying. Yes I know which module is causing the problem but why? Is it a dependency? It doesn't say. Maybe you work with node module that have better exceptions.

@fSociety
I've had seen Enough Errors
all Explained well where's the problem , Could you tell me what's the error ?

@fSociety
Define lucky land ????!!
Man all I try to is help
I know what pains you , The node modules are really a pain in the ass

@fSociety
And Since you mentioned Believe me I'm so unlucky , I live in the worst place in the world and I'm trying to keep on with it , all I do care for devs and their problems because I feel them thats all .

Maybe learn to read mate, been using node since 0.10, its error make perfect sense to me.

@RTRMS "I've never had that problem therefore it doesn't exist."
Well idgaf if you 'believe' me or not you wank.
It's attitudes like that which give devs a bad name

@fSociety what, the inability to read the error messages, no I have not, sometimes it's a bit verbose, but it's always pretty obvious what actually went wrong. Unless of course you using some other middleware that has lousy error message, but that's not exactly nodes fault no it is...

@RTRMS that's exactly what I'm bitching about dude. That if the node module doesn't have an exception built for that particular error then you'll get a non specific error message thrown. Today it was webpack last week it was something else. You may not think that it's node's problem and you may be right however other languages handle this problem a lot better

@fSociety you cannot go blaming the language, or even the platform for the issues with a specific 3rd party plugin, that's like blaming the car dealership for an accident you had while driving drunk.

It is not nodes fault that a middleware they never wrote, does not handle errors properly.

I will give you we pack, thier errors are rubbish, most annoyingly the easiest way to fix most of them is to start over, as good as it may be, it's a pain in the arse.

@RTRMS do you think that it is possible for node to be changed in a way that helps show more specific errors when the module fails to do so?