Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
You should use node's path module to prevent cross-os issues with paths (I'm assuming this was a server error).
-
@shellbug I'm assuming yes it was node path issue but shouldn't nodejs handle path when installed?
-
@shellbug I honestly don't know, it's a project I'm not part of, but two colleagues on windows are facing this issue and using PHP storm from jetbrains, while another one on macOS using vs code is not having this issue at all
-
@gitpush have they tried using vs code on windows as well? Just to make sure the problem is windows and not the ide.
-
@shellbug I'll suggest that but to be honest I don't really care I'm overloaded with tasks and have no time to trouble shoot for other devs :S
I'll send them on slack and tell them to check
Related Rants
Was just asked why a react project keeps on throwing CI error that path not found, saw the OS was windows and my reply was:
I don't dare using Nodejs/React on Windows, on *nix machine or that thing will keep on messing up
I hope I was right in my response :S
undefined
go linux or stay windows
windows (yuk!)
react
node