JHipster release 4.11.0 Permalink to "JHipster release 4.11.0"

What’s new Permalink to "What’s new"

This release features 115 closed tickets and pull requests, here are the more important ones:

  • Use jhipster-dependencies BOM, that should greatly simplifies future application upgrades.
  • Couchbase support, in addition to our current MongoDB and Cassandra support (and of course MySQL, PostgreSQL, MariaDB, Oracle, SQL Server!).
  • Switch back from Chromium to PhantomJS - this is going to impact everyone: if you ever had any issue downloading or running Puppeteer, we’ve switched back to our old system, which was running faster and smoother. Of course, in the long term, the plan is still to move to Puppeteer.

We also added React support as an “experimental” feature, as we know a lot of people are waiting for it:

  • Please note this is experimental. Don’t expect it to work if you use non-default options, for example.
  • To enable experimental features, we have a specific --experimental flag: if you run jhipster --experimental you will have the new React option when selecting your front-end framework.
  • We need help to test and finish this implementation, so don’t hesitate to participate!

Closed tickets and merged pull requests Permalink to "Closed tickets and merged pull requests"

As always, you can check all closed tickets and merged pull requests here.

How to upgrade Permalink to "How to upgrade"

Automatic upgrade

For an automatic upgrade, use the JHipster upgrade sub-generator on an existing application:

Upgrade your version of JHipster:

yarn global upgrade generator-jhipster

And then run the upgrade sub-generator:

jhipster upgrade

Manual upgrades

For a manual upgrade, first upgrade your version of JHipster with:

yarn global upgrade generator-jhipster

If you have an existing project, it will still use the JHipster version with which it was generated. To upgrade your project, you must first delete its node_modules folder and then run:


You can also update your project and all its entities by running

jhipster --with-entities

You can also update your entities one-by-one by running again the entity sub-generator, for example if your entity is named Foo

jhipster entity Foo

Help and bugs Permalink to "Help and bugs"

If you find any issue with this release, don’t hesitate to:

If the issue you have is an urgent bug or security issue, please: