I don’t think it’s very constructive to give “feedback” in the way you’re giving it.
That said: There is a lot of history around why yarn.lock is not included on GitHub, which you may want to explore if you’re interested. Including it wouldn’t solve the issue at hand. The issue is with a specific way Yarn resolves node modules (plug and play) which is far superior to the “node modules folder” which would duplicate the dependencies for each exercise. This isn’t unique to JavaScript and TypeScript, but there are also other languages such as Ruby that use a central-ish repository.
Things aren’t always broken in JavaScript, but one particular tiny thing is: eslint doesn’t understand the resolution of packages if it’s not in node modules. They have been working on a fix but it’s not released. A package from the community is supposed to resolve this but I have not yet gotten it to work the way we want it to.
Finally, the entire platform’s content, so anything apart from the core bits (the website editor etc.) is built by and maintained by volunteers. Unfortunately I currently have stage four lymphoma and am paralysed from the hips down. I won’t be able to fix this issue any time soon as I’m trying to stay alive instead. Perhaps you could direct your energy to resolve the issue yourself.
