# In 1.11 and 1.10: ERROR: expected package \`JuliaSyntaxHighlighting \[dc6e5ff7\]\` to be registered

**URL:** <https://discourse.julialang.org/t/in-1-11-and-1-10-error-expected-package-juliasyntaxhighlighting-dc6e5ff7-to-be-registered/122555>\
**Category:** General Usage\
**Created:** [November 12, 2024, 5:26pm UTC](https://discourse.julialang.org/t/in-1-11-and-1-10-error-expected-package-juliasyntaxhighlighting-dc6e5ff7-to-be-registered/122555 "2024-11-12T17:26:29Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Palli](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/palli/32/3380_2.png) [@Palli](https://discourse.julialang.org/u/Palli)\
**Post date:** [November 12, 2024, 5:26pm UTC](https://discourse.julialang.org/t/in-1-11-and-1-10-error-expected-package-juliasyntaxhighlighting-dc6e5ff7-to-be-registered/122555/1 "2024-11-12T17:26:29Z")

</div>

What is it about? I removed my ./Project.toml file just in case, then:

```julia
$ julia +1.11 --project=.

julia> using JSON
..
   Resolving package versions...
ERROR: expected package `JuliaSyntaxHighlighting [dc6e5ff7]` to be registered

also when adding it directly:

pkg> add JuliaSyntaxHighlighting
   Resolving package versions...
ERROR: expected package `JuliaSyntaxHighlighting [dc6e5ff7]` to be registered

```

I find old workaround (do not remove .julia, then at least move it):

> <https://stackoverflow.com/questions/65461774/error-expected-package-juno-e5e0dc1b-to-be-registered>

> I was able to solve this issue by deleting the registries folder within my .julia folder.

It likely works, but should such be needed? Why doesn’t Julia recover from this (what’s the least invasive fix/workaround)? Is it maybe “self-inflicted”, I often do CTRL-C while precompiling (to avoid OOM).

I checked some versions down to 1.6 same error as above, but in 1.5 different:

```julia
(pharaldsson) pkg> add Sentinel
┌ Error: Could not parse entry for `deps`
└ @ Pkg.Types /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.5/Pkg/src/manifest.jl:146
ERROR: MethodError: no method matching get(::Pair{String,Any}, ::String, ::Nothing)

```

---

<div class="post-metadata">

**Author:** ![Palli](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/palli/32/3380_2.png) [@Palli](https://discourse.julialang.org/u/Palli)\
**Post date:** [May 27, 2025, 11:42am UTC](https://discourse.julialang.org/t/in-1-11-and-1-10-error-expected-package-juliasyntaxhighlighting-dc6e5ff7-to-be-registered/122555/2 "2025-05-27T11:42:16Z")

</div>

I believe it only happens if you have a Manifest.toml file, and it’s kind of in the way, and you can move it out of the way be renaming it (maybe you’re even ok with deleting, I’m just unsure when it might have critical info for your project that you might want to preserve; myself I’ve never had to):

```julia
mv Manifest.toml Manifest.toml_old_in_the_way

```

in your current directory, if you were using a project there, you can also point to a fresh project directly, or if you’re not using one, then you might move the relevant file in the .julia directory…

I filed an issue:

> <https://github.com/JuliaLang/julia/issues/58534>
>
> I believe this only happens if you have a Manifest.toml file in the way when e.g…. doing:
> 
> julia project=.
> 
> What should Julia do, can it remove/rename the file, or even just state it's in the way? Could/should it add JuliaSyntaxHighlighting to it?
> 
> 
> This is a bad new user experience, not easily googlable, but I posted a workaround for my question here:
> 
> https://discourse.julialang.org/t/in-1-11-and-1-10-error-expected-package-juliasyntaxhighlighting-dc6e5ff7-to-be-registered/122555
> 
> See there, for a similar error for Juno, that I point to. I find it at least more important for this to work with Julia's own stdlib, so special-casing the error message, explaining what to do, rather than just what "happened", taking it into account feels appropriate.