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/c4703d11-d30a-40aa-a714-91ebe51011b5%40googlegroups.com.
