Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The following incompatible package was found installed: #136

Closed
zhanggang807 opened this issue May 25, 2021 · 12 comments
Closed

The following incompatible package was found installed: #136

zhanggang807 opened this issue May 25, 2021 · 12 comments

Comments

@zhanggang807
Copy link

Package Control

The following incompatible package was found installed:

Pretty JSON

This is usually due to syncing packages across different machines in a way that does not check package metadata for compatibility.

Please visit https://packagecontrol.io/docs/syncing for information about how to properly sync configuration and packages across machines.

To restore package functionality, please remove each listed package and reinstall it

@TerminalFi
Copy link
Collaborator

  1. Are you syncing this package across machines?
  2. Are those machines using the same Sublime Text version?

@tfarmerpgr
Copy link

I am going to go out on a limb and say it is from the ST4 upgrade. I had the same issue yesterday. Of all of the installed packages, Pretty JSON was the only one that had this message displayed after the upgrade. It displays this message on every start of Sublime Text 4, unless the package is removed.

  • Package syncing not enabled
  • Package installed via Package Control awhile back

@jaraco
Copy link

jaraco commented May 26, 2021

I encountered the same error alongside another plugin (Babel) after updating to ST4 4107. The error with Babel cleared after upgrading that plugin. I concur there's probably an incompatible change that occurred with the latest ST update that broken the plugin metadata.

@BryanH
Copy link

BryanH commented May 26, 2021

This works for me:

  1. Remove Pretty JSON using package manager
  2. Add Pretty JSON using package manager
  3. Close and reopen Sublime

Environment: macOS Catalina (10.15.7); Sublime 4 (build 4107)

@travelgirl-fics
Copy link

travelgirl-fics commented May 26, 2021

also have the same problem moving from ST 3 to 4. no syncing (one machine only)

i remove pretty json, but i can't reinstall version compatible with ST 4. the error: expecting value line 1 column 1 char 0 whenever i try to prettify a json file

during installation, the description in package manager implies compatibility with sublime 2 and 3 only. closing/reopening ST does not fix problem

windows 10 home, sublime 4 (build 4107)

@TerminalFi
Copy link
Collaborator

Can you share the JSON you are trying and a screen recording of it happening?

@travelgirl-fics
Copy link

travelgirl-fics commented May 26, 2021

this is the file that doesn't work -- it has comments for first and last line, but i believe that's allowed by spec:
Ukulele Chordify Config - ORIGINAL Rob Caplan.json.txt

this file doesn't sort (but doesn't display an error):
settings.json.txt

remove the .txt (github apparently doesn't approve of json files for upload

other files seem to work just fine. random chance had me fail two of hundreds/thousands on my box :)

@TerminalFi
Copy link
Collaborator

@travelgirl-fics when you reinstall Pretty JSON fully quit sublime and launch again. Does the issue persist?

@TerminalFi
Copy link
Collaborator

Resolved with latest release

@travelgirl-fics
Copy link

uninstall pretty json
close ST
reopen ST
install pretty json
close ST
reopen ST
run PJ against the chordify/caplan file
fails

Clipboard01

@TerminalFi TerminalFi reopened this May 26, 2021
@TerminalFi
Copy link
Collaborator

uninstall pretty json
close ST
reopen ST
install pretty json
close ST
reopen ST
run PJ against the chordify/caplan file
fails

Clipboard01

This is due to that file having comments. This plugin follows JSON spec which doesn't support comments.

#25

@travelgirl-fics
Copy link

huh. would have sworn the spec allowed comments. sigh.
thx :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants