Fix or workaround for obscure ERROR: expected package `JuliaSyntaxHighlighting [dc6e5ff7]` to be registered

[PallHaraldsson]

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.

[IanButterworth]

Apart from the vscode extension serving a bad manifest (@davidanthoff is aware of this, not sure if it's fixed yet) I don't expect this to be hit by new users. Apart from the vscode issue, the only way users would have hit this was trying a very early 1.12 beta, or master back when master was 1.12.

I do agree it's painful though.

[KristofferC]

Yeah, vscode have to fix their thing and then no one should hit anymore.