Unable to find (or install) JSCustom on Package Control
See original GitHub issueI can’t seem to find JSCustom (also tried a few similar queries) on Package Control with Sublime Text 4.
I wonder if it is related to the MISSING
badge over on the Package Control page?
OS: macOS 11.4 Sublime version: 4107
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Cannot install Package Control - Sublime Text 3
Hi, I cannot install Package Control on my Sublime Text 3. ... I can't find the option to do so, so I am...
Read more >Troubleshooting - Package Control
There are no packages available for installation. This message is displayed whenever Package Control can not find any packages that are installable.
Read more >Can't find certain package in Package control: Install Package
8 Answers 8 · Go to Preferences > Package Control · In the Command Palette, type Package Control: Install Package · In the...
Read more >Can't find in package control · Issue #218 · babel/babel-sublime
I see the package here, but it doesn't seem to show up via cmd+shift+p -> "Package Control: Install Package" -> "Babel".
Read more >How to install & use Package Control | Scott Granneman
Press Command-Shift-P (Mac OS X) or Ctrl-Shift-P (Windows) to open the Command Palette. Start typing Package Control until you see the appropriate commands....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Now all is working fine, thanks!
Fixed. Please confirm/disconfirm.
The problem was an issue with the Package Control crawler that kept it from finding the ST3-compatible tags. I’ve worked around it by deleting some old dev tags.