update development documentation with basedpyright-specific info

CONTRIBUTING.md

@@ -1,6 +1,5 @@
 # Contributing
 
-
 ## issues
 
 unlike the upstream pyright repo, we are very open to ideas for improvements and bug reports. if you've raised an issue on the upstream pyright repo that was closed without a solution, feel free to raise it again here.
@@ -9,15 +8,4 @@ please upvote issues you find important using the 👍 react. we don't close iss
 
 ## local development
 
-although pyright is written in typescript, we've made improvements to the developer experience for python developers who are not familiar with typescript/nodejs. you should be able to work on basedpyright without ever having to install nodejs yourself. the node installation is instead managed by a [pypi package](https://pypi.org/project/nodejs-wheel/) and installed to the project's virtualenv. the only thing you need to have installed already is python (any version from 3.8 to 3.12 should work)
-
-we recommend using vscode, as there are project configuration files in the repo that set everything up correctly (linters/formatters/debug configs, etc).
-
-1. hit `F1` > `Tasks: Run task` > `install dependencies`, or run the following command:
-   ```
-   ./pw pdm install
-   ```
-   this will install all dependencies required for the project (pyprojectx, pdm, node, typescript, etc.). all dependencies are installed locally to `./.venv` and `./node_modules` 
-2. press "Yes" when prompted by vscode to use the newly created virtualenv
-
-you can now run any node/npm commands from inside the venv.
+[see here](https://docs.basedpyright.com/#/build-debug?id=building-basedpyright)

docs/build-debug.md

@@ -1,33 +1,17 @@
-## Building Pyright
+## Building basedpyright
 
-To install the dependencies for all packages in the repo:
-1. Install [nodejs](https://nodejs.org/en/) version 16.x
-2. Open terminal window in main directory of cloned source
-3. Execute `npm run install:all` to install dependencies for projects and sub-projects
+although pyright is written in typescript, in basedpyright we've made improvements to the developer experience for python developers who are not familiar with typescript/nodejs. you should be able to work on basedpyright without ever having to install nodejs yourself. the node installation is instead managed by a [pypi package](https://pypi.org/project/nodejs-wheel/) and installed to the project's virtualenv. the only thing you need to have installed already is python (any version from 3.8 to 3.12 should work)
 
+we recommend using vscode, as there are project configuration files in the repo that set everything up correctly (linters/formatters/debug configs, etc).
 
-## Building the CLI
+1. hit `F1` > `Tasks: Run task` > `install dependencies`, or run the following command:
+   ```
+   ./pw pdm install
+   ```
+   this will install all dependencies required for the project (pyprojectx, pdm, node, typescript, etc.). all dependencies are installed locally to `./.venv` and `./node_modules` 
+2. press "Yes" when prompted by vscode to use the newly created virtualenv
 
-1. cd to the `packages/pyright` directory
-2. Execute `npm run build`
-
-Once built, you can run the command-line tool by executing the following:
-
-`node index.js`
-
-## Building the VS Code extension
-
-1. cd to the `packages/vscode-pyright` directory
-2. Execute `npm run package`
-
-The resulting package (pyright-X.Y.Z.vsix) can be found in the client directory.
-To install in VS Code, go to the extensions panel and choose “Install from VSIX...” from the menu, then select the package.
-
-
-## Running Pyright tests
-
-1. cd to the `packages/pyright-internal` directory
-2. Execute `npm run test`
+you can now run any node/npm commands from inside the venv.
 
 
 ## Debugging Pyright

docs/internals.md

@@ -2,15 +2,17 @@
 
 ## Code Structure
 
-* packages/vscode-pyright/src/extension.ts: Language Server Protocol (LSP) client entry point for VS Code extension.
-* packages/pyright-internal/typeshed-fallback/: Recent copy of Typeshed type stub files for Python stdlib
-* packages/pyright-internal/src/pyright.ts: Main entry point for command-line tool
-* packages/pyright-internal/src/server.ts: Main entry point for LSP server
-* packages/pyright-internal/src/analyzer: Modules that perform analysis passes over Python parse tree
-* packages/pyright-internal/src/common: Modules  that are common to the parser and analyzer
-* packages/pyright-internal/src/parser: Modules that perform tokenization and parsing of Python source
-* packages/pyright-internal/src/tests: Tests for the parser and analyzer
-
+* `packages/vscode-pyright/src/extension.ts`: Language Server Protocol (LSP) client entry point for VS Code extension.
+* `packages/pyright-internal/typeshed-fallback/`: Recent copy of Typeshed type stub files for Python stdlib
+* `packages/pyright-internal/src/pyright.ts`: Main entry point for command-line tool
+* `packages/pyright-internal/src/server.ts`: Main entry point for LSP server
+* `packages/pyright-internal/src/analyzer`: Modules that perform analysis passes over Python parse tree
+* `packages/pyright-internal/src/common`: Modules  that are common to the parser and analyzer
+* `packages/pyright-internal/src/parser`: Modules that perform tokenization and parsing of Python source
+* `packages/pyright-internal/src/tests`: Tests for the parser and analyzer
+* `packages/pyright`: basedpyright npm package (used internally by [the playground](http://basedpyright.com))
+* `basedpyright`: pypi package wrapper for the npm package, so that users don't need to install nodejs themselves
+* `docstubs`: stubs with [docstrings on compiled modules](https://docs.basedpyright.com/#/?id=docstrings-for-compiled-builtin-modules) (generated from `packages/pyright-internal/typeshed-fallback/` when building the pypi package)
 
 ## Core Concepts