# A process for core library fixes and improvements

**URL:** <https://discourse.elm-lang.org/t/a-process-for-core-library-fixes-and-improvements/7916>\
**Category:** Request Feedback\
**Created:** [November 15, 2021, 8:05pm UTC](https://discourse.elm-lang.org/t/a-process-for-core-library-fixes-and-improvements/7916 "2021-11-15T20:05:29Z")\
**Posts on this page:** 1\
**Showing post:** 41

<div class="post-metadata">

**Author:** ![opvasger](https://avatars.discourse-cdn.com/v4/letter/o/8e8cbc/32.png) [@opvasger](https://discourse.elm-lang.org/u/opvasger)\
**Post date:** [November 27, 2021, 8:54am UTC](https://discourse.elm-lang.org/t/a-process-for-core-library-fixes-and-improvements/7916/41 "2021-11-27T08:54:42Z")

</div>

Manipulating compiler-output with scripts works perfectly well - we could make a bunch of those in a Git-repo to support various browser APIs, fix issues, and make performance-improvements.

elm-optimize-level-2 sort of does this

I do this a lot instead of asking for work elsewhere ☀

---

_[View the full topic](https://discourse.elm-lang.org/t/a-process-for-core-library-fixes-and-improvements/7916)._