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
#10152 switched the prettify function to be async and that is of course fine. We then had to await the usage of that function now. We did update some at the time and then #10478 updated a lot of the others.
The problem is that #10478 was related to a major version upgrade and so was not cherry picked over into next. This means we have to create the fix against next or in someway backport the current code in main into next to fix this issue.
This only happens in JS projects.
How do we reproduce the bug?
Run CLI commands on the stable release version of redwood, e.g. yarn rw setup mailer.
What's your environment? (If it applies)
No response
Are you interested in working on this?
I'm interested in working on this
The text was updated successfully, but these errors were encountered:
Josh-Walker-GM
changed the title
[Bug]: CLI commands fail due to unawaited promise
[Bug]: CLI commands fail due to unawaited promise (JS projects)
Jun 9, 2024
This PR waits all calls to `transformTSToJS` which became async due to
the prettier upgrade explained here:
#10762Closes#10762Closes#10929
---------
Co-authored-by: GitHub Actions <>
Co-authored-by: Josh GM Walker <56300765+Josh-Walker-GM@users.noreply.github.com>
This PR waits all calls to `transformTSToJS` which became async due to
the prettier upgrade explained here:
#10762Closes#10762Closes#10929
---------
Co-authored-by: GitHub Actions <>
Co-authored-by: Josh GM Walker <56300765+Josh-Walker-GM@users.noreply.github.com>
What's not working?
#10152 switched the prettify function to be async and that is of course fine. We then had to await the usage of that function now. We did update some at the time and then #10478 updated a lot of the others.
The problem is that #10478 was related to a major version upgrade and so was not cherry picked over into next. This means we have to create the fix against next or in someway backport the current code in main into next to fix this issue.
This only happens in JS projects.
How do we reproduce the bug?
Run CLI commands on the stable release version of redwood, e.g.
yarn rw setup mailer
.What's your environment? (If it applies)
No response
Are you interested in working on this?
The text was updated successfully, but these errors were encountered: