Replies: 2 comments 6 replies
-
yes on removing node modules and maybe all your JS code that got processed by webpack no on removing the ruby gem I hope that helps! |
Beta Was this translation helpful? Give feedback.
2 replies
-
Ah sry but could I delete it from the gem bundle?
…On Tue, Jul 23, 2024, 5:19 AM Justin Gordon ***@***.***> wrote:
the gem is not in the bundles produced by webpack
—
Reply to this email directly, view it on GitHub
<#1643 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAKS5N6ITLQUIGPANFPLDHTZNYNYXAVCNFSM6AAAAABLA4SFGKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAMJSGQYTOMY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm new to all of this - so I apologize if this question is rather naive...
But our prod environment is containerized, and part of that build is to call
rake assets:precompile
, which I hear also calls webpack compilation. Is it possible, to save space, for us to get rid of the node_modules after assets are compiled? And is there any possibility that, after that, there might even be the potential to strip out the react_on_rails gem from bundle (so that we don't need to have execjs / node.js installed in the container as well)?Beta Was this translation helpful? Give feedback.
All reactions