I noticed that when I was trying to initialize Astrum that I couldn't run it within a different folder I was changed into (e.g. - ~/folder-name/pattern-library). I would be getting the EACCES: permission denied error.
But when I would run astrum init ./folder-name/pattern-library (as stated in the docs) it works fine but I need to be backed out to the root directory for that to work.
Is this because Astrum doesn't have R/W access to the other directories from the get go? Just wondering if it's something I'm missing or if that's the intended result.
Tell us about the issue you are experiencing
I noticed that when I was trying to initialize Astrum that I couldn't run it within a different folder I was changed into (e.g. -
~/folder-name/pattern-library
). I would be getting theEACCES: permission denied
error.But when I would run
astrum init ./folder-name/pattern-library
(as stated in the docs) it works fine but I need to be backed out to the root directory for that to work.Is this because Astrum doesn't have R/W access to the other directories from the get go? Just wondering if it's something I'm missing or if that's the intended result.
What behaviour would you expect?
How can this issue be replicated?
Screenshots / Screencast
Your environment
Platform: MacOS OS Version: Mojave Node Version: 11.1.0 NPM Version: 6.4.1 Astrum Version: 1.9.5