I am trying to use the generator-jhipster-material to generate the Jhipster in combination with Bootstrap material design and I was not successfull in achieving it.
Does the "generator-jhipster-material" has been ported to latest Angular 4, Jhipster 4, Bootstrap 4 ?
No because last publication is from one year ago (before Angular 2+ support was added to Jhipster)
Related
i searched google but couldn't find any migration guide.
I've working website that is in Bootstrap 3.0.2, I am upgrading it to Bootstrap 3.4.1 because of the vulnerabilities found in <3.4.1, I know I may have to give my code a major revamp to migrate it. I just want to know is it safe to use bootstrap 3.4.1 ? or migrate ot v4 ?
also can you point me to any migration guide for bootstrap v3.0.2 to 3.4.1.
If you do decide to go forward to v4 I would recommend going straight to v5 instead, the latest version. It is a lot more stable with not as much JS (even though v4 was very good).
v4 and v5 are not that different really, but the differences between v3 and v4 are huge. Most of the time this is coming down to the way attributes are detailed. In v3 navbar for example two of the attributes were data-toggle and data-target. From v4 onwards these became data-bs-toggle and data-bs-target.
I suspect those changes will be the biggest thing to do, otherwise it might not take as long as you think.
I moved to Bolt 4 (from Bolt 3.7) and would like to implement front-end user to give them access to private contents of the website. Previously, I used the extension BoltAuth/Auth, which worked like a charm.
Now in Bolt 4, there is no easy way like in Bolt 3.x to install an extension from the back-end page. I found out I could use composer to do so, but I run in the following problem:
> composer require "boltauth/auth:3.0.1"
[InvalidArgumentException]
Could not find a matching version of package boltauth/auth. Check the package
spelling, your version constraint and that the package is available in a stability
which matches your minimum-stability (stable).
Either I do something wrong, or the extension is not compatible with Bolt 4.1.
Could someone tell me if there is a way to make this extension work? Or alternatives for front-end user management?
EDIT: I'm now using the bolt/users extension as it can be used to add a ROLE_MEMBERS and let users login for the frontend.
Yes, unfortunately the architecture for plugins (mainly driven by the move from Silex to Symfony) changed completely between 3.x and 4.x and it's not really feasible to release new 4.x compatible versions.
So for now there won't likely be updates to BoltAuth. It may be worth joining the Slack community and seeing if any other developers are working on 4.x compatible solutions to the client login scenarios.
This question is about the usage of jhipster-generator.
I noticed that the react support (namely generator-jhipster-react) has been merged into generator-jhipster, but I found no guide on how to generate react projects by generator-jhipster.
Could anyone identify how to create react projects with generator-jhipster?
As of today (2017-11-23) this has just been merged into the master branch, so you can use it by using the project directly from GitHub.
This should be released very soon, as it will be included in our next version 4.11.0. As this is still in development, you will need to run it with the --experimental flag. This will be documented in the release notes (this is a new flag).
I have just updated my project to work with Angular 5, and I have got a NodeJS setup on my hosting so I want to create an Angular Universal Application, I would like to convert my current Angular 5 project into a working Angular Universal project that I can setup on my hosting.
The only thing I found on this so far is this;
Convert Angular 4 web app to Angular Universal app
I followed this and It gave me errors, I imagine due to the quick changing nature of Angular that the answer is most likely outdated, so I was wondering the best way to convert it.
Should I just use the starter seed and do the tedious work of adding all my code?
The best way to do this for me personally was add in all my components, services, modules into the universal-starter project, ensure I remove hammerjs or import it properly (for Material 2). I converted most of my components to have .module so I could use their lazy loading (not forgetting to add these paths properly in my routing file and in the static lazy loading path)
It only took a few hours and alot of that was just bug testing/fixing so it was pretty easy all in all.
I had the same issue several weeks ago. There is a Wiki on how to implement Universal into an Angular CLI project : https://github.com/angular/angular-cli/wiki/stories-universal-rendering
Maybe that helps you out.
I found it the easiest to take the current Angular Universal Starter Kit and import all my Modules into a fresh installation. As the new starter is for Angular 5 CLI I hope it's future proof. We will see…
I wrote a starter kit for MEAN applications with Angular Universal for Angular 5 and you can clone my repository at GitHub here: https://github.com/Stanza987/mean-starter-kit. It provides all the instructions you need to get started. For your specific app, you can just delete the MongoDB part (Mongoose and the out of server.js, node_src/config/database) and npm uninstall mongoose and be able to integrate your project in.
Im use a Elasticsearch 5.1.2 (docker installation) and integrated with a project generated with jHipster 4.0.2.
After configure Elasticsearch, Elastic show the message:
java.lang.IllegalStateException: Received message from unsupported version: [2.0.0] minimal compatible version is: [5.1.2]
sn_elasticsearch |
Its posible to upgrade the client version of Spring Data Elastic integration in jHipster project? Someone knows how to?
[]s
spring-data-elasticsearch does not support version 5 yet. It is a work in progress by a team of volunteers (not driven by the Spring Data team).
According to the latest post on GitHub where you can track the issue:
Given that we will look into upgrading elasticsearch to latest version and as #olivergierke suggested it will be released with Kay if we will be able to merge changes before RC1 which is in mid March [2017].
This pull request still require major week or two of a work, its not straight forward merge. We are independent resource(s) willing to contribute on this project wherever we can, anyone who is willing to do the same is more than welcome to contribute.
We will keep posting update from our side about upgrade on the same thread.