# What's in your @?

**URL:** https://discourse.julialang.org/t/whats-in-your/129530
**Category:** General Usage
**Tags:** package, environment
**Created:** [June 1, 2025, 4:00pm UTC](https://discourse.julialang.org/t/whats-in-your/129530 "2025-06-01T16:00:04Z")
**Posts on this page:** 1
**Showing post:** 13

<div class="post-metadata">

### Author: ![sijo](https://avatars.discourse-cdn.com/v4/letter/s/da6949/32.png) [@sijo](https://discourse.julialang.org/u/sijo)
#### Post date: [June 2, 2025, 9:09am UTC](https://discourse.julialang.org/t/whats-in-your/129530/13 "2025-06-02T09:09:02Z")

</div>

```julia
pkg> st
ERROR: no active project

```

because I disable this feature in my `startup.jl`:

```julia
# Remove global environment from load path
let
    i = findfirst(==("@v#.#"), LOAD_PATH)
    if !isnothing(i)
        deleteat!(LOAD_PATH, i)
    end
end

```

Too many times I have added packages in the global environment by mistake, and then I forgot to add them in the local environment (because it was working!), resulting in non-reproducible projects and possibly corrupted state where incompatible packages where used together. Because as the [documentation says](https://docs.julialang.org/en/v1/manual/code-loading/#Environment-stacks):

> Packages in non-primary environments can end up using incompatible versions of their dependencies even if their own environments are entirely compatible. This can happen when one of their dependencies is shadowed by a version in an earlier environment in the stack (either by graph or path, or both).

I’ve ranted about this before (a bit too vehemently) [here](https://discourse.julialang.org/t/general-environment-creating-issues-for-local-ones/74327/4). The gist of it is that I don’t understand why Julia would use incompatible package versions by default, instead of showing an error and maybe having an opt-in setting to allow it (suggested name: `yolo=yes`).

---

_[View the full topic](https://discourse.julialang.org/t/whats-in-your/129530)._