# VS Code Linting missingref on my own package

**URL:** <https://discourse.julialang.org/t/vs-code-linting-missingref-on-my-own-package/94450>\
**Category:** New to Julia\
**Tags:** question, package, lint\
**Created:** [February 11, 2023, 1:53am UTC](https://discourse.julialang.org/t/vs-code-linting-missingref-on-my-own-package/94450 "2023-02-11T01:53:19Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![graphitical](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/graphitical/32/45785_2.png) [@graphitical](https://discourse.julialang.org/u/graphitical)\
**Post date:** [February 11, 2023, 1:53am UTC](https://discourse.julialang.org/t/vs-code-linting-missingref-on-my-own-package/94450/1 "2023-02-11T01:53:20Z")

</div>

I’m writing my own package using VS Code and when I go to write some minor programs in a `scripts` folder I get a missingref warning for my own package. Other people have posted about this, but I can’t seem to use their solutions. For example, one key issue is activating the current project environment, but I have already done that. My directory structure looks like this

MyPackage/  
├─ scripts/  
│ ├─ myscript.jl  
├─ src/  
│ ├─ file1.jl  
│ ├─ file2.jl  
│ ├─ MyPackage.jl  
├─ test/  
│ ├─ sometest.jl  
Manifest.toml  
Project.toml

I am hoping that there is some other detail that I need to tell VSCode about so I don’t have to keep bumping into this issue.