Skip to content
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

Open
sorash opened this issue Jan 22, 2020 · 4 comments · May be fixed by #186
Open

ServerlessError: Export 'project-name-ServerlessAliasReference' does not exist. #181

sorash opened this issue Jan 22, 2020 · 4 comments · May be fixed by #186

Comments

@sorash
Copy link

@sorash sorash commented Jan 22, 2020

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.

@shintasmith

This comment has been minimized.

Copy link

@shintasmith shintasmith commented Jan 31, 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.

@raymercb

This comment has been minimized.

Copy link

@raymercb raymercb commented Mar 10, 2020

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

@victoraldir

This comment has been minimized.

Copy link

@victoraldir victoraldir commented Mar 22, 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?

@Enase

This comment has been minimized.

Copy link
Contributor

@Enase Enase commented Mar 25, 2020

fix is coming #186

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

5 participants
You can’t perform that action at this time.