-
Notifications
You must be signed in to change notification settings - Fork 1k
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
[REF-552] Reflex prints warning about Node binary not found #1778
Comments
@masenf I have made some changes, now how to verify changes locally? |
Hi @masenf I looked at the source code for the problem that you mentioned. This is my understanding. "reflex init" installs bun and node using reflex/reflex/utils/processes.py Lines 116 to 134 in 7019708
In this function, node's bin path is fetched in order to be added to the PATH variable, and if node isn't installed, the warning that you mentioned is thrown. Since python3:11 docker image doesn't have node installed by default, and we need to install node using fnm zip, it makes sense for the initial calls to install bun and node to throw these warnings (as these installation is done through processes.new_process). So, I feel that this warning makes sense - as until we install node, the warning needs to be thrown... Your thoughts on this? |
Running
reflex init
inside a freshpython:3.11
docker contain prints the following warning twiceWhich doesn't really make sense, because then it goes and bootstraps a version of node, which it then proceeds to use.
This warning should only be displayed if node is not installed, and Reflex is unable to bootstrap a version.
Present in 0.2.7a3
From SyncLinear.com | REF-552
The text was updated successfully, but these errors were encountered: