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.

Sign up for GitHub

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

Jump to bottom

Amplify mock function does not print console.error to terminal #6461

Closed
kldeb opened this issue Jan 22, 2021 · 2 comments
Closed

Amplify mock function does not print console.error to terminal #6461

kldeb opened this issue Jan 22, 2021 · 2 comments
Labels
bug Something isn't working functions Issues tied to the functions category mock Issues tied to the mock functionality pending-release Code has been merged but pending release

Comments

@kldeb
Copy link
Contributor

kldeb commented Jan 22, 2021

Describe the bug
When I use console.error in node function in amplify it doesn't write console.error to the terminal (fish).

Amplify CLI Version
4.41.0

To Reproduce

  • run amplify add function, follow a regular flow
  • add a console.error('this is an error') to the new function just created
  • run amplify mock function funcName

Expected behavior

  • see console errors

Desktop (please complete the following information):

  • OS: Mac
  • Node: v12.13.0

Additional context
We'd like to sort on errors in cloud watch so not using console.error is an issue
@nikhname nikhname added mock Issues tied to the mock functionality functions Issues tied to the functions category enhancement bug Something isn't working and removed enhancement labels Jan 23, 2021
@edwardfoyle edwardfoyle mentioned this issue Feb 12, 2021
Merged
@edwardfoyle edwardfoyle added the pending-release Code has been merged but pending release label Feb 12, 2021
@edwardfoyle
Copy link
Contributor

The fix for this has been released in the latest version of the CLI. Please upgrade to the latest version to try it out.

@github-actions
Copy link

This issue has been automatically locked since there hasn't been any recent activity after it was closed. Please open a new issue for related bugs.

Looking for a help forum? We recommend joining the Amplify Community Discord server *-help channels for those types of questions.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 25, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug Something isn't working functions Issues tied to the functions category mock Issues tied to the mock functionality pending-release Code has been merged but pending release
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@kldeb @nikhname @edwardfoyle