# Transforming a Pluto notebook into a Julia package

**URL:** <https://discourse.julialang.org/t/transforming-a-pluto-notebook-into-a-julia-package/60789>\
**Category:** Pluto\
**Created:** [May 8, 2021, 6:47pm UTC](https://discourse.julialang.org/t/transforming-a-pluto-notebook-into-a-julia-package/60789 "2021-05-08T18:47:14Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![aplavin](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/aplavin/32/222056_2.png) [@aplavin](https://discourse.julialang.org/u/aplavin)\
**Post date:** [May 8, 2021, 8:47pm UTC](https://discourse.julialang.org/t/transforming-a-pluto-notebook-into-a-julia-package/60789/7 "2021-05-08T20:47:49Z")

</div>

It would indeed be great to be able to seamlessly transition from early prototyping in Pluto to a regular package! I asked a similar question on slack just a few days ago, but looks like nothing like this exists.

Compared to REPL or IDEs like VSCode, Pluto is reactive: tests and examples immediately reexecute when any related piece of code is changed. Also, there are no issues with modifying definitions of structs in Pluto - unlike plain julia or Revise.

---

_[View the full topic](https://discourse.julialang.org/t/transforming-a-pluto-notebook-into-a-julia-package/60789)._