You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Prerequisites
up upgrade
)-v, --verbose
flag.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:
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/
The text was updated successfully, but these errors were encountered: