Sharing Top Content from the Angular-sphere.

JHipster release 4.13.0

  • This release was initially supposed to be a patch release, to fix this very annoying bug: – – But as we also merged support for Angular 5.1, it has become a minor release: – – As a result, this is recommended upgrade over JHipster v4.12.0 for everyone.
  • For an automatic upgrade, use the JHipster upgrade sub-generator on an existing application: – – And then run the upgrade sub-generator: – – For a manual upgrade, first upgrade your version of JHipster with: – – If you have an existing project, it will still use the JHipster version with…
  • To upgrade your project, you must first delete its folder and then run: – – You can also update your project and all its entities by running – – You can also update your entities one-by-one by running again the entity sub-generator, for example if your entity is named Foo…

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:

This release was initially supposed to be a patch release, to fix this very annoying bug:

But as we also merged support for Angular 5.1, it has become a minor release:

As a result, this is recommended upgrade over JHipster v4.12.0 for everyone.

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

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

And then run the upgrade sub-generator:

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

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 folder and then run:

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

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

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:

JHipster release 4.13.0