builds fail when installing through package control

Building JS Custom.sublime-syntax.yaml-macros... (Packages/JSCustom/src/JS Custom.sublime-syntax.yaml-macros)

Error in macro execution.
  in "<file>", line 4, column 1

Error in macro execution.
  in "<file>", line 5, column 5

Traceback (most recent call last):
  File "~/Sublime Text 3/Packages/yaml_macros_engine/st3/yamlmacros/src/engine.py", line 68, in multi_constructor
    return apply_transformation(loader, node, macros[suffix])
  File "~/Sublime Text 3/Packages/yaml_macros_engine/st3/yamlmacros/src/engine.py", line 58, in apply_transformation
    return apply(transform, args)
  File "~/Sublime Text 3/Packages/yaml_macros_engine/st3/yamlmacros/src/util.py", line 18, in apply
    return fn(args)
  File "~/Sublime Text 3/Packages/yaml_macros_engine/st3/yamlmacros/lib/include.py", line 12, in include_resource
    file_path, file_contents = get_st_resource(resource)
  File "~/Sublime Text 3/Packages/yaml_macros_engine/st3/yamlmacros/src/sublime_resources.py", line 139, in get_st_resource
    installation_path = get_st_installation_folder()
  File "~/Sublime Text 3/Packages/yaml_macros_engine/st3/yamlmacros/src/sublime_resources.py", line 135, in get_st_installation_folder
    return path.dirname(exe)
  File "./python3.3/posixpath.py", line 151, in dirname
AttributeError: 'NoneType' object has no attribute 'rfind'

(file paths edited, replaced with ~)

same error on both builds

[Thom1729]

My bad! 1.0.16 uses the OutputPanel from sublime_lib, but I wasn’t constructing it correctly. As a result, it would break if the panel didn’t already exist. Because it existed in my session, I did not notice the error.

1.0.17 is out with a fix. It should be available through Package Control within an hour or so.

[Thom1729]

Your JS Custom syntaxes are listed under User. Because they are dynamically compiled, the actual syntax definitions are stored in Packages/User/JS Custom/Syntaxes. As far as I know, there is no way for JS Custom to change the behavior of this menu.

The Styled Components syntax only exists to support the new styled_components configuration option. It should not be visible in the menu. I’ve just released v1.0.8, which should correct this.