Kevin Herrera

Sure, but I think I might understand the issue. As you build the *.phar file, you notice the file size fluctuating as the build is running, is that correct? I...

The bug ticket mentions that they switched from a one-by-one approach to `buildFromIterator()`. The one-by-one approach is required by Box in order to process each individual file. While we may...

Hah, I like your idea much better! The current process is something like this: ``` for each file listed in box.json read its contents into memory process the contents add...

I'll see that Box supports this in the next major version of Box.

I did a quick performance test using [Symfony](https://packagist.org/packages/symfony/framework-standard-edition#v3.1.2) and got the following results: **Before PR:** ``` Building... real 15m51.610s user 6m55.666s sys 7m22.764s ``` **After PR:** ``` Building... real 16m40.861s...

I'll see about adding something like this for the next version of Box. Currently, the [`Phar::running()`](http://php.net/manual/en/phar.running.php) function should fit the bill if the `phar` extension is available.

I like this idea, but I need input from other users. Using the shebang line this way [doesn't appear to be supported everywhere](http://stackoverflow.com/questions/4303128/how-to-use-multiple-arguments-with-a-shebang-i-e).

Your `varDumper.php` script needs to `require` the Composer autoloader.

You will then need to manually require all of the classes you need in your `VarDumper.php` script.

It sounds like you believe that a `.phar` file contains bytecode that is loaded by PHP and then executed. A `.phar` file is basically an archive with a PHP script...