5 ms·
I'm slightly confused, what is the use case for this? It says "no npm, babel, etc" but then it goes and downloads the packages for you.
by fokinsean 9y ago
I'm slightly confused, what is the use case for this? It says "no npm, babel, etc" but then it goes and downloads the packages for you.
- kevan 9y agoLots of places are Java™ shops, and adding new shiny stuff from the NodeJS ecosystem for frontend work can be difficult. I couple years ago I had to build a weird multi-step build bridge between babel and the Grails asset pipeline. A pure JVM implementation would probably make this sort of thing less painful for a lot of companies.
- deleted 9y ago[deleted]
- fokinsean 9y agoAh ok, so this makes it easier to integrate react into the view layer for a traditional java mvc application is that right?
- kevan 9y agoYep, lowers the entry barrier to add it to a project. I think most of the modern frameworks have decent support out of the box but for projects started a decade ago it's useful
- sbergot 9y agoIt is "npmless" ;-)
- moru0011 9y agoIt's not only npm, its also jsx transpilation, bundling (incl. a shim of npm, es6 imports and html-imports) and java-javascript interfacing.