Panjie Setiawan Wicaksono

I don't know if I should do this, and there is still a new `tslint` that's being developed according to @angelozerr, but while waiting for it, I forked this repo...

Just bumped into this myself. I have similiar API response structure as @passcod ``` javascript { ... data: [ {actual: 'data'}, {actual: 'data'} ... ] ... } ``` Back when...

Thanks @deepsweet! For less plugin, if you could migrate it to the current start, I'm willing to test it because I have some use cases with less stuff right now....

So after much tinkering I ended up using `lerna run` script in each sub-package for AVA tests. I noticed when dealing with a lot of files (hundreds), which tends to...

Unfortunately I can't share the project which I tried `start` on for now. But, I created a repro at https://github.com/panjiesw/start-playground to simulate what I experienced above :) Maybe there's something...

About the master fix, I already tried it in linked local packages and it's indeed been fixed! From what I know for case 1: `lerna run --parallel` accepts `--concurrency` options...

Here is the result without `@babel/register` ```bash time --verbose npm run build:start Command being timed: "npm run build:start" User time (seconds): 102.66 System time (seconds): 3.65 Percent of CPU this...

:laughing: that's a 5 letters bug! It's a big improvement! The result with `time` doesn't show much, but my RAM usage isn't spiking as high as before, it's on par...

Dropping Node 6 is a good idea, since frankly Start is relatively new (the revived version), so its main target is also somewhat new packages with high possibility of running...

Not too pretty, but I created a reporter at https://github.com/panjiesw/start-ora-reporter. It's not for performance gain but I do need a reporter which doesn't output all files processed.