Implement startup validation for required environment variables

[manideepk90]

Implement startup validation for required environment variables

Create validation for required environment variables:

• HYPERSWITCH_PRODUCTION_URL
• HYPERSWITCH_SANDBOX_URL
• API keys and endpoints

Note: Ignore Sentry keys

Currently, we are not validating whether the keys are provided in the .env file or not. If the app is compiled or bundled without these keys, the PaymentSheet never opens. We should add a strict validation to ensure the required keys are present. This applies to both yarn start and yarn bundle commands.

[abhirajadhikary06]

Hi @manideepk90 ,

I’d like to take up issue.

My plan is to add a small Node.js script that checks for the presence/validation of HYPERSWITCH_PRODUCTION_URL, HYPERSWITCH_SANDBOX_URL, and the necessary API keys (excluding Sentry keys) before running yarn start or yarn bundle. The script will use dotenv to load variables from the .env file, log any missing ones, and exit with an error if something’s missing.

I’ll wire it up using prestart and prebundle hooks in package.json and make sure it’s tested properly. This should help prevent PaymentSheet issues caused by missing configurations.

Please assign me to this issue, and let me know if there are any additional resources I should follow.

Thanks!

[Sankalan47]

Hi @manideepk90
I've completed the implementation for the environment variable validation system.
PR: #376
The changes include:

• Comprehensive validation script for required/optional env variables
• Integration with all major build/start commands