I know that folks often ask to add things to Base here on Discourse, and that usually the correct answer is “no”, but I think there’s a very good reason to add Infiltrator.jl to Base Julia. Let me explain. Infiltrator.jl is a very useful and performant tool for debugging. However, it has one main d…

I share this concern, but it’s not too hard to write Main.@infiltrate instead of just @infiltrate.

Ohhh, does that work? I was wondering if there was a better way to do this. I guess I should have asked on Discourse instead of Stack Overflow, which I did 22 days ago: https://stackoverflow.com/questions/71208181/use-infiltrator-jl-on-package-code-without-adding-infitrator-to-project-toml

Hmm, I tried using Main.@infiltrate in my code and I’m getting the error below. Any advice? julia> using Infiltrator julia> using PackageA [ Info: Precompiling PackageA [b7d5e62f-924e-4906-b2b5-430ba4531d91] ERROR: LoadError: UndefVarError: @infiltrate not defined Stacktrace: [1] #macroexpand#51…

That shouldn’t be fatal, it just means your package wasn’t fully precompiled

Did you try adding Infiltrator in your default Julia environment? I think that makes it implicitly available in other environments as part of the environment stack in LOAD_PATH? Then you should be able to do using Infiltrator within your package — it’ll emit some warnings about undeclared dependen…

Just wrote some (minimal) documentation for this: https://juliadebug.github.io/Infiltrator.jl/stable/API/#Infiltration-and-exfiltration There’s also a precompile-safe function form now, which you can use like this: if isdefined(Main, :Infiltrator) Main.infiltrate(@__MODULE__, Base.@locals, @__F…

An older thread has additional details / tips that might be helpful for keeping Infiltrator out of your dependencies: [image] Separate "Dev" packages in Project.toml General Usage When creating a package, I often use dependencies that are purely for development and have n…

[image] c42f: That said, I do kinda wish Infiltrator or something like it was part of the REPL stdlib. If there was a macro @REPL to spawn a REPL inside an arbitrary scope that would be pretty great. [image] I’ve been waiting here 30 minutes for the debugger to reach my breakpoint just so I…

Did you know that you can write Main.@infiltrate in your package code and it will work if you have Infiltrator loaded in your session? You can edit it in with Revise once the deved package is loaded, otherwise it might complain at load, not sure

That was mentioned in the first reply: Add Infiltrator.jl to Base? - #2 by pdeffebach

Add Infiltrator.jl to Base?

Internals & Design

jbu July 29, 2022, 4:05am 8

An older thread has additional details / tips that might be helpful for keeping Infiltrator out of your dependencies:

Topic		Replies	Views
ANN: Infiltrator.jl Package Announcements package , announcement , debug , debugging	20	3050	September 4, 2019
How to use Infiltrator? General Usage	9	842	January 8, 2025
[ANN] Infiltrator.jl v1.0 Package Announcements debug , debugging	10	1930	June 18, 2025
ANN: Exfiltrator Community	16	1520	August 21, 2020
Infiltrator based debugger VS Code debug	2	977	September 15, 2023

Add Infiltrator.jl to Base?

Related topics