{"id":15409,"date":"2014-09-06T20:37:25","date_gmt":"2014-09-06T15:07:25","guid":{"rendered":"https:\/\/2thenew.online\/blog\/?p=15409"},"modified":"2014-09-06T20:37:25","modified_gmt":"2014-09-06T15:07:25","slug":"check-global-object-pollution-using-global-object-guard","status":"publish","type":"post","link":"https:\/\/2thenew.online\/blog\/check-global-object-pollution-using-global-object-guard\/","title":{"rendered":"Check Global Object Pollution using global-object-guard"},"content":{"rendered":"

JavaScript is language for Ninjas some time mistake happens by Ninja also which slow down our Node Application, because unknowingly we are dynamically creating the property on GLOBAL objects or some time we get stuck in some closure issue’s which are not easy to trace and becomes a memory leak for the application. These are the common problem’s with Ninjas. During\u00a0all these problems I found some useful npm module called global-object-guard which become a solution for my problems related with GLOBAL objects.<\/p>\n

Lets discuss GLOBAL issues with the help of example.<\/strong><\/p>\n

_appSetting =<\/span> {<\/span>\r\n    PORT:<\/span> 2000<\/span>,<\/span>\r\n    HOST:<\/span> \"http:\/\/localhost\"<\/span>\r\n}<\/span>;<\/span>\r\n\r\n_otherServerSetting =<\/span> {<\/span>\r\n    \/\/So on...<\/span>\r\n}<\/span>;<\/span>\r\n\r\n\/\/ Do your code .......<\/span>\r\n\r\nobj =<\/span> {<\/span>name:<\/span> \"Kashish\"<\/span>,<\/span> age:<\/span> 24<\/span>}<\/span>;<\/span>\r\n\r\n(<\/span>function<\/span> ()<\/span> {<\/span>\r\n    person =<\/span> {<\/span>address:<\/span> \"B4-90 US\"<\/span>}<\/span>\r\n}<\/span>)();<\/span>\r\n\r\n<\/code><\/pre>\n
The above code polluting the GLOBAL object by making property dynamically which can be unknown to the developer<\/p>\n
When I write same code using npm module global-object-guard. Lets see how it will help us out to check whether code is hitting global object or not??<\/p>\n
Help your self with global-object-guard<\/strong><\/p>\n
\/\/ Require this Package<\/span>\r\nvar<\/span> GlobalObjectGuard =<\/span> require<\/span>(<\/span>'global-object-guard'<\/span>);<\/span>\r\n\r\n\/\/My All Global Object Settings<\/span>\r\n_appSetting =<\/span> {<\/span>\r\n    PORT:<\/span> 2000<\/span>,<\/span>\r\n    HOST:<\/span> \"http:\/\/localhost\"<\/span>\r\n}<\/span>;<\/span>\r\n\r\n_otherServerSetting =<\/span> {<\/span>\r\n    \/\/So on...<\/span>\r\n}<\/span>;<\/span>\r\n\/\/--------------------------------------------<\/span>\r\n\r\n\/\/ Just Apply GlobalObjectGuard<\/span>\r\nvar<\/span> gb =<\/span> GlobalObjectGuard.<\/span>Create<\/span>(<\/span>global);<\/span>\r\n\r\n\/\/ Do your code .......<\/span>\r\n\r\n\/\/ Some time Mistakes happen<\/span>\r\nobj =<\/span> {<\/span>name:<\/span> \"Kashish\"<\/span>,<\/span> age:<\/span> 24<\/span>}<\/span>;<\/span>\r\n\r\n\/\/ Don't worry just check the Global Pollution if you want.<\/span>\r\nvar<\/span> result =<\/span> gb.<\/span>getDifference<\/span>();<\/span>\r\nconsole.<\/span>log<\/span>(<\/span>\"Checking Global Object Pollution: \"<\/span>,<\/span> result);<\/span>\r\n\/\/ Output: Checking Global Object Pollution:  { obj: [ { name: 'Kashish', age: 24 } ] }<\/span>\r\n\r\n\/\/ You can reposition your global object state<\/span>\r\n\/\/ This will Set your current global state as a default State<\/span>\r\n\/\/ (NOTE: ALL THE GLOBAL POLLUTION BECOMES THE PART OF GLOBAL OBJECT)<\/span>\r\ngb.<\/span>rePositionGlobalObject<\/span>(<\/span>global);<\/span>\r\n\r\n\/\/ Recheck the Status<\/span>\r\nresult =<\/span> gb.<\/span>getDifference<\/span>();<\/span>\r\nconsole.<\/span>log<\/span>(<\/span>\"After Reposition the Global Object: \"<\/span> +<\/span> JSON.<\/span>stringify<\/span>(<\/span>result));<\/span>\r\n\/\/ Output: After Reposition the Global Object: {}<\/span>\r\n\r\n\/\/ Lets do some mistake<\/span>\r\n(<\/span>function<\/span> ()<\/span> {<\/span>\r\n    person =<\/span> {<\/span>address:<\/span> \"B4-90 US\"<\/span>}<\/span>\r\n}<\/span>)();<\/span>\r\n\r\nresult =<\/span> gb.<\/span>getDifference<\/span>();<\/span>\r\nconsole.<\/span>log<\/span>(<\/span>\"Opes Just hit the global object: \"<\/span> +<\/span> JSON.<\/span>stringify<\/span>(<\/span>result));<\/span>\r\n\/\/ Output: Opes Just hit the global object: {\"person\":[{\"address\":\"B4-90 US\"}]}<\/span>\r\n\r\n\/\/ Let this GlobalObjectGuard take care this cleaning work. [ Dangerous it can kill your app also ]<\/span>\r\ngb.<\/span>refreshGlobalObject<\/span>();<\/span>\r\n\r\n\/\/ Check the status. Every Thing is Clean Now.<\/span>\r\nresult =<\/span> gb.<\/span>getDifference<\/span>();<\/span>\r\nconsole.<\/span>log<\/span>(<\/span>\"Everything is clean by GlobalObjectGuard: \"<\/span> +<\/span> JSON.<\/span>stringify<\/span>(<\/span>result));<\/span>\r\n\/\/ Output: Everything is clean by GlobalObjectGuard: {}<\/span><\/code><\/pre>\n
Some useful link…<\/p>\n
NPM: https:\/\/www.npmjs.org\/package\/global-object-guard<\/p>\n
GitHub: https:\/\/github.com\/kashishgupta1990\/global-object-guard<\/p>\n","protected":false},"excerpt":{"rendered":"
JavaScript is language for Ninjas some time mistake happens by Ninja also which slow down our Node Application, because unknowingly we are dynamically creating the property on GLOBAL objects or some time we get stuck in some closure issue’s which are not easy to trace and becomes a memory leak for the application. These are […]<\/p>\n","protected":false},"author":135,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":2,"footnotes":""},"categories":[1],"tags":[1506,1508,1507,1163,1177],"class_list":["post-15409","post","type-post","status-publish","format-standard","hentry","category-technology","tag-global-object","tag-global-object-guard","tag-guard","tag-memory-leak","tag-nodejs-2"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t