While a bundler itself might be very niche, I believe what is learned here can also be applied to many other areas: building a linter, dead code analyzer, testi

While a bundler itself might be very niche, I believe what is learned here can also be applied to many other areas: building a linter, dead code analyzer, testing framework, code quality checker, diff tool, SRI for files, etc., basically anything that needs to go from an entry point to grab all the files imported in the tree. It's still not a "mainstream need" by any means, but I believe with this article you can do many more things than just a bundler. Fairly well put in the first paragraph IMHO: > If we think of JavaScript testing as a map-reduce operation that maps over all test files and “reduces” them to test results, then JavaScript bundling maps over all source files and “reduces” them into a bundle