-
Notifications
You must be signed in to change notification settings - Fork 73
failed build - using latest version which is in a failed state. #151
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
Comments
hi @rdyar, may I ask how you traced the problem? |
I had the same issue here. After rolling back to |
the error said Then checked the npm site for this module and saw it was in a failed state. |
Have the same here, going back to 1.9.3 my project works |
I've been pulling my hair out for two days because of this "Unresolved dependencies" error. If only I noticed the version bump of this plugin... dang |
Duplicate of #149 |
went to deploy a project and it failed, traced it back to this plugin which is currently in a failed state. We were pulling in the latest version so it is now pinned to the previous version in our package.json file like:
"serverless-plugin-split-stacks": "1.9.3"
The text was updated successfully, but these errors were encountered: