# Track down the JavaScript code responsible for polluting the global scope

**URL:** <https://forum.devtalk.com/t/track-down-the-javascript-code-responsible-for-polluting-the-global-scope/41063>\
**Category:** Frontend In The News\
**Tags:** javascript, code, in-the-news\
**Created:** [17 February 2022 13:03 UTC](https://forum.devtalk.com/t/track-down-the-javascript-code-responsible-for-polluting-the-global-scope/41063 "2022-02-17T13:03:19Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![CommunityNews](https://forum.devtalk.com/user_avatar/forum.devtalk.com/communitynews/32/1113_2.png) [@CommunityNews](https://forum.devtalk.com/u/CommunityNews)\
**Post date:** [17 February 2022 13:03 UTC](https://forum.devtalk.com/t/track-down-the-javascript-code-responsible-for-polluting-the-global-scope/41063/1 "2022-02-17T13:03:19Z")

</div>

> Track down the JavaScript code responsible for polluting the global scope.  
> Here’s how you can debug what JavaScript code is adding global variables to the window object

Read in full here:

> **[Track down the JavaScript code responsible for polluting the global scope](https://mmazzarolo.com/blog/2022-02-16-track-down-the-javascript-code-responsible-for-polluting-the-global-scope/)**
>
> Debugging what JavaScript code is adding global variables to the window object.

_This thread was posted by one of our members via one of our news source trackers._