more updates

Author: aspeddro

Diff for: .vscodeignore

@@ -9,6 +9,7 @@ server/node_modules/.bin
 node_modules/.bin
 analysis/
 tools/
+scripts/
 dune-project
 analysis.opam
 tools.opam

Diff for: CHANGELOG.md

@@ -12,6 +12,10 @@
 
 ## master
 
+#### :house: Internal
+
+- Move `rescript-tools` to OCaml code and make `analysis` an library. https://github.com/rescript-lang/rescript-vscode/pull/855
+
 ## 1.30.0
 
 #### :rocket: New Feature

Diff for: CONTRIBUTING.md

@@ -76,7 +76,7 @@ opam install ocaml-lsp-server
 
   <img width="359" alt="image" src="https://user-images.githubusercontent.com/1909539/97448639-19db0800-18ee-11eb-875a-d17cd1b141d1.png">
 
-- For the native analysis binary tests: `cd analysis && make test`.
+- For the native analysis binary tests: `make test`.
 
 ## Change the Grammar
 
@@ -105,7 +105,7 @@ We call a few binaries and it's tricky to call them properly cross-platform. Her
 
 ## General Coding Guidance
 
-- `server/` is a standalone folder that can be vendored by e.g. Vim and Sublime Text. Keep it light, don't add deps unless absolutely necessarily, and don't accidentally use a runtime dep from the top level `package.json`.
+- `server/` is a standalone LSP server. Keep it light, don't add deps unless absolutely necessarily, and don't accidentally use a runtime dep from the top level `package.json`.
 - This codebase stayed alive by not trying to babysit long-living processes. Be fast, call a binary and shut down.
 
 ## Rough Description Of How The Plugin Works
@@ -206,9 +206,8 @@ We're happy to gather more resources over time here, including more in-depth get
 _This below will automatically release the LSP package as well._
 
 1. Bump the version to an _even minor_ version number in `package.json` and `server/package.json` and their lockfiles. It's very important that it's an even minor like `1.8.0`, and not `1.7.0`. This is because even minors are reserved for actual releases, and uneven minors for pre-releases. Commit and push the version bump.
-2. Make sure @ryyppy is aware of your changes. He needs to sync them over to the vim plugin.
-3. Let CI build your version bump commit.
-4. Tag the commit with the version number (e.g. `git tag 1.6.0`) and push the tag (e.g. `git push origin 1.6.0`). Another build will trigger, which should automatically:
+2. Let CI build your version bump commit.
+3. Tag the commit with the version number (e.g. `git tag 1.6.0`) and push the tag (e.g. `git push origin 1.6.0`). Another build will trigger, which should automatically:
    - create a `rescript-vscode-<version-number>.vsix` file
    - publish that extension version to the VSCode marketplace
    - create an automatic release on GitHub