@danielbachhuber why not use Composer with WordPress Packagist instead? This would then include compiled and minified JS. Eventually if we use Browserify, using a submodule won't be an option.

why not use Composer with WordPress Packagist instead?

Because I'm managing dependencies with Git submodules. Also, I like the option to be able to easily contribute back while I'm working on the project.

OK, cool. But then eventually you'd need to run grunt build anyway if we do any Browserify compilation, right?

But then eventually you'd need to run grunt build anyway if we do any Browserify compilation, right?

Well, this would break my use of the project completely. My preference would be that you always commit a built copy of the assets to the repo.

@danielbachhuber You may not need to filter your script and style URLs anymore due to #249

Cool, thanks for the heads up 👍