Node: Solving Async in Node.js

[laynef]

Is your feature request related to a problem? Please describe.
Please describe the problem you are trying to solve.

Storing async returns in a variable like Ruby on Rails:
GitHub Repo: https://github.com/laynef/SolvingCallbackHell

Node.js is very new in the backend world. The Async problem is one of the biggest problems. This is a way to get the resolve from callbacks.

git clone https://github.com/laynef/SolvingCallbackHell example
cd example
node example.js

Describe the solution you'd like
Please describe the desired behavior.

Let me know how I can help with this problem. Await is still the wrong way. If any variable type worked like this function the problem is solved and our code will read line by line synchronously.

Describe alternatives you've considered
Please describe alternative solutions or features you have considered.

Syntactical sugar is already the wrong way to change javascript as a whole. With using the v8 engine, Node.js does not have to repeat those issues because Node.js as a whole should not match javascript on the browser anyways. I'd love to see where I could be of help.

[devsnek]

the issue tracker is for bugs in node.js. there are plenty of other places online to share libraries you've made. thanks!

[laynef]

I'm not trying to solve a native problem in Node with a third party

[laynef]

The await keyword is the wrong approach

[ghost]

@laynef

I don't see any problem in Node.js. The feature request you proposed doesn't make sense to me. Callbacks already work as they should work.

Await is still the wrong way

Wrong way for what? If you don't like something about JavaScript syntax/semantics, you may want to submit a new proposal to tc39/proposals

[laynef]

Right it's a depth issue and callbacks then store it in an array. I'll check out node_modules next. I still have the best intentions

[laynef]

Add that shit to "await"

[addaleax]

@laynef As far as the issue here is concerned, a) it seems that you are advocating for a language-level feature, so Node.js is not the right place for this (as mentioned above) and b) it’s not very clear what you are actually advocating for.