未加星标

3 simple tips for handling environment variables in JavaScript

字体大小 | |
[前端(javascript) 所属分类 前端(javascript) | 发布者 店小二05 | 时间 2019 | 作者 红领巾 ] 0人收藏点击收藏

So you have a SPA application and you are proud of it. And suddenly a random developer comes and say: "In a test environment, we need a bit different URL/variable/routine/stupid thing/..."

In big companies, the way to solve above is a piece of cake. You go to the architect and (s)he gives you a solution. Everybody implements it and are happy ever after.

Wait! No! Step back!!!! The real life doesn't look like this. But the problem still exists. We need variables in our SPA applications. No matter in is it Angular, React or Vue. Bellow a few ideas on how to solve this problem.

Solution 1 - No config at all

To implement "no config at all" you need to create a multiple if statements based for example on URL. So when the application is on localhost variable becomes X, when it is on test becomes Y, and so on. Example code can look like:

let envName = ""; if(document.URL.startsWith("http://localhost")){ envName = "localhost" } else if(document.URL.startsWith("https://test")){ envName = "test" } else if(document.URL.startsWith("https://www")){ envName = "prod" } else { console.warn("NOOOOOOO!!!!!") } Pros It is working, isn't it? Cons It isn't testable at all until you deploy to the proper environment You cannot create a new env fast Every mistake in the config function requires deploying to every environment Solution 2 - Build using env files

This is the most common solution in javascript world. For example, in Angular, you have following files:

├── environment.ts ├── environment.dev.ts ├── environment.uat.ts ├── environment.prod.ts

With entries .angular-cli.json like:

"environmentSource": "environments/environment.ts", "environments": { "dev": "environments/environment.ts", "prod": "environments/environment.prod.ts" }

More in the official documentation . In other frameworks it is similar. For example in React projects we use .env files ( example project ). In Vue.js is almost same ( docs )

Pros It looks better Adding new environment looks easy Testable is better because we can test all files separately and check the contents Cons Still building once for all environments is not possible, unless we run npm build in deploy scripts, which can have side effects (like packages changes) Solution 3 - default + override

Declare your variables in one file (like above in environment.ts ) and in your index.html include a separate javascript file with overrides, like <script src="env.js"></script> . If it won't exist or be empty your code will use defaults.

Pros env.js Cons You have to talk with backend developers or even worse with DevOps guy to create such file ;) The end

Do you use something else? Maybe I am wrong, and don't know a better solution. If yes please let me know!

本文前端(javascript)相关术语:javascript是什么意思 javascript下载 javascript权威指南 javascript基础教程 javascript 正则表达式 javascript设计模式 javascript高级程序设计 精通javascript javascript教程

代码区博客精选文章
分页:12
转载请注明
本文标题:3 simple tips for handling environment variables in JavaScript
本站链接:https://www.codesec.net/view/628440.html


1.凡CodeSecTeam转载的文章,均出自其它媒体或其他官网介绍,目的在于传递更多的信息,并不代表本站赞同其观点和其真实性负责;
2.转载的文章仅代表原创作者观点,与本站无关。其原创性以及文中陈述文字和内容未经本站证实,本站对该文以及其中全部或者部分内容、文字的真实性、完整性、及时性,不作出任何保证或承若;
3.如本站转载稿涉及版权等问题,请作者及时联系本站,我们会及时处理。
登录后可拥有收藏文章、关注作者等权限...
技术大类 技术大类 | 前端(javascript) | 评论(0) | 阅读(104)