Not to be a detractor, but what problem does stylifycss solve that isn't solved in almost the exact same way with other solutions? Is it just usage/approach/code-style/feel?
Aside: I'm not the one who downvoted, would welcome the input from them as well. This is an integration framework for styling JS applications, so it does fit imo.
Worth adding, a very natural use of generators would be for a CSV parser engine... Generally speaking, generators can be thought of natural streams. Async generators and for-await being extensions to this usage.
My bad for double checking forEach and not entries... working from years old memory isn't always the greatest. Like recalling IE5.0.0 and IE8 specific bugs (so glad I don't need to remember, but kind of sad as I've built up so much esoteric knowledge).
Okay, so I'm able to bring in an npm module that makes pretty heavy use of npm's tcp interfaces, which is nice to see... will probably try mssql next, if that works, I'll be very happy indeed.
This is about iterating an object... should probably also mention that if you're expecting an array, that may be null/undefined, you can use optional chaining.
myArray?.forEach(...)
As mentioned in the article, you have Object.entries. Should probably also mention Object.keys and Object.values.
IIRC Array.prototype.forEach was ES5 (not 6), while Object.entries was added with ES6/ES2017.
This is about iterating an object... should probably also mention that if you're expecting an array, that may be null/undefined, you can use optional chaining. myArray?.forEach(...) As mentioned in the article, you have Object.entries. Should probably also mention Object.keys and Object.values. IIRC Array.prototype.forEach was ES5 (not 6), while Object.entries was added with ES6/ES2017.