I understand your point, and I agree that Bitcoin’s network effect is a powerful backer that is unlikely to suddenly evaporate. The best evidence of this is the continued increase in value of Bitcoin, despite many boom/bust cycles and competing chains.
I don’t recommend this method—it doesn’t have any advantage over the method described in this article (especially with the recent update on react-app-env), but does have the disadvantage of unexpectedly/accidentally overwriting a file with uncommitted changes.
Windows doesn’t have sh. Try naming the file .env.local instead, in which case dotenv will automatically read the file and you won’t need to make any change to package.json for your local environment. As for the other environments, you’ll need to figure out what the Windows equivalent of the
source command is. You should be able to use that in place of the call to
I know someone who works at a Japanese preschool in America. Several months ago she told me that her coworkers were considering investing in a holdings company which described itself as tied to the value of XRP. They claimed that XRP was poised to go up due to some announcements that are coming down the pipeline regarding XRP and banks in Japan.
Thank you Georgi.
As for the issue you mentioned, I did a fresh run through with the latest create-react-app (1.3.1) and react-scripts (1.0.1), and didn’t encounter the error. Are you using a fairly recent version of react-scripts? They have sometimes changed the loader config, perhaps an older version had some difference…
Thank you for pointing this out. In addition to losing proptypes, context, and the higher-order componentability, you would have to update every place that you use the component if ever needing to add state, implement any of the lifecycle methods, etc. Even if you don’t mind doing this, others could easily be surprised and confused by this. For this…