NEXT_PUBLIC_VERCEL_ENV="development" in .env not respected when npm run start

[yhyu13]

Please check that this issue hasn't been reported before.

• I searched previous Bug Reports didn't find any similar reports.

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

# 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

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?

• Android
• iPhone/iPad
• Linux
• macOS
• Windows

Acknowledgements

• My issue title is concise, descriptive, and in title casing.
• I have searched the existing issues to make sure this bug has not been reported yet.
• I am using the latest version of AgentGPT.
• I have provided enough information for the maintainers to reproduce and diagnose the issue.