Replies: 1 comment
-
This is definately about the junctions / symlinks. I sorted out the code using workspaces and this works under wsl. But under windows the symlink that |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I've been developing an app in Windows first under WSL and now with the 1.1.3 native binary. Everything was working fine but now I've hit problems trying to refactor some code as separate npm modules. Long story short, I'd like to have a local dev setup so that some things on node_modules would be Windows directory junctions pointing to the git repo with latest version. However this quickly leads to startup errors like
When I try to replace this a local copy of the same folder, it works. Also works under WSL. But this is not 100% "junctions don't work" either, I can junction individual folders and files and have it work. Problem seems to be junctions in node_modules. My suspicion is that when searching through the node_modules, something ends up doing ".." on the path which ends up in the ".." of the physical path, not the junction. In cmd this works correctly with junctions, i.e. "cd .." takes you to folder where junction is created.
My question really is that
EDIT: Could be related to #10144
Beta Was this translation helpful? Give feedback.
All reactions