6 ms·
@OhSoHumble: Second Point: "A couple weeks back I tried to give WSL a try but everything was broken" Did you run an Insider build? 14986 completed a batch of
by bitcrazed 10y ago
@OhSoHumble: Second Point:
"A couple weeks back I tried to give WSL a try but everything was broken"
Did you run an Insider build? 14986 completed a batch of inotify related syscall improvements since we first added inotify support in 14328 (Details here: https://msdn.microsoft.com/commandline/wsl/release_notes https://msdn.microsoft.com/commandline/wsl/release_notes)
- OhSoHumble 10y agoMy main project is a Rails/Ember.js application to help people find affordable housing in the bay area. My problem was that the CLI built to help glue the two together didn't work on Windows so I tried it out in the WSL. Because of missing inotify support, hot reloading was broken. I found that I really missed that functionality so I moved to the fast ring of insider builds. After an update, node was completely broken. I didn't know how to switch to the slow ring to get a build that may have worked so I switched to developing to the Arch install I have on another drive.
- bitcrazed 10y agoWhat OS build & Linux version are you running? Type `ver` at the Cmd prompt, and `lsb_release -a` at the Bash prompt. What do you mean when you say your node is "broken"? And I don't follow re. your Arch install on another drive?