#Errors when building astro on a Mapped Network Drive

31 messages ยท Page 1 of 1 (latest)

scarlet hazel
#

So I was building a astro page in a project on a Mapped Network Drive (U:) in doing so, I found many errors which I was having alot of trouble fixing (3+hours). I realised after some time it was mapping files to U:\NETWORKMACHINENAME\projdir instead of U:\projdir and it was causing all of my errors, I moved the entire project from U:\ to a local drive D:\ and instantly no issues/errors and everything worked as expected. Is this normal? Should this be a bug?

tired brook
#

Windows and network drives or even folders that are synced with OneDrive or other platforms tend to have quite a few weird issues that are not limited to Astro from my experience

scarlet hazel
#

I DO NOT use Onedrive or anything of that sort, it is a networked drive on a machine in my LAN

tired brook
#

To be clear, that was simply an example

scarlet hazel
#

for sure, I just do not like Onedrive haha

#

thank you for your input however

tired brook
#

Neither did i when i used to maintain 1000s of windows systems daily ๐Ÿคฃ

scarlet hazel
#

I bet haha

tired brook
#

But yeah, Windows network drives and running software from them HEAVILY depend on the type of software being designed for that purpose... ๐Ÿ˜… there is quite a few .exe files that i ran into in the past that refused to even launch if ran directly from a network share of any sort, even if mounted by group policy ๐Ÿ˜ข

scarlet hazel
#

hmm... sad ๐Ÿ™

#

the thing is it was just a simple one page astro build, couldn't even run dev build

#

i am new to astro, but still I havn't experienced this on other types of builds

#

would it matter that it is actually a linux machine running a samba server

#

i would imagine not... but...

tired brook
#

I don't have a windows system anymore to test it myself, hopefully another user who might have an idea could try it out...

(Linux would be the last thing to cause a issue with npm/node... ๐Ÿ˜… i actually daily linux, and have very few issues with node now compared to my node on windows ๐Ÿคฃ )

#

More likely something with the way the mount is setup in windows ๐Ÿค”

scarlet hazel
#

hmmm...

tired brook
#

Maybe try converting to a NFS mount with the advanced feature tools? and converting the linux share to NFS as well

#

That should treat it more like an actual proper shared folder that should always path correctly

scarlet hazel
#

ok I shall try that. Yeah I have many linux machines these days myself, but still daily drive the windows system due to other programs I need on daily basis.

Again thank you very much for your input, I really appreciate it

#

one day I will daily drive Linux!

tired brook
#

best of both worlds if you have a system that will actually boot windows?

scarlet hazel
#

oh god id sooner move to linux lol

tired brook
#

(yeah my laptop refuses to boot windows, but i dont really mind)

scarlet hazel
#

i might try it

#

thank you

tired brook
#

Ping me if you ever build the next Winbuntu ๐Ÿ˜›

scarlet hazel
#

hahah will do haha

tired brook
#

(totally serious btw... would love that setup script too)

scarlet hazel
#

will let you know. Im just happy for your input right now (add me if you like) im down to create what I can, my time is quite limited these days but yeahh...