Sublime Forum

New Sass Build for ST3 not available in Package Control

#1

It looks like an updated Sass Build package is available (version 2016.01.06.22.03.29) on https://packagecontrol.io/packages/SassBuilder. When I search for SassBuild* in Package Control: Install Package in ST3 I only see the old version for ST2 (v2015.03.10.11.27.26). This old version doesn’t appear to be compatible with ST3 (per the link above). How do I get this new version (now called Sass Builder)?

0 Likes

#2

You may have overridden the channel URL in your Package Control settings to point towards an old URL that is only for ST2.

1 Like

#3

Thanks for the quick response. I’m new to Sublime Text and just downloaded ST3 two days ago. I installed Package Control using the instructions here: “https://packagecontrol.io/installation”. The only thing I have really done after that is install additional packages using Package Control. I’m having trouble finding the Package Control settings as most of the package files are “packed”. Based on your article here: “https://github.com/wbond/package_control_channel” it looks like I may need to check / modify the channel.json file. Is that what you’re suggesting?

0 Likes

#4

I just tried to install this and It’s doing the same thing for me here. There may be something hinky going on behind the scenes with package metadata or something? Certainly I’ve also never fiddled with anything regarding channel URL’s for my installs.

In particular:

  • The PackageControl page you linked to says it’s version 2016.01.06.22.03.29, named Sass​Builder and written by bnlucas.
  • The version that PackageControl displays inside sublime has a completely different version number, name and author (also the github repo is different).

I’ve never experienced something like this before. It looks like the version the page is showing is a package that’s not available inside of PackageControl itself at all. I don’t know how the two correlate though.

In the interim you could do a manual install of the package, although that’s sub-optimal.

0 Likes

#5

Just to cover this particular question, you can generally get at the settings for installed packages via the Preferences > Package Settings menu item (or, if you’re using MacOS, Sublime Text > Preferences > Package Settings. This menu contains a list of packages for which there are settings you can look at/fiddle with.

0 Likes

#6

Thanks for that tip! Here’s code in my “Package Control.sublime-settings” file:

// A list of URLs that each contain a JSON file with a list of repositories.
// The repositories from these channels are placed in order after the
// repositories from the “repositories” setting
“channels”: [
https://packagecontrol.io/channel_v3.json
],

// A list of URLs that contain a packages JSON file. These repositories
// are placed in order before repositories from the "channels"
// setting
"repositories": [],

Based on this page: “https://github.com/wbond/package_control_channel” that code looks correct. I see here: “https://packagecontrol.io/docs/channels_and_repositories” that there is a way to upgrade the repository but I’m not sure that’s necessary as the above looks correct. I’ll hold off on that for now as I’m not sure of the ramifications of doing that upgrade as it appears to be used primarily for creating custom repositories.

0 Likes

#7

My guess would be that this is related to the fact that the plugin says that it’s ST3 compatible but it doesn’t mark itself as actually being ST3 compatible, so it doesn’t show up in the channel for ST3 packages.

0 Likes

#8

You both most likely ended up installing the SASS Build package (which is also far more popular) instead of SASS Builder. As @OdatNurd noted already, SASS Builder itself is not marked as compatible with ST3 and thus isn’t installable by default with PC. You can force PC to recognize it by manually adding the package’s github url as a “repository” to package control’s settings. There is also a command for this.

We have a policy that should prevent packages with similar names like these, but sometimes they slip through or have been added before that policy was enforced.

1 Like