You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Support asset compilation with node (ex: with webpacker) for Go apps, without the need to specify one of the nodejs buildpacks
Possible Solution
A new go-assets buildpack that wraps some of the existing nodejs BPs (probably everything except for *-start ones), users can then specify the build CMD with BP_NODE_RUN_SCRIPTS
Motivation
It's possible to achieve this by simply including the full nodejs buildpack in a group alongside the go BP, but it'd be nice to be able to specify a single group for our go apps. One could also argue that there's a potential need for doing this for other languages like java and maybe others
The text was updated successfully, but these errors were encountered:
is there a sample application you could provide that demonstrates this Go + nodejs asset compilation use case?
Unfortunately nothing public, even internally we only have one app that has this use case (but a very important one 😅 ).
That app has a "hand rolled" stack, but I do hope to play with https://gobuffalo.io at some point this week and can try to report back with more information.
Describe the Enhancement
Support asset compilation with node (ex: with
webpacker
) for Go apps, without the need to specify one of the nodejs buildpacksPossible Solution
A new
go-assets
buildpack that wraps some of the existing nodejs BPs (probably everything except for*-start
ones), users can then specify the build CMD withBP_NODE_RUN_SCRIPTS
Motivation
It's possible to achieve this by simply including the full nodejs buildpack in a group alongside the go BP, but it'd be nice to be able to specify a single group for our go apps. One could also argue that there's a potential need for doing this for other languages like java and maybe others
The text was updated successfully, but these errors were encountered: