Buddhike de Silva

@jasongwartz Sorry about the lag in my response. This has been on our radar for a while but didn't make it to the top of the list. We would be...

@jasongwartz & @DoHe Thanks for sharing your experience here. That's a great story 👍. @fllaca I think it makes sense to prefix each line with the module name.

Custom arguments are specified in `.mbt.yml`. In this instance (assuming this is your build command in linux), you could do something like: ``` build: linux: cmd: npm args: ['run', 'dev:eap',...

Schema of `.mbt.yml` is documented here: https://mbtproject.github.io/mbt/#synopsis

Sorry I misunderstood your question 😊. Currently this is supported via environment variables. To achieve this, you would need a script like this: ``` #!/bin/sh set -e npm run dev:eap...

@ojizero Do you think `ApplyFilters` should return a more detailed information to support operations like this or is there a better way to do this?

It does not necessarily have to be in `ApplyFilters`. Could be a wrapper around it. But I guess we need a function that would return a set of filtered modules,...

@ojizero, Don't apologise man 😄. Thanks again for the awesome contributions. Take it easy!

I think this is a great idea. It's similar to the experience with `git`. I guess `HEAD^` and `HEAD~N` is more natural from that perspective.

Hey @philipbelcher, apologies for not updating the location before it disappeared. I intend to do this at some point but presently very time poor. It would be great if you...