-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Build error during "pc run --env prod" #292
Comments
Ok interesting I haven't experienced this error before but I'll try and recreate. Just to make sure your local host 3000 is not working right, is it just a blank page? |
Yes. the error output is same even if the page is empty. ( def index() returns pc.text("testing...") ) |
I'm sorry to bother you, but .. did you install node version more than It seems that all the errors are related to node. |
My node version is v18.12.1 (installed from nvm) |
note: I failed to regenerate to make the issue. The following environments are that I tried.
|
@dev-onejun Thanks for trying to reproduce. I can't reproduce this either, mine seems to work alright. If anyone else gets this issue I'll look into it more. Sorry for this issue @wbfw109 maybe it will be resolved in newer future versions can't seem to pin this error as of now |
I solved. (but I don't know exact reason) List of what I did:
pyconfig.py:
and run (I ignore the eslint installation error.) I carefully guess that it was a problem with the version of Pynecone. Thank you all for your interest in this issue. :) |
Describe the bug
I don't know what's problem. Running in development works well (
pc run
). but in production not. (pc run --env prod
)To Reproduce
Steps to reproduce the behavior:
pc run --env prod
in fish shellExpected behavior
Server will be opend.
Screenshots
Specifics (please complete the following information):
Additional context
After the error occurs, port 8000 always in used. It is recreated with new PID even if I kill it's PID.
└ This only seems to happen when I exit VS code with server is opening. 📅 updated on 2023-01-21 10:00:04
The text was updated successfully, but these errors were encountered: