Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing Brunch vs Angular, the Slant community recommends Brunch for most people. In the question“What are the best frontend JavaScript module bundlers?” Brunch is ranked 8th while Angular is ranked 9th. The most important reason people chose Brunch is:
According to speed benchmarks, Brunch is one of the fastest tools around for compiling files. According to the authors of Brunch the reason behind this speed is that it recompiles **only** the changes that were made to an app and performs extensive caching of the app's code.
Specs
Question Ranking
Pros
Pro Compilation is super fast
According to speed benchmarks, Brunch is one of the fastest tools around for compiling files. According to the authors of Brunch the reason behind this speed is that it recompiles only the changes that were made to an app and performs extensive caching of the app's code.
Pro Time to setup is extremely low
After installing Brunch the next step is to load a skeleton from git.io/skeletons. This step is as easy as installing another plugin from the npm registry, just point Brunch to the path of the required skeleton/generator then wait for it to work out its magic. Next, run brunch build then wait for a second or two and voila! the project is ready.
Pro The configuration file is small and the configuration itself is fast and easy
Brunch's config files can be extremely small compared to other alternatives. The fact that brunch also allows you to chose from a number of generators also lowers the configuration time considerably.
Pro Concatenates scripts and styles and auto-generates matching source maps
Brunch automatically produces a source map for all javascript files and CSS stylesheets whenever it minifies an app's resources. This little feature is extremely helpful when debugging is required at the client end.
Pro Great tooling and language support
Very good CLI and webpack, bundling, testing, deployment support. Deep TypeScript integration and support.
Cons
Con Slightly over-engineered
Very enterprisey - made for huge architectures and with tons of declarative, non-intuitive annotations it makes it overkill for very small projects.
Con Native i18n support over-engineered
Not developer-friendly. Switching languages need reloading the whole page. There are third party solutions that work better.
