When creating a package, I often use dependencies that are purely for development and have nothing to do with my package’s functionality (e.g. Revise.jl , Debugger.jl , Infiltrator.jl . If I ever wanted to share my package, these unnecessary packages would be shared too unless I manually deleted them f…

Environments in Julia are nested, when working on a project you usually have access to both - package’s dependencies and dependencies in the enclosing environment (e.g. @v1.6): (YourPackage) pkg> st # prints dependencies of YourPackage (YourPackage) pkg> activate. # switch to the default environm…

This is a good question. My current approach is to have Infiltrator in my 1.6 project.toml, then inside my module code use Main.@infiltrate.

Can all of that stuff go in test dependencies? Having the separate project and manifest for those seems to make sense and presumably you are doing development by editing/creating tests anyways?

The way most people deal with this is to have all those dev packages, as you call them, installed in your Main environment ((@1.6), for example) and then create a new environment for your package ((@MyPkg)) . With this setup you have access to Revise and Debugger, and any other package you need to w…

So, technically, there are two separate @MyPkg environments, one in environments folder and the other in dev/MyPkg folder? Is there a workflow description for this thing?

It’s documented in the Pkg.jl docs introduction here . Basically, when you start the REPL with julia --project, you have access to your 1.6 environment as well as your MyPackage project.toml. This issue is about how stuff inside MyPackage can’t see the 1.6 project.toml

But no. There are not two MyPkg environments. People above this post have been referring to the Main environment (@v1.6 for example) and your package’s environment @MyPkg. The packages that are installed in the main environment are accessible from all julia sessions no matter what other environment …

You can build your own custom stack pretty easily (as briefly mentioned above). For example, if you keep dev tools installed in devtools/Project.toml as follows: $ tree . . |-- devtools | |-- Manifest.toml | `-- Project.toml # Debugger, BenchmarkTools, ... |-- Manifest.toml |-- Project.toml …

Separate "Dev" packages in Project.toml

General Usage

Topic		Replies	Views
Is there concept of dev dependencies in Pkg? General Usage	11	1947	June 21, 2021
Is there a way to separate development dependencies from runtime dependencies in Project.toml? New to Julia	2	461	February 18, 2021
Add dev packages to Pkg environment outside of Project.toml New to Julia	2	972	February 12, 2021
Use package not in current environment for testing/development General Usage	12	1520	October 30, 2021
How to install packages which are needed only for development General Usage package-manager	3	1742	March 13, 2019

Separate "Dev" packages in Project.toml

Related topics