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
Because npm run dev command includes env-cmd concurrently, for it to work, there needs to be a .env (or .env.js or .env.json) file in the root folder.
Solution 1: Suggest creating a .env.example file in the root folder. An attendant change might be to include the following in the .gitignore files: .env.*!.env.example
Solution 2: Don't use env-cmd and just use concurrently directly. I thought it's more common to include env variables / .env file in the backend, as opposed in the root of the folder hmm
The text was updated successfully, but these errors were encountered:
zxt-tzx
changed the title
Include .env.example in root folder
include .env.example in root folder
Mar 21, 2022
Because
npm run dev
command includesenv-cmd concurrently
, for it to work, there needs to be a.env
(or.env.js
or.env.json
) file in the root folder.Solution 1: Suggest creating a
.env.example
file in the root folder. An attendant change might be to include the following in the.gitignore
files:.env.*
!.env.example
Solution 2: Don't use
env-cmd
and just useconcurrently
directly. I thought it's more common to includeenv
variables /.env
file in the backend, as opposed in the root of the folder hmmThe text was updated successfully, but these errors were encountered: