finds.dev← search

// the find

jhipster/generator-jhipster

★ 22,421 · TypeScript · Apache-2.0 · updated Jun 2026

JHipster is a development platform to quickly generate, develop, & deploy modern web applications & microservice architectures.

JHipster is a Yeoman-based code generator that scaffolds full-stack Spring Boot + Angular/React/Vue applications with your choice of database, auth mechanism, and build tool. It's been around since 2013 and targets Java backend developers who want to skip the boilerplate of wiring together a production-ready monolith or microservice architecture. The generated code is yours to own and modify.

The matrix of supported combinations is genuinely impressive — SQL/NoSQL, JWT/OAuth2/session auth, Maven/Gradle, three frontend frameworks — and daily CI builds verify each permutation actually works, not just the happy path. The blueprint system lets you extend or override the generator without forking it, which is the right abstraction for enterprise customization. JDL (JHipster Domain Language) lets you describe your entity model once and generate both backend entities and frontend CRUD in one shot — useful for data-heavy apps where schema changes are frequent. It's actively maintained with commits as recent as yesterday and has a real ecosystem of blueprints (Quarkus, Micronaut, .NET) that reuse the same JDL toolchain.

The generated code is verbose by design, and once you diverge from the generator's opinions you're on your own — regenerating after significant customization is painful because the merge conflicts are enormous. The Yeoman dependency is a liability; Yeoman itself is largely unmaintained and the generator toolchain feels dated compared to modern alternatives like nx or turborepo. Microservice setups require Eureka or Consul for service discovery and a gateway, which is a lot of infrastructure to manage for teams that just want a few services talking to each other. The output leans heavily on patterns from 2018-era Spring Boot (XML-free but still very annotation-heavy), so developers who prefer a more functional or reactive style will find themselves fighting the generated structure.

View on GitHub → Homepage ↗

// want more like this?

We dig through GitHub every week and send a few repos picked for what you actually care about — each with an honest take like this one.

Get finds in your inbox → Search again →