Add support for Grunt about sbt-web HOT 8 CLOSED

+1

from sbt-web.

+1

from sbt-web.

+1

from sbt-web.

Ok, I get the idea. :-) Please no more +1 comments as they pollute the issue.

Of course, community contributions are also most welcome. :-) If anyone would like to talk about this design of this that I have in mind then please ping me.

from sbt-web.

I don't want to further pollute this topic, but I'm very curious in this integration. We broke away from the standard play framework build route a long time ago. Our configuration looks a little more like this now:
my-play-app
-client-app (sub-folder for our custom front-end SPA and all of the assets)
-public (nothing in it by default)
-.... (all the other play project root level folders)

During our Jenkins build processes, the first step runs npm install inside of the client-app folder, then runs the grunt task to build & unit-test our front-end SPA. The output of the grunt job saves the built files out to the public folder, then sbt runs the compile & build on the next build step so that the play app has the statically built assets.

Long-term, I would be interested in seeing if sbt-web matures to a point where these steps could essentially be executed by SBT itself so I don't have to break apart the build process for npm and grunt from the build steps to run the app itself. I could probably do this myself with my own sbt task using a Process, but a higher level grunt integration would be more awesome.

Thanks for the good work!

from sbt-web.

Isn't that those technologies are mutually exclusive, if there is grunt + plugins sbt-web + plugins makes no sense? I am not suprised Christopher may be a bit reluctant to work on that.

For big companies quite often there is separation of front-end and backend devs and at the moment teaching them scala or sbt-web is out of most people scopes. Grunt being js based with many plugins in ecosystem is leading the way, to me that does not mean sbt-web makes no sense but rather than one needs to be patient and hope community in large numbers of folks picks that up.

from sbt-web.

During our Jenkins build processes, the first step runs npm install inside of the client-app folder, then runs the grunt task to build & unit-test our front-end SPA. The output of the grunt job saves the built files out to the public folder, then sbt runs the compile & build on the next build step so that the play app has the statically built assets.

We already have support for npm so by just having a package.json at the root of your sbt project is sufficient i.e. it will update the dependencies automatically.

Long-term, I would be interested in seeing if sbt-web matures to a point where these steps could essentially be executed by SBT itself so I don't have to break apart the build process for npm and grunt from the build steps to run the app itself. I could probably do this myself with my own sbt task using a Process, but a higher level grunt integration would be more awesome.

What are your requirements in terms of plugins i.e. what do you need?

Isn't that those technologies are mutually exclusive, if there is grunt + plugins sbt-web + plugins makes no sense? I am not suprised Christopher may be a bit reluctant to work on that.

I'm not reluctant to work on this, it is just a question of priorities. There are not enough hours in the day of course. :-)

from sbt-web.

This isn't an sbt-web issue, if someone wants to provide an sbt-grunt that integrates with sbt-web then that's fine but sbt-web itself doesn't need to be modified for sbt-grunt.

If you're using Play Framework, then I would recommend not using sbt-web at all if you're using grunt, instead, just use grunt as shown here:

https://www.playframework.com/documentation/2.6.x/SBTCookbook

from sbt-web.