feat: support custom initializationOptions

[chrismwendt]

This lets consumers provide custom initializationOptions for all workspaces.

This subsumes #11 which included workarounds for go-langserver prior to sourcegraph/go-langserver#373

[codecov-io]

Codecov Report

Merging #36 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #36   +/-   ##
=======================================
  Coverage   65.18%   65.18%           
=======================================
  Files          11       11           
  Lines         293      293           
  Branches       20       20           
=======================================
  Hits          191      191           
  Misses        102      102

Impacted Files	Coverage Δ
src/index.ts	62.04% <ø> (ø)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e394a11...3d60ad3. Read the comment docs.

[chrismwendt]

@felixfbecker Do I need to bump the beta branch to trigger CI to make a release?

[felixfbecker]

yep

[sourcegraph-bot]

🎉 This PR is included in version 1.1.0-beta.2 🎉

The release is available on:

• npm package (@beta dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[chrismwendt]

1.1.0-beta.2 doesn't seem right. The latest is 2.0.0-beta.1. Is there another branch I need to update?

[felixfbecker]

That's weird indeed. Will investigate

[felixfbecker]

Filed semantic-release/semantic-release#1191

[felixfbecker]

I released 2.0.0-beta.2 manually

[chrismwendt]

Ok, thanks. I'm seeing a source map warning, not sure if it's related:

[serve] ⚠️ Could not load source file "../../src/features/feature.ts" in source map of "../node_modules/@sourcegraph/lsp-client/dist/features/feature.js".

[felixfbecker]

Well sources are not published nor inlined, but that doesn't sound related to the release issue?

[chrismwendt]

Gotcha, yeah it's not related.