Thanks for trying it out and sharing your experience!
1- npm install logs gives exact same warnings for those dependencies for me
too. that's normal.
2- I'm not familiar with sitecustomize.py but I just googled it and found
out its about customizing python environments for different projects on a
machine. I will at some point have to give more friendly details of
installation for people using that, and/or anaconda. But everything related
to the python side of things can be tested independently of vscode and
leointeg, by simply starting the leobridgeserver.py script manually
yourself in any way you choose... (terminal, or some shell...)
3- I've never encountered this dialog saying '${file}' can not be
resolved... I'll switch to my windows machine and will come back here to
report about the current node.js version that is installed on my machine,
along with version of any other thing that might not have been taken care
of by the 'npm install' step.
In the meantime, (if you're ok with this), could you please click on the
help/about button in vscode's menu? it's got a handy 'copy' button which
you could use to then paste the results in here. That would give general
info that might be useful. For instance on my linux machine I get this
report:
Version: 1.45.1
Commit: 5763d909d5f12fe19f215cbfdd29a91c0fa9208a
Date: 2020-05-14T08:27:22.494Z
Electron: 7.2.4
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Linux x64 5.5.5-050505-generic
Thanks! I'll get back to you in a few with more relevant things or tips to
get people on windows to run this more smoothly.
Félix
On Sunday, May 31, 2020 at 6:39:48 PM UTC-4, Edward K. Ream wrote:
>
> On Friday, May 29, 2020 at 10:44:13 PM UTC-5, Félix wrote:
>
> > I just pushed a new version on the master branch of LeoInteg. ...I made
> sure it runs well under Windows this time! ;)
>
> Here are my experiences.
>
> 1. npm install reported the following:
>
> found 310 vulnerabilities (298 low, 12 high)
> run `npm audit fix` to fix them, or `npm audit` for details
>
> I didn't run npm audit fix, to keep things as they were.
>
> 2. Adding the path to the leo-editor folder did not work. Adding this to
> my sitecustomize.py did work:
>
> import sys
> leo_path = r'C:\leo.repo\leo-editor'
> if leo_path not in sys.path:
> sys.path.append(leo_path)
>
> Finally, running F5 in vs code gave an error previously. Now it asks me
> for an environment. When I select node.js I get a dialog saying '${file}'
> can not be resolved. Please open an editor.
>
> What do I do now?
>
> Edward
>
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/leo-editor/914bfce0-05f1-4d42-829e-d0d426cbf3ac%40googlegroups.com.
