-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gulp deploy broken #3
Comments
Hey Tim, This may not actually be the full solution (I've run into a new error) but what worked for me was updating the botfiles dependency line to have Give it a go? |
So I also ran into this issue and was able to work around it by inserting the absolute path as recommended above. However post that I get to "gulp deploy" and it fails with: Error: EISDIR: illegal operation on a directory, read I've tried a number of solutions with no luck. |
when I run 'gulp deploy' I get "Could not install from "botfiles" as it does not contain a package.json file." However my ./botfiles and dist/botfiles both have package.json in them |
@kogden Sounds like you might have Also, did you run npm install before running gulp deploy? |
@Generic42 I've run into the same issue as you after using the full path to the botfiles directory instead of "file.botfiles" in my package.json file. Do you have any idea how to proceed? Would it have anything to do with the fact that a lot of the packages used are deprecated? [16:03:32] Finished 'node-mods' after 15 s |
The problem has to do with the "dist" directory. Error output:
npm ERR! enoent ENOENT: no such file or directory, open '/Users/timbray/dev/atbot/blank-lambda-bot/dist/botfiles'
npm ERR! enoent ENOENT: no such file or directory, open '/Users/timbray/dev/atbot/blank-lambda-bot/dist/botfiles'
Apologies in advance if I missed something obvious.
The text was updated successfully, but these errors were encountered: