# How to use Pluto when developping a package

**URL:** <https://discourse.julialang.org/t/how-to-use-pluto-when-developping-a-package/80016>\
**Category:** Pluto\
**Tags:** package\
**Created:** [April 25, 2022, 9:28pm UTC](https://discourse.julialang.org/t/how-to-use-pluto-when-developping-a-package/80016 "2022-04-25T21:28:18Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![maajdl](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/maajdl/32/22838_2.png) [@maajdl](https://discourse.julialang.org/u/maajdl)\
**Post date:** [April 25, 2022, 9:28pm UTC](https://discourse.julialang.org/t/how-to-use-pluto-when-developping-a-package/80016/1 "2022-04-25T21:28:19Z")

</div>

Hello

The last version of Pluto has its own built-in package manager.  
Unfortunately I need to include a **Pkg.activate()** statement in the notebooks for testing.  
And this statement should be removed before distribution.  
To make sure packages will then be installed automatically.

Would there be another way to work?  
Just to avoid editing before distributing …

Thanks,

Michel

**I want to avoid using Pkg.activate() in Pluto files when testinh**

```julia
begin
	using Pkg
	Pkg.activate()
	using ThermoMineral
	using Plots
end

```

**My simple package**

```julia
> ThermoMineral
> ├── Manifest.toml
> ├── Project.toml
> ├── sample Pluto notebooks
> │ ├── 1 ThermoMineral.jl
> │ ├── 2 Equilibrium examples.jl
> │ ├── 3 Ellingham diagram.jl
> │ ├── 4 Adiabatic flame temperature.jl
> │ ├── 5 Clinker burning.jl
> └── src
> ├── ThermoMineral.jl
> ├── cement.jl
> ├── composition.jl
> ├── functions.jl
> ├── mineralData.jl
> ├── mixture.jl
> ├── substance.jl
> ├── thermoData.jl
> └── util.jl

```