ctrl+shift+p filters: :st2 :st3 :win :osx :linux
Browse

Composer

by francodacosta ST2/ST3

composer plugin for Sublime Text 2

Details

  • 2013.11.15.20.36.13
  • github.​com
  • github.​com
  • 4 years ago
  • 2 hours ago
  • 5 years ago

Installs

  • Total 13K
  • Win 7K
  • OS X 3K
  • Linux 3K
Dec 12 Dec 11 Dec 10 Dec 9 Dec 8 Dec 7 Dec 6 Dec 5 Dec 4 Dec 3 Dec 2 Dec 1 Nov 30 Nov 29 Nov 28 Nov 27 Nov 26 Nov 25 Nov 24 Nov 23 Nov 22 Nov 21 Nov 20 Nov 19 Nov 18 Nov 17 Nov 16 Nov 15 Nov 14 Nov 13 Nov 12 Nov 11 Nov 10 Nov 9 Nov 8 Nov 7 Nov 6 Nov 5 Nov 4 Nov 3 Nov 2 Nov 1 Oct 31 Oct 30 Oct 29 Oct 28
Windows 5 2 3 3 4 5 2 3 8 2 3 4 5 10 5 4 2 4 8 6 6 11 5 6 5 4 7 4 9 2 3 6 5 7 4 5 4 3 3 6 6 3 7 7 3 3
OS X 0 3 1 2 1 3 1 5 2 0 0 0 3 1 3 2 3 2 0 0 2 1 4 0 0 2 1 0 3 1 1 1 0 2 2 1 2 1 1 2 0 0 0 1 0 1
Linux 0 4 1 1 1 5 2 0 0 2 1 3 2 2 3 2 3 1 3 2 7 1 1 2 0 2 0 3 1 1 1 2 1 6 1 1 3 1 5 0 0 2 2 0 0 2

Readme

Source
raw.​githubusercontent.​com

Composer integration for Sublime Text 2 & 3

ST3 support is still beta, please report issues

With this plugin you can manage your dependencies with composer

Currently the following features are supported: * Execute composer install * Execute composer update * Execute composer self-update * Execute composer dump-autoload * Package management: * Add package * Remove package * Edit composer.json file * Validate a composer.json file

Instalation

Via Package Control

First install Package Control if you haven't done so yet.

Then go to Preferences -> Package Control -> Install Package and type composer to install this plugin.

This is the recommended installation method.

Manual Instalation

Go to your sublime package folder and type:

git clone git@github.com:francodacosta/composer-sublime.git

Running Composer

Just open the command prompt (ctrl + shifp + p) and type composer, context menus are also provided

Features Help

Composer install

executes the composer install command, with the default settings the following command will be executed

composer.phar install -n -v

Composer update

executes the composer update command, with the default settings the following command will be executed

composer.phar update -n -v

Composer self update

executes the composer self update command, updating the composer binary to the latest version. With the default settings the following command will be executed

composer.phar self-update -n -v

Composer dump autoload

executes the composer dump autoload command to regenerate the autloader configuration With the default settings the following command will be executed

composer.phar dump-autoload -n -v

Composer validade

executes the composer validate command With the default settings the following command will be executed

composer.phar validate -n -v

Composer Add Package

You can add a package to the required package list.

When you execute this command a prompt is presented (in the bottom of the screen) allowing you to specify the package name and version contraints

The syntax for adding a package is as follows:

package name : version

if you do not specify a version the default will be *

Composer Remove Package

Removes a package from the required packages section in composer.json

When you select this option a list of required packages will pop up, you only need to select the package to be removed

Note: this just removes the reference from composer.json_ it will not remove any files

Edit composer.json file

this option will open a new window pointing to the composer.json file

Configuration Options

  • show_status: show messages in the status bar
  • show_output: opens an output window and shows composer working
  • composer_command: Path to composer.phar file
  • composer_install_extra: extra arguments to pass to the install command
  • composer_update_extra: extra arguments to pass to the update command
  • composer_dumpautoload_extra: extra arguments to pass to the dump-autoload command
  • composer_selfupdate_extra: extra arguments to pass to the self-update command

How is composer.json found?

The plugin tries to locate the composer.json file. It starts at the same folder of the file beeing edited and goes all the way up to the root folder. If you do not specify the composer_command option the default is to look for composer.phar on the same folder where composer.json was found