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).
Related
We are using mix of Jenkins & TeamCity pipelines for our Angular projects.
We want to break the build if specific version of node is not used by a project, or specific version(range of version) a library is not used. We want to have precise controls on the versions being used by developers. How to implement such build breaker in the CI/CD pipelines?
We don't have a clue if this is possible. This problem arrived after log4j issue, our teams want to have compliance on versions being used
i will try to give you a little of context.
With my team we are trying to migrate MUI v3 to v4 in a reactJs project. We did it with the project itself and it works! but, some kind of problems came up when we navigated to certain windows that use a certain library to work.
This library was developed by other guy that is not in the company anymore and we are not in touch neither, but, we have access to the library GitHub repository, them are two actually.
https://github.com/rjpizarro/forms
https://github.com/rjpizarro/make-request
i've never had to do this so, i decided to clone the project then install the dependencies and run it.
I'm using nvm so in that moment i was working with node v12 and i got some errors when i executed the npm start ("start": "webpack --watch").
If i use node 10 the scrips runs perfectly but in the entire project we are using node 12 so i'm not sure what is the problem here.
i'm wonder if it could be a problem when i'll try to migrate from MUI v1 to v4 and use the modified library into my project again, or in first place, why its working rigth now?
Anyway i just wanted to know, just if i need it, Could i use different versions of node in a library and then use other newer version into the entire project?
Could this make some negatives effect into my entire project?
Which is the best way to migrate MUI into this library and put it in my project again?
Each nodejs process (including all the modules/libraries it loads) has exactly one version of nodejs running. It isn't possible to have two separate versions of nodejs in the same process each running different parts of the code.
You could make two separate nodejs apps that each run under a different version of nodejs that communicate with each other via some interprocess communication, but they have to be two separate applications/processes.
If you want to run everything in one process (on one version of nodejs), then you will need to test and fix all your libraries to run on that one version of nodejs.
I am building an app in Flutter. I need to make two versions of it - a pro and lite version. I use Android Studio. What would be the best way to maintain two versions of an app, so I don't have to create two different projects and update the code in both projects ?
You could achieve this using Flavors where you can create 2 binaries from the same code base with different app ids. Anotehr way, although not tried myself you can use the flutter tools to create multiple different builds for each platform.
From there you can have 2 entry main files that will be configured for each flavor, main.dart and main_lite.dart. In there you can specify what features are enabled for each one
I ran into a similar issue with an app for work. The solution I am using is to simply have a singe project for both apps but a special gitHub branch for the 2nd app.
So for instance my main app is on master and the 2nd app is on the second_app branch.
When I make a significant change, I make sure to merge it in master first.
And then I just git merge master into second_app.
So, it's not 100% automatic, but it works fine for most cases. And you have the whole git merge workflow at your disposal so you can easily resolve conflicts when you merge.
I currently have a React based website. I want to start on the process of converting the website to also work natively through react-native. I understand that I will need to re-build the UI for the native version.
My goal however is to leave both versions in the same node project so I dont have to update my non-view based code separately for both versions of the code base.
Is it possible to add the dependencies and files necessary for react native while not having to separate the native code out into it's own completely separate project and if so how?
Lerna is a tool that optimizes the workflow around managing multi-package repositories with git and npm.
I am using the React native 0.57.8 but React native navigation Version is: 1.1.471
but the current version for React native navigation is: 2.20.2
May I know which version for React native navigation I have to install for upgrade My Application already on live but I want to upgrade the React native navigation not sure which version I have to use.
Please suggest
That's not a coding question though, but whatever I am explaining will be applicable for all the updations of libraries anyone wants to do.
Just go through with the Release notes, check with the new
functionalities added or older functionalities deprecated. After
updating, a thorough check of your app will be required to check with
the flows. Create a separate branch and work over that, if all works
fine, merge it with your primary branch and push the app for update