i installed jhipster 6 and everything is working fine. but when i generate entities, translations are not available on the frontend though the translation files are there.
on the entity page i get something like : translation-not-found[blogApp.tag.home.title]
i found a solution to the issue! the generator and the app version were not the same.
when you type jhipster info, you get the version of the generator and when you type jhipster you get the app version.
Both have to be the same. if it's not the same just re-install the generator [ npm i -g generator-jhipster# ]
Related
I am upgrading my application from angular 13 to 14.
For angular 13 everything was working fine but after doing the angular 14 updates I am facing this error and am unable to understand where I am making the mistake.
Node: 14.21.1
enter image description here
I tried to changing "#angular-devkit/build-angular": "^13.3.10" but no luck
Please refer to:
https://github.com/manfredsteyer/ngx-build-plus/issues/361
Your issue seems similar to this one and the resolution would be the same mostly but in case you want to get it fixed by the TPL author
You will have to figure out which TPL is causing the issue run
yarn list #angular-devkit/build-angular
This would tell you which TPL requires the 15 version of angular in your project.
Hope this helps :)
I'm kinda new to strapi. actually this the first time to try it. so i followed the documentation and was able to get the first page to work but admin page always go blank. sadly i don't know nodeJs or react so I'm not sure about what to do in here but seems there's something wrong with the permissions please check the attached image.
i've tried
npm install in the project root directory.
npm run setup in the project root directory.
as mentioned in this issue on github but it want's useful
I'm using
strapi 3 alpha
nodeJs 11
npm 6+
mariaDB 10.1
windows 10 64bit
I suggest you to clean the database your use. And when it's done, restart your Strapi server. It will re-create all table needed by Strapi.
So simply, I checked strapi website to find out that version 3 is out of the alpha status and then I installed the newer version and tried to use it and it did work so seems some bug was in the alpha edition which strapi team has fixed by themselves
I had a similar issue after setting up SSL on Digital Ocean one-click. I just ran npm run build. I did not do anything with the database.
I just generated a project with jhipster normally. I am now trying to use the Bootswatch theme by typing the command npm install -g generator-jhipster-bootswatch and yo jhipster-bootswatch as shown on their website and I have this error:
Unable to find src/main/webapp/app/blocks/config/http.config.js or missing required jhipster-needle. Interceptor not added to JHipster app.
version :
jhipster 4.13.3
Can someone help me solve this problem?
generator-jhipster-bootswatch is 2 years old , its not compatible with Angular 5 in JHipster 4 (see issue)
I am working on ember cli version 1.12 and node js version v0.12.7,I want to intergrate ember-cli-barcode addon.I have tried following:
ember install:npm ember-cli-barcode
Then it will show message that it required node version 4 >.So I have used Node version v7.0.0 stable.I installed node modules and addon.
Then tried following command:
npm install
bower install
ember server
But It will always shows errors,of node-modules etc.Kindly help me for the same how to integrate addon and which file need to change.
This should be a comment but I can't comment yet. I'm the author and it's compatible with Ember 2.4 onward. I will be putting version compatibility information in the readme.
I haven't worked with a cli version this old but ember install should be all you need if it's compatible. The add-on is a really thin wrapper around JsBarcode, so you could use the library direct if you have stay with the current ember version.
To get the benefits of the full ember-cli ecosystem, you'd have to be using the versions that support it. I think that it began in 1.13
As mentioned, it's highly likely that this addon assumes the standard CLI setup. You could ask the author.
Depending on your app complexity, you could do a few different things.
You could use the js library https://github.com/lindell/JsBarcode - (which is what the addon uses)
OR you may want to rewrite the app with the latest and greatest - now. 1.12 is going to be expensive to keep up / and since you've likely figured out how all the logic should work, then writing it again won't be the hardest part. (this sounds fun, right?) - and then use the addon
Which will take longer?
I am trying to set up this repository locally https://github.com/lrdiv/ember-soundcloud and i have come across to this issue with broccoli-emblem-compiler. See the image in attached
From my understanding the broccoli-emblem-compiler is not able to compile my emblem templates and i don't know how i can figure it out.
These are all the steps i have done to install and set up the project with Ember-Cli
ember new soundcloud
ember install:addon ember-cli-coffeescript
ember install:npm broccoli-emblem-compiler
I have deleted the app folder and replace with the project https://github.com/lrdiv/ember-soundcloud that i have cloned
then i have installed the other node modules required
ember install:npm broccoli-static-compiler
ember install:npm broccoli-merge-trees
ember install:npm install body-parser
and at the end i run
ember server , and in my terminal i get that error i have attached.
What can i do now to sort this out? What's really the problem?
I did many things to try to fix this. One was replacing the project broccoli-emblem-compiler with this line in the project settings:
"broccoli-emblem-compiler": "git+https://github.com/cascalheira/broccoli-emblem-compiler.git"
At some time the error went away, I think it was when I used this repository. It is mentioned in the other issues.
I ran into problems with broccoli-emblem-compiler, but just had success with ember-cli-emblem-hbs-printer -
https://github.com/201-created/ember-cli-emblem-hbs-printer
I was able to solve this by specifying a version of emblem.js in my package.json file.
Specifically, I added the following line:
"emblem": "0.3.14"