jwkvam / jupyterlab-vim

:neckbeard: Vim notebook cell bindings for JupyterLab
MIT License
975 stars 73 forks source link

Trouble with development install on Windows 10 #68

Closed llinfeng closed 6 years ago

llinfeng commented 6 years ago

I cloned the repo and tried to issue the first command for development install, and here goes the error message that I see:

USER MINGW64 /d/Git_Warehouse/jupyterlab-vim (master)
$ jlpm install
yarn install v1.9.4
[1/4] Resolving packages...
success Already up-to-date.
$ npm run build

> jupyterlab_vim@0.10.0 build D:\Git_Warehouse\jupyterlab-vim
> tsc

src/index.ts(214,38): error TS2459: Type 'NotebookPanel' has no property 'notebook' and no string index signature.
src/index.ts(216,29): error TS2339: Property 'notebook' does not exist on type 'NotebookPanel'.
src/index.ts(227,38): error TS2459: Type 'NotebookPanel' has no property 'notebook' and no string index signature.
src/index.ts(229,29): error TS2339: Property 'notebook' does not exist on type 'NotebookPanel'.
src/index.ts(240,29): error TS2459: Type 'NotebookPanel' has no property 'notebook' and no string index signature.
src/index.ts(253,29): error TS2459: Type 'NotebookPanel' has no property 'notebook' and no string index signature.
src/index.ts(266,29): error TS2459: Type 'NotebookPanel' has no property 'notebook' and no string index signature.
src/index.ts(279,29): error TS2459: Type 'NotebookPanel' has no property 'notebook' and no string index signature.
src/index.ts(281,29): error TS2339: Property 'notebook' does not exist on type 'NotebookPanel'.
src/index.ts(292,29): error TS2459: Type 'NotebookPanel' has no property 'notebook' and no string index signature.
src/index.ts(305,33): error TS2339: Property 'notebook' does not exist on type 'NotebookPanel'.
src/index.ts(306,34): error TS2339: Property 'notebook' does not exist on type 'NotebookPanel'.
src/index.ts(308,64): error TS2339: Property 'notebook' does not exist on type 'NotebookPanel'.
src/index.ts(319,33): error TS2339: Property 'notebook' does not exist on type 'NotebookPanel'.
src/index.ts(320,34): error TS2339: Property 'notebook' does not exist on type 'NotebookPanel'.
src/index.ts(322,64): error TS2339: Property 'notebook' does not exist on type 'NotebookPanel'.
src/index.ts(333,29): error TS2339: Property 'notebook' does not exist on type 'NotebookPanel'.
src/index.ts(334,29): error TS2339: Property 'notebook' does not exist on type 'NotebookPanel'.
src/index.ts(336,33): error TS2339: Property 'notebook' does not exist on type 'NotebookPanel'.
src/index.ts(337,33): error TS2339: Property 'notebook' does not exist on type 'NotebookPanel'.
src/index.ts(349,29): error TS2339: Property 'notebook' does not exist on type 'NotebookPanel'.
src/index.ts(349,64): error TS2339: Property 'notebook' does not exist on type 'NotebookPanel'.
src/index.ts(350,29): error TS2339: Property 'notebook' does not exist on type 'NotebookPanel'.
src/index.ts(352,33): error TS2339: Property 'notebook' does not exist on type 'NotebookPanel'.
src/index.ts(353,33): error TS2339: Property 'notebook' does not exist on type 'NotebookPanel'.
src/index.ts(365,38): error TS2339: Property 'notebook' does not exist on type 'NotebookPanel'.
src/index.ts(366,29): error TS2339: Property 'notebook' does not exist on type 'NotebookPanel'.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! jupyterlab_vim@0.10.0 build: `tsc`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the jupyterlab_vim@0.10.0 build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\llinfeng\AppData\Roaming\npm-cache\_logs\2018-10-16T20_00_20_567Z-debug.log

error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

Failed attempts

I have tried to install node.js though its Windows installer; and have tried to call the nodejs installed through Anaconda. Together with the jlpm command, all three attempts yielded the same error.

On more question: is there an easier way to set customized mappings?

In reference to issue #17, I was happy to have implemented a few mappings of mine in this fork. However, it has been challenging to replicate per my recent OS-rebuild. Please advise if this is worth a new issue to discuss.

llinfeng commented 6 years ago

I found a funny way to have WSL run jupyter lab through a "Windows native browser", and I am still stuck with adding the following two mappings to the jupyter lab on my WSL subsystem.

Here goes the error messages that I got when trying to issue the third step of "installing the development version" (jupyter labextension link .) trying_to_build

Solution that I am trying:

Implicitly, the new commit mentioned some phrases jlab 0.35..., and I am attempting to get this newer version of Jupyterlab all together. Relevant commands are:

llinfeng commented 6 years ago

Updated solution

Using the WSL subsystem on Windows, I managed to build a local customized version after updating the JupyterLab version to 0.35.1. I used conda, and here goes the set of commands:

conda install -c conda-forge jupyterlab=0.35.1
jlpm install
jlpm run build
jupyter labextension link .

The local build will run as of 2018-10-17, and no restarting is needed: within the same bash session, firing jupyter lab will have the new add-on loaded.