serverless-aws-alias: ServerlessError: Export 'project-name-ServerlessAliasReference' does not exist.

I am seeing the following error message when using serverless@1.61.3. This issue does not happen with prior versions.

Serverless: [AWS cloudformation 400 0.279s 0 retries] listImports({ ExportName: 'project-name-ServerlessAliasReference' })

Serverless Error ---------------------------------------

ServerlessError: Export 'project-name-ServerlessAliasReference' does not exist.
    at promise.catch.err (C:\Users\user\AppData\Roaming\npm\node_modules\serverless\lib\plugins\aws\provider\awsProvider.js:329:27)
    at process._tickCallback (internal/process/next_tick.js:68:7)

Environment:

Your Environment Information ---------------------------
     Operating System:          win32
     Node Version:              10.16.0
     Framework Version:         1.61.3
     Plugin Version:            3.2.7
     SDK Version:               2.3.0
     Components Core Version:   1.1.2
     Components CLI Version:    1.4.0

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.

About this issue

Original URL
State: open
Created 4 years ago
Reactions: 27
Comments: 19 (2 by maintainers)

Most upvoted comments

fix is coming https://github.com/serverless-heaven/serverless-aws-alias/pull/186

+16

Enase on Mar 25, 2020

I am seeing this issue with version 1.62 as well. Downgrading to serverless version 1.61.2 solves the problem . But it would be good to have this fixed in the latest version so we don’t have to keep pinning on version 1.61.2.

+13

shintasmith on Jan 31, 2020

Experiencing this problem with 1.80.0. Any updates on this being fixed?

+11

PaulKleinschmidt on Aug 27, 2020

Still persists on 2.3.0

dobeerman7 on Oct 13, 2020

Hi guys, any update on this? I’m getting the same message with serverless 1.66.0.

raymercb on Mar 10, 2020

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.

tanmay-kulkarni on Nov 2, 2020

Any updates on this being fixed? I really needs this and I can’t find an alternative or workaround.

eliyasmeth on Nov 12, 2020

Hello folks, the problem seems to be happening with 1.67.0 as well

Framework Core: 1.67.0 Plugin: 3.5.0 SDK: 2.3.0 Components: 2.22.3

Any updates?

victoraldir on Mar 22, 2020

Meanwhile, to avoid this error, we can downgrade the serverless version. This one works well on my side: 1.61.2

raymercb on Apr 27, 2020