# \[ANN\] AppBundler.jl - Bundle Your Julia GUI Application

**URL:** <https://discourse.julialang.org/t/ann-appbundler-jl-bundle-your-julia-gui-application/106971>\
**Category:** Package Announcements\
**Tags:** announcement, gui\
**Created:** [November 30, 2023, 11:40pm UTC](https://discourse.julialang.org/t/ann-appbundler-jl-bundle-your-julia-gui-application/106971 "2023-11-30T23:40:50Z")\
**Posts on this page:** 1\
**Showing post:** 37

<div class="post-metadata">

**Author:** ![Janis\_Erdmanis](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/janis_erdmanis/32/10869_2.png) [@Janis\_Erdmanis](https://discourse.julialang.org/u/Janis_Erdmanis)\
**Post date:** [November 14, 2025, 10:11am UTC](https://discourse.julialang.org/t/ann-appbundler-jl-bundle-your-julia-gui-application/106971/37 "2025-11-14T10:11:36Z")

</div>

Currently, it seems they are downloaded at runtime and placed in the user’s `DEPOT_PATH`. I overlooked them. There appears to be an easy fix by using `include_lazy=true` when retrieving them with [`Artefacts.select_downloadable_artifacts`](https://docs.julialang.org/en/v1/stdlib/Artifacts/#Artifacts.select_downloadable_artifacts), which I plan to implement.

---

_[View the full topic](https://discourse.julialang.org/t/ann-appbundler-jl-bundle-your-julia-gui-application/106971)._
