We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I essentially want to login as local auth even when npm run start, (because dev no opt the frontend web page is just way toooo slow!)
While in .env
# Deployment Environment: NODE_ENV="development" NEXT_PUBLIC_VERCEL_ENV="${NODE_ENV}"
with npm run dev, all is fine
But when running with npm run start, NEXT_PUBLIC_VERCEL_ENV switched to production, not respecting what .env tells it to be!
I have to manually modify code to make local auth work with optimized front end code
https://github.com/yhyu13/AgentGPT/blob/710a46d98205069bce867633b7c9a489c54fcc6d/next/src/server/auth/index.ts#L65
v1.0.0 release commit
running with npm run build && npm run start instead of npm run dev
No response
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Please check that this issue hasn't been reported before.
Expected Behavior
I essentially want to login as local auth even when npm run start, (because dev no opt the frontend web page is just way toooo slow!)
While in .env
with npm run dev, all is fine
But when running with npm run start, NEXT_PUBLIC_VERCEL_ENV switched to production, not respecting what .env tells it to be!
I have to manually modify code to make local auth work with optimized front end code
https://github.com/yhyu13/AgentGPT/blob/710a46d98205069bce867633b7c9a489c54fcc6d/next/src/server/auth/index.ts#L65
Current behaviour
v1.0.0 release commit
Steps to reproduce
running with npm run build && npm run start instead of npm run dev
Possible solution
No response
Which Operating Systems are you using?
Acknowledgements
The text was updated successfully, but these errors were encountered: