Takeaways:

1. You should check for null values

Issue titles tagged with the intent “Uncaught TypeError”

The first intent we find is Uncaught TypeError, which is a well-known issue by the JavaScript community. We can see that most of the documents are talking about the same kind of errors, like: Uncaught TypeError: Cannot read property 'name' of null. Maybe Typescript is not such a bad idea after all.

2. Handling inputs is more difficult than expected

You had 2 jobs

The pattern of asking how to correctly handle forms is something that we will also see repeated in all of these frameworks. Issues related with validation, events firing when they shouldn’t (or should), are on the list. In fact, each one of the frameworks have their own guide on how to work with forms: Angular, React, and Vue.

3. People definitely ask for features

A quick search for feature request on the Angular repo reveals that almost 5k from their total of 15k issues are relevant for that query. This is also present in React (~20%) but not so much in Vue (~10%).

4. No one said that importing modules was easy

Easy peasy?

There are hundreds of issues out there that begin in the same way: Cannot find module. You know things may go wrong when you are not able to find the https module.

5. Things don’t work as expected when changing the NODE_ENV

React elements should be treated as immutable

It’s kind of the Works on my machine for JavaScript. We have seen issues related with the development and production mode. There is also another bunch that mention the strict mode, which is not related with the Node environment, but is semantically close.