# GHC JS Backend - Improve compiled size

**URL:** <https://discourse.haskell.org/t/ghc-js-backend-improve-compiled-size/12098>\
**Category:** Uncategorized\
**Created:** [May 14, 2025, 9:06pm UTC](https://discourse.haskell.org/t/ghc-js-backend-improve-compiled-size/12098 "2025-05-14T21:06:07Z")\
**Posts on this page:** 2\
**Page:** 2

<div class="post-metadata">

**Author:** ![GulinSS](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.haskell.org/gulinss/32/4922_2.png) [@GulinSS](https://discourse.haskell.org/u/GulinSS)\
**Post date:** [May 18, 2025, 3:00pm UTC](https://discourse.haskell.org/t/ghc-js-backend-improve-compiled-size/12098/21 "2025-05-18T15:00:08Z")

</div>

> [@panmona](#):
>
> -DGHCJS\_BROWSER

Specify this might require whole GHC JS Backend rebuild to make effect. This option does not work well when applied “on the fly”

* * *

Also keep in mind that this option is more like a hack for current GHC JS Backend. Better find a way how to avoid its usage.

---

<div class="post-metadata">

**Author:** ![GulinSS](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.haskell.org/gulinss/32/4922_2.png) [@GulinSS](https://discourse.haskell.org/u/GulinSS)\
**Post date:** [May 18, 2025, 3:02pm UTC](https://discourse.haskell.org/t/ghc-js-backend-improve-compiled-size/12098/22 "2025-05-18T15:02:55Z")

</div>

Also, if you have a good progress it would be nice to create an article which will describe your experience like we did. 🙂

We have to collect experience with modern GHC JS Backend to see whole picture of such complex transition.

[Previous page](https://discourse.haskell.org/t/ghc-js-backend-improve-compiled-size/12098.md?page=1)