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

apex up doesnt support node 12 #820

Open
2 of 4 tasks
omar-dulaimi opened this issue Nov 17, 2020 · 2 comments
Open
2 of 4 tasks

apex up doesnt support node 12 #820

omar-dulaimi opened this issue Nov 17, 2020 · 2 comments

Comments

@omar-dulaimi
Copy link

omar-dulaimi commented Nov 17, 2020

Prerequisites

  • I am running the latest version. (up upgrade)
  • I searched to see if the issue already exists.
  • I inspected the verbose debug output with the -v, --verbose flag.
  • Are you an Up Pro subscriber?

Description

Hello,
I added new code to our backend and it contained the not so new private class fields. Everything worked fine locally, running the same runtime version.

Steps to Reproduce

using up v1.5.1
add any private class fields like:

class Test {
 #result;
constructor(result) {
this.#result = result;
}
}

deploy live
inspect with:
up logs

After a couple of hours debugging this, I had to refactor the class to the old syntax. and everything worked.

Hopefully we won't run into this problem again when we decide to upgrade to node12.

Love Up?

Please consider signing up for Up Pro (https://up.docs.apex.sh/#guides.subscribing_to_up_pro) or donating via https://opencollective.com/apex-up/donate.

Slack

Join us on Slack https://chat.apex.sh/

@sobafuchs
Copy link

Did you set the following in your up.json?

 { "lambda": {"runtime":"nodejs12.x"} }

@omar-dulaimi
Copy link
Author

I did but nothing worked unfortunately so I had to revert back to nodejs10.x

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

No branches or pull requests

2 participants