-
Notifications
You must be signed in to change notification settings - Fork 68
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
ServerlessError: Export 'project-name-ServerlessAliasReference' does not exist. #181
Comments
I am seeing this issue with version |
Hi guys, any update on this? I'm getting the same message with serverless 1.66.0. |
Hello folks, the problem seems to be happening with 1.67.0 as well
Any updates? |
fix is coming #186 |
Meanwhile, to avoid this error, we can downgrade the serverless version. This one works well on my side: 1.61.2 |
Same problem with 1.78.1. Has the problem been fixed? |
Still experiencing the same issue. Is there any plan on fixing this? Thanks! |
Experiencing this problem with 1.80.0. Any updates on this being fixed? |
Still persists on 2.3.0 |
User with version 2.9.0 here. This issue is still there. As this is so far beyond version 1.61.2, I kinda don't want to downgrade as suggested above. Would be great if this issue is fixed soon. Thank you. |
Any updates on this being fixed? I really needs this and I can't find an alternative or workaround. |
I can confirm this is working, one more review is pending on the PR. |
Is the fix released? Here is what I'm on: serverless v2.15.0 |
Same issue with the following: Serverless: 2.18.0 |
Quick fix can be found here |
Same issue with Serverless: 2.29 Same issue with the serverless-aws-alias-fixed package |
The only way i got this to work is to use this or you can use the following without serverless-aws-alias |
It worked for me when i used following changes: file : package.json"devDependencies": { ############################# On file : serverless.yaml...................
|
fails.
|
I am seeing the following error message when using [email protected]. This issue does not happen with prior versions.
Environment:
Looking into the changelog for 1.61.3, this commit seems to try and improve error handling, which could be causing this message to come up.
Temporary fix to this problem for anyone else running into it, is to install version 1.61.2 as a project dev dependency and use
node ./node_modules/serverless/bin/serverless deploy
instead.Please let me know if any more information can help.
The text was updated successfully, but these errors were encountered: