-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Trouble with development install on Windows 10 #68
Comments
I found a funny way to have WSL run
Here goes the error messages that I got when trying to issue the third step of "installing the development version" ( Solution that I am trying:Implicitly, the new commit mentioned some phrases
|
Upon wrestling with issue jwkvam#68, it turned out that I do need JupyterLab 0.35.1 to get the new `jupyterlab-vim` to build locally.
Updated solutionUsing the WSL subsystem on Windows, I managed to build a local customized version after updating the JupyterLab version to 0.35.1. I used
The local build will run as of 2018-10-17, and no restarting is needed: within the same bash session, firing |
Upon wrestling with issue #68, it turned out that I do need JupyterLab 0.35.1 to get the new `jupyterlab-vim` to build locally.
I cloned the repo and tried to issue the first command for development install, and here goes the error message that I see:
Failed attempts
I have tried to install
node.js
though its Windows installer; and have tried to call thenodejs
installed through Anaconda. Together with thejlpm
command, all three attempts yielded the same error.npm run build
/c/ProgramData/Anaconda3/npm run build
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.
The text was updated successfully, but these errors were encountered: