PHPackages                             delboy1978uk/bone-vendor-dev - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Framework](/categories/framework)
4. /
5. delboy1978uk/bone-vendor-dev

ActiveLibrary[Framework](/categories/framework)

delboy1978uk/bone-vendor-dev
============================

VendorDev package for Bone Framework

v1.2.0(2y ago)055MITPHPPHP ^8.2

Since Dec 18Pushed 2y ago1 watchersCompare

[ Source](https://github.com/delboy1978uk/bone-vendor-dev)[ Packagist](https://packagist.org/packages/delboy1978uk/bone-vendor-dev)[ RSS](/packages/delboy1978uk-bone-vendor-dev/feed)WikiDiscussions master Synced 1mo ago

READMEChangelogDependencies (2)Versions (9)Used By (0)

vendordev
=========

[](#vendordev)

If you create packagist libraries that get installed in your vendor folder, sometimes it's easier to work on those files directly inside a project. However, sometimes you might alter files that were installed by Composer and not Git, so you would typically clone the project again into a temp folder, move the `.git` into the composer installed one, delete the temp folder, then see the changes in the original folder. This tool does this for every project in a given vendor directory, then lists projects that have had files changed.

installation
------------

[](#installation)

Use Composer

```
composer require delboy1978uk/bone-vendor-dev

```

usage
-----

[](#usage)

If using Bone Framework, simply add to the `config/packages.php` to add the command. If not you can add the `VendorDevCommand` to any existing Symfony console app, or you can call `bin/vendor-tool`

```