Dwight Watson

Having a similar error over here with a new machine. I can run `php artisan basset:build --production` and the assets compile correctly, but they don't compile automatically on the development...

For some reason, I'm now getting the same error on my primary machine. The Node.js installer for Mac places `node` at `usr/local/bin/node`. I've tested the following filters: ``` $filter->whenAssetIs('.*\.less')->setArgument('/usr/local/bin/node', 1)->findMissingConstructorArgs();...

On another note, if I set the path to my Node in the `LessFilter` constructor, it does actually work... ``` public function __construct($nodeBin = '/usr/local/bin/node', array $nodePaths = array()) {...

This is by design, at some point the decision was made that the validator should operate on the mutated values. Looking back I'm not sure if I still think that...

Thanks for this - happy to consider it, but it's concerning that the change has broken the tests. If you can show that it works without breaking the existing functionality...

Hey, thanks for the suggestions. I don't mind the idea of adding `createOrFail` and `updateOrFail` but I don't feel the same about `newOrFail`. I feel like "newing up" an instance...

Yeah, I'd definitely be open to that functionality. I'm a little swamped at the moment but happy to accept a PR in the meantime.

Unfortunately this breaks all the tests - any idea on how to get the suite back to green when using `app()`?

Happy to review a PR with tests that covers this functionality. Unfortunately I'm not in a position to work on this feature at the moment.

I see where you're coming from, however a concern here is that we would now run the rules twice - and this is especially an issue when talking about the...