Regenerate files, which hadn't picked up the correct version of tree-sitter-javascript

npm is still a mystery to me. I never know what to invoke to update dependencies.

In {tsx,typescript}/src/grammar.json, I looked for private_property_identifier which is a recent addition to tree-sitter-javascript. It's now present, so I assume this time I did the right thing.

Originally, I had just modified package.json by hand, followed by npm install. I suppose this is deeply wrong since the generated grammar.json still inherited from the older tree-sitter-javascript grammar.

This time, I did this:

npm install github:tree-sitter/tree-sitter-javascript#ae9bc67

followed by

npm run build
npm test

I think code generation should be automated to avoid this kind of problems.

Checklist:

[x] All tests pass in CI.
[x] There are sufficient tests for the new fix/feature.
[x] Grammar rules have not been renamed unless absolutely necessary.
[x] The conflicts section hasn't grown too much.
[x] The parser size hasn't grown too much (check the value of STATE_COUNT in src/parser.c).

tree-sitter / tree-sitter-typescript

Regenerate files, which hadn't picked up the correct version of tree-sitter-javascript #168