You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Follow the instruction and try to run env-cmd as suggested in docs. You will receive different error like FileNotFound etc. (I am using env-cmd version 9.0.1)
Expected Behavior
After some time, I found a solution. Working example:
"scripts": {
"build:local": "env-cmd -f ./.env.production.local npm run build",
"build:production": "env-cmd -f ./.env.production npm run build"
}
Is this a bug report?
Incorrect information in docs ->
Deployment
.Steps to Reproduce
Expected Behavior
After some time, I found a solution. Working example:
Actual Behavior
In docs you can find something like this:
The text was updated successfully, but these errors were encountered: