Комментарии:
That was a very helpful approach of explanation. I managed to debug and fix my environmental variables issue I had. Thank you sir.
Ответить1. you don't have to install something globally to run "npx something"
2. to avoid extra space you can wrap the value in single quotes, e.g. "set NODE_ENV='development' && otherstuff..."
Great video, really helpful. Thank you.
ОтветитьThanks for this video man!
ОтветитьVideo was sooo good, had no choice but to subscribe! Thank you
ОтветитьFAB!
ОтветитьThanks... I recommend you post this on stack overflow
ОтветитьAll the commands here do not work under Windows. Too bad. Trifles a statement that it would work with "set" under Windows, but not a single one works. Very sad ... One should take a statement only if you have tested this !!!
Ответитьgood..
ОтветитьThanks Bro was confused why undefined was coming in console export $(cat .env) works like charm
But a question when i deploy my app to any cloud platform like heroku or any other does it work. means they just ask for environment variables while hosting during production
Thank you
Ответитьlife saver. thank you.
ОтветитьThanks for this tutorial, really informative. Can we get package.json information (such as version, script etc) at run time?
Ответитьthank you soo much
Ответитьsubscribed!
ОтветитьPerfectly concise. Answered my questions.
Ответитьnice video. But still trying to figure out how to have different configurations for staging and production. for example if i deploy to production, where do I store the .env file, because those variables are specific to production.
Ответитьyou come straight to point, I love it ... thanks for the help man..really appreciate it
Ответить