chore: update manifests, actions and docs

Author: amaanq

.eslintrc.js

@@ -0,0 +1,20 @@
+module.exports = {
+  'env': {
+    'commonjs': true,
+    'es2021': true,
+  },
+  'extends': 'google',
+  'overrides': [
+  ],
+  'parserOptions': {
+    'ecmaVersion': 'latest',
+    'sourceType': 'module',
+  },
+  'rules': {
+    'indent': ['error', 2, {'SwitchCase': 1}],
+    'max-len': [
+      'error',
+      {'code': 120, 'ignoreComments': true, 'ignoreUrls': true, 'ignoreStrings': true},
+    ],
+  },
+};

.gitattributes

@@ -1,5 +1,20 @@
-parser.c linguist-vendored
-parser.h linguist-vendored
-grammar.json linguist-vendored
-tsx/examples/* linguist-vendored
-typescript/examples/* linguist-vendored
+typescript/src/** linguist-vendored
+tsx/src/** linguist-vendored
+
+/examples/* linguist-vendored
+
+typescript/src/grammar.json linguist-generated
+typescript/src/node-types.json linguist-generated
+typescript/src/parser.c linguist-generated
+
+tsx/src/grammar.json linguist-generated
+tsx/src/node-types.json linguist-generated
+tsx/src/parser.c linguist-generated
+
+typescript/src/grammar.json -diff
+typescript/src/node-types.json -diff
+typescript/src/parser.c -diff
+
+tsx/src/grammar.json -diff
+tsx/src/node-types.json -diff
+tsx/src/parser.c -diff

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,59 @@
+name: Bug Report
+description: File a bug or issue
+title: "bug: "
+labels: [bug]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        **Before** reporting an issue, make sure to search [existing issues](https://github.com/tree-sitter/tree-sitter-typescript/issues). Usage questions such as ***"How do I...?"*** either belong in [Discussions](https://github.com/tree-sitter/tree-sitter/discussions) upstream or in our [Discord server](https://discord.gg/w7nTvsVJhm) and will be closed.
+        If your issue is related to a bug in your editor-experience because your editor *leverages* tree-sitter and this parser, then it is likely your issue does *NOT* belong here and belongs in the relevant editor's repository.
+  - type: checkboxes
+    attributes:
+      label: Did you check existing issues?
+      description: Make sure you've checked all of the below before submitting an issue
+      options:
+        - label: I have read all the [tree-sitter docs](https://tree-sitter.github.io/tree-sitter/using-parsers) if it relates to using the parser
+          required: false
+        - label: I have searched the existing issues of tree-sitter-typescript
+          required: true
+  - type: input
+    attributes:
+      label: "Tree-Sitter CLI Version, if relevant (output of `tree-sitter --version`)"
+      placeholder: "tree-sitter 0.20.8 (6bbb50bef8249e6460e7d69e42cc8146622fa4fd)"
+    validations:
+      required: false
+  - type: textarea
+    attributes:
+      label: Describe the bug
+      description: A clear and concise description of what the bug is. Please include any related errors you see such as parsing errors or tree-sitter cli errors.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Steps To Reproduce/Bad Parse Tree
+      description: Steps to reproduce the behavior. If you have a bad parse tree, please include it here. You can get this by running `tree-sitter parse <path-to-file>` and copying the output.
+      placeholder: |
+        1.
+        2.
+        3.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Expected Behavior/Parse Tree
+      description: A concise description of what you expected to happen, or in the case of a bad parse tree, the expected parse tree.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Repro
+      description: Minimal code to reproduce this issue. Ideally this should be reproducible with the C library or the tree-sitter cli, do not suggest an editor or external tool. Also, a link to the TypeScript Playground showing that the snippet below is valid JavaScript or TypeScript would be great (https://www.typescriptlang.org/play)
+      value: |
+        // Example code that causes the issue
+        function foo() {
+          // Code that fails to parse, or causes an error
+        }
+      render: TypeScript
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1 @@
+blank_issues_enabled: false

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,36 @@
+name: Feature Request
+description: Suggest a new feature
+title: "feature: "
+labels: [enhancement]
+body:
+  - type: checkboxes
+    attributes:
+      label: Did you check the tree-sitter docs?
+      description: Make sure you read all the docs before submitting a feature request
+      options:
+        - label: I have read all the [tree-sitter docs](https://tree-sitter.github.io/tree-sitter/using-parsers) if it relates to using the parser
+          required: false
+  - type: textarea
+    validations:
+      required: true
+    attributes:
+      label: Is your feature request related to a problem? Please describe.
+      description: A clear and concise description of what the problem is. Ex. I think the grammar models this rule incorrectly and can be improved, or the TypeScript spec has officially added a new feature that should be added to the grammar.
+  - type: textarea
+    validations:
+      required: true
+    attributes:
+      label: Describe the solution you'd like
+      description: A clear and concise description of what you want to happen.
+  - type: textarea
+    validations:
+      required: true
+    attributes:
+      label: Describe alternatives you've considered
+      description: A clear and concise description of any alternative solutions or features you've considered.
+  - type: textarea
+    validations:
+      required: false
+    attributes:
+      label: Additional context
+      description: Add any other context or screenshots about the feature request here. If your feature request is related to a new TypeScript feature, please include a link to the relevant **official** TypeScript documentation.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -1,6 +1,5 @@
+# Checklist
 
-
-Checklist:
 - [ ] All tests pass in CI.
 - [ ] There are sufficient tests for the new fix/feature.
 - [ ] Grammar rules have not been renamed unless absolutely necessary.

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,30 @@
+name: CI
+on:
+  workflow_dispatch:
+  pull_request:
+  push:
+
+jobs:
+  test:
+    runs-on: ${{ matrix.os }}
+    strategy:
+      fail-fast: true
+      matrix:
+        os: [macos-latest, ubuntu-latest]
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-node@v4
+        with:
+          node-version: 18
+      - run: npm install
+      - run: npm test
+
+  test_windows:
+    runs-on: windows-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-node@v4
+        with:
+          node-version: 18
+      - run: npm install
+      - run: npm run test-windows