JHipster Lite demo video

[Julien Dubois]

Hi everyone!

I know this mailing list is public, and this is mostly for Pascal & Colin, but the more feedback I get, the better… Please just don’t publicise this too much, as I’m doing this to prepare for Devoxx next week.

So I’ve made this 35-minute videos about JHipster Lite, and I would appreciate your comments. It’s a private link, and I’ll make it public after Devoxx, if you find it good of course!

https://youtu.be/dTzGQNOKWug

Thank you for your feedback!

Julien Dubois

[Anthony Viard]

Hi Julien,

The video is private so we can't access it. You should change the visibility to "unlisted", only people with the link can then watch it. 

--
You received this message because you are subscribed to the Google Groups "JHipster dev team" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jhipster-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jhipster-dev/9AA547B8-BFB6-475D-8955-D0742FB8DEDC%40gmail.com.

[Julien Dubois]

Oh this is so bad, I thought the private link would work!!

I just put it to “unlisted”, it should be good now, thank you!

[Anthony Viard]

It works!

Yes private is for your own usage only.

It could be great if we can have an animated intro we could reuse for several different JHipster videos.

[Frederik Hahne]

Nice video, cool to see the progress jh lite has made. Btw, while coding the nei4j part. It seems there is problem with m1/arm64. I can do maven package/npm install in jh lite. Did anyone have similar issues? I worked once, because I already did run it locally, but I think it was before the new module dependency view/ui.

--

[Julien Dubois]

I just made it public, as the feedback looked good, RT appreciated at https://twitter.com/juliendubois/status/1577192349805023232 :-)

[Pascal GRIMAUD]

Hello Julien,

Thanks a lot for this great video, love it!

Here are some minor comments:

- some other differences with generator-jhipster:

  - Java 17 by default (vs Java 11)

  - Vue 3 (vs Vue 2), JHLite itself used Vue 3 + Vite

  - Svelte (vs Blueprint)

- you could show the difference between compacted / extended mode, which give more details on each module

- when running tests in IntelliJ, just run with coverage instead, so you can show it's 100% coverage. Why ? Because each module / each commit is too small and it's not hard to keep the high quality for the new code

- if you want to go further, just select the sonar module, start the sonar instance and run the analysis

- when talking about Hexagonal Arch, it's important to mention the domain is not the same domain used in classic generator-jhipster. The domain in JHLite is used to code your business code there, and it does not depend on any framework

- for contributors, as each module is small, it's easy to add a new feature and will not impact the other existing ones

- it would be easy to have the same approach to add quarkus, micronaut and so on...

Have a nice day,

Pascal

[Frederik Hahne]

Of course it should be I can't do npm install with following error:

m ERR! npm ERR! code ETARGET
npm ERR! npm ERR! notarget No matching version found for node-dar...@16.17.0.
npm ERR! npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! npm ERR! notarget a package version that doesn't exist.
npm ERR!
npm ERR! npm ERR! A complete log of this run can be found in:
npm ERR! npm ERR!     /Users/frederik.hahne/.npm/_logs/2022-10-04T07_40_56_586Z-debug-0.log
npm ERR! node:internal/modules/cjs/loader:959
npm ERR!   throw err;
npm ERR!   ^
npm ERR!
npm ERR! Error: Cannot find module 'node-bin-darwin-arm64/package.json'
npm ERR! Require stack:
npm ERR! - /Users/frederik.hahne/git/github/jhipster/jhipster-lite/node_modules/node/installArchSpecificPackage.js
npm ERR!     at Function.Module._resolveFilename (node:internal/modules/cjs/loader:956:15)
npm ERR!     at Function.resolve (node:internal/modules/cjs/helpers:108:19)
npm ERR!     at ChildProcess.<anonymous> (/Users/frederik.hahne/git/github/jhipster/jhipster-lite/node_modules/node-bin-setup/index.js:19:27)
npm ERR!     at ChildProcess.emit (node:events:513:28)
npm ERR!     at maybeClose (node:internal/child_process:1093:16)
npm ERR!     at Process.ChildProcess._handle.onexit (node:internal/child_process:302:5) {
npm ERR!   code: 'MODULE_NOT_FOUND',
npm ERR!   requireStack: [
npm ERR!     '/Users/frederik.hahne/git/github/jhipster/jhipster-lite/node_modules/node/installArchSpecificPackage.js'
npm ERR!   ]
npm ERR! }

Removing the package-lock.json helps, but it feels strange having to do this. @matt @julien did you had something similar as you are already on m1 mac?

[Julien Dubois]

Hi Frederik,

Yes you need to do "arch -x86_64 zsh” to force the architecture. I know, it sucks :-)

To view this discussion on the web visit https://groups.google.com/d/msgid/jhipster-dev/CACh2FPS511Uh6P_reqXdqQQhS0WiYDi6V1Ny%2BLYYanKUD0Ak9g%40mail.gmail.com.

[Frederik Hahne]

Haha, thanks! Using fish shell but will try it. As mentioned removing package-lock worked too but not sure what will happen in x86 machines afterwards.

[Vishal Mahajan]

I just got a chance to watch the demo video, and finally understood the UI layout/flow to generate new projects and apply iterative changes :)

Kudos to everyone who contributed to the JH lite project.

Cheers,

Vishal

To view this discussion on the web visit https://groups.google.com/d/msgid/jhipster-dev/CACh2FPS5JaXnNoM7G2SAowXRaG33nZ%2B-T4DHYvGzVKir1L%3Dt8g%40mail.gmail.com.