Mark Finger

Probably too late to the party, but my first guess would be that `root: process.cwd()` is probably pointing at the wrong directory. Assuming your config file lives in the root,...

Incidentally, babel's added source map support for something approaching bundling: https://github.com/babel/babel/pull/3323/files Probably not of relevance, but it's worth being aware of.

#111 is another possible solution

A common issue with build tools is the need to cover a lot of edge-cases. These cases accumulate, codebases become bloated, and development slows down. The usual solution is a...

Unfort used to be a fairly large monorepo project that was broken up once it had stabilised. This was done with the intention that boundaries would be formed and cognitive...

**monorepo + greenkeeper** Yeah, monorepo sounds like the way to go. https://github.com/greenkeeperio/greenkeeper/issues/139 is still pending. In the short term, it's probably easiest to simply turn greenkeeper off and go back...

Unfort handles files as individual units, which ensures that moving the pipeline into child processes shouldn't be the most difficult process - at least, in concept. The current process involves...

One downside to moving the pipeline into workers is that it would probably require any overrides to be made in separate files so that the workers can import them without...

Should create a reasonably large test-case with 10,000+ files in random directories. Should randomly generate the code and have them import one another so that the graph picks up everything....

Key benefits that I'm expecting from pipeline workers would be: - increasing the IO thread count so that jobs touching the FS complete faster - off-loading CPU-intensive code that's blocking...