# Modularization of JavaScript API **URL:** \ **Category:** 💡 Ideas\ **Created:** [February 5, 2021, 8:33pm UTC](https://es.discourse.group/t/modularization-of-javascript-api/637 "2021-02-05T20:33:43Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![redradist](https://yyz2.discourse-cdn.com/free1/user_avatar/es.discourse.group/redradist/32/396_2.png) [@redradist](https://es.discourse.group/u/redradist)\ **Post date:** [February 5, 2021, 8:33pm UTC](https://es.discourse.group/t/modularization-of-javascript-api/637/1 "2021-02-05T20:33:43Z")
Hi all, For me as developer that worked with lots of languages seems bad practices to put all JavaScript API in one global object as property ... Due to this JavaScript global object is looks like a garbage Is there a specification that tries to modularize JavaScript API ? In such way it would be easier to write cross-platform libraries and applications ... ---
**Author:** ![aclaymore](https://yyz2.discourse-cdn.com/free1/user_avatar/es.discourse.group/aclaymore/32/501_2.png) [@aclaymore](https://es.discourse.group/u/aclaymore)\ **Post date:** [February 5, 2021, 8:56pm UTC](https://es.discourse.group/t/modularization-of-javascript-api/637/2 "2021-02-05T20:56:31Z")
Hi @redradist There is this proposal: [GitHub - tc39/proposal-built-in-modules](https://github.com/tc39/proposal-built-in-modules) to add Standard built-in libraries for language APIs instead of adding them to the global object. ---
**Author:** ![ljharb](https://yyz2.discourse-cdn.com/free1/user_avatar/es.discourse.group/ljharb/32/8_2.png) [@ljharb](https://es.discourse.group/u/ljharb)\ **Post date:** [February 5, 2021, 8:57pm UTC](https://es.discourse.group/t/modularization-of-javascript-api/637/3 "2021-02-05T20:57:02Z")
You may find [https://github.com/tc39/proposal-built-in-modules](https://github.com/tc39/proposal-built-in-modules) interesting, but it's got a number of competing constraints.