How to separate module environment from package environment

[Titas22]

Hi,

Is there a way to nicely and easily separate a development environment from the actual package one?

Say I’m working on a small module and to test it I want to use it either in REPL or a scrip and I want to use Revise.jl to not have to restart the session all the time.

If I add it via ] add Revise it will end up in the packages Project.toml file which I don’t really want since the package itself doesn’t need that as a dependency.

[gdalle]

An easy approach is to create a shared environment that is different from your default v1.9, for instance pkg> activate @playground, and then pkg> dev your package into it.

How should I use Revise.jl (and other developer tools) to develop a package?

When I create a new package, I often want BenchmarkTools, Revise, and other dependencies that are accessible within my package’s environment, but won’t be added as dependencies for users. I’ve tried playing around with [extras], but I have not been able to replicate this usage. How are folks using Revise when developing a package? Are you adding Revise as a dependency, then removing it before you commit?