add lerna, metapackage, integrity checks, and move src (76 1️⃣ )

[bollwyvl]

For #76, continuing on #77, this does the Big Move of src and starts setting up the tooling for further work. It may or may not be appropriate to squash merge this: i tried to be concise but ended up creating a few more commits than I would have liked, but it's still reasonable to start working on step 2.

• Moves src into a new sub-package
• as few other changes as i could manage
• creates new, unpublished "dev-only" root package
  • move all the test-time language servers here
  • move most scripts (not test) here
• adds new, unpublished metapackage
  • includes references in tsconfig to jupyterlab-lsp
    • keeping these versions in-line is a bit of a chore, and should probably be managed with an integrity script a la lab
• changes the lab build strategy for ci (pack, install, build) vs binder (link, install, build)
  • this will likely have to change some as we introduce packages that aren't labextensions
• add integrity script to check metapackage versions and refs (also other things)
• update docs

[jupyterlab-dev-mode]

Thanks for making a pull request to JupyterLab!

To try out this branch on binder, follow this link:

[bollwyvl]

Boo, need to chomp the line break on the variables in the yaml...

[bollwyvl]

Huzzah, mostly-working pass. Despite my desire to keep this a manageable review, the metapackage demanded that I start thinking more about the integrity stuff, so I've gone ahead and added that to CI... still want to do some stuff on here, will start a punchlist above.

[bollwyvl]

I had another go through the docs... given there is just the one "real" package and the metapackage, there isn't a lot to say that's new, but I did catch (and add a test for) the version of the package listed in /README.md. If this goes green, it's probably ready for review...

[bollwyvl]

Yep, probably done on this for the time being. No rush to review. I'll check out #78 and see if there's a way to do server discovery that makes sense.

[krassowski]

Well, the point here was to demonstrate the RC installation. It's a pity I rushed through with soft release, though I do not feel that we need this integrity check for this part - other than this example, we do not need the version in the README. Though I am also happy for it to stay - as-is.

[bollwyvl]

Either way! Sometimes it's great to have the version in the readme, others, more so much...

…

On Wed, Oct 30, 2019, 16:52 M. Krassowski ***@***.***> wrote: ***@***.**** commented on this pull request. ------------------------------ In README.md <https://github.com/krassowski/jupyterlab-lsp/pull/79#discussion_r340852028> : > @@ -120,7 +120,7 @@ jupyter labextension update @krassowski/jupyterlab-lsp Use install command (update does not seem to work) appending ***@***.***` to the extension name, like this: ```bash -jupyter labextension install @***@***.*** Well, the point here was to demonstrate the RC installation. It's a pity I rushed through with soft release, though I do not feel that we need this integrity check for this part - other than this example, we do not need the version in the README. Though I am also happy for it to stay - as-is. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <https://github.com/krassowski/jupyterlab-lsp/pull/79?email_source=notifications&email_token=AAALCRC6L2CZIOPPN3NXJI3QRHXZFA5CNFSM4JFZDSDKYY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOCJZM3SQ#pullrequestreview-309513674>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAALCRAGMLUPSDF7EKIRQ7DQRHXZFANCNFSM4JFZDSDA> .