-
Notifications
You must be signed in to change notification settings - Fork 139
Error: EISDIR, read #22
Comments
Of note, it works just fine for a fresh ionic project - there must be some directory in my hierarchy that it is not expecting. Unfortunately, there are a lot of directories in my project that aren't in a stock one! Any ideas about where I can hook in to figure out which directory it's bonking on? |
Figured it out - it was a |
Hmm, as a work around you could either add this symbol link to the ignore list, or if it's content is required - copy that directory to your project. As I understand, you would like for the CLI client to detect the symbolic links and add their content to the manifest? |
My workaround was to copy it in, and that works fine (of course it's hacky, but whatever). Yes, I think the ideal behavior should be that it copies the symlinked directory, flat, into the target bundle and the manifest. That way, you can use symlinked dependencies with |
👋 Hi! Thank you for your interest in this repo. 😢 We are not using nordnet/cordova-hot-code-push-cli anymore, and we lack the manpower and the experience needed to maintain it. We are aware of the inconveniece that this may cause you. Feel free to use it as is, or create your own fork. 🔒 This will now be closed & locked. ℹ️ Please see #79 for more information. |
I'm getting this error when I try to run it.
I'm on OSX 10.11, node version
v0.10.38
(though the error also occurs with node 4.2.1). I tried to add debugging logging, stack traces, etc. but was stymied because I couldn't find the events.js file that was actually throwing the error.The text was updated successfully, but these errors were encountered: