Unable to compile client app on Heroky #1543

NelsonEU · 2023-06-12T08:38:36Z

NelsonEU
Jun 12, 2023

Hello,

I've just started using this gem for a new project, but I face an issue when deploying to Heroku.

My app is split between a client-bundle and a server-bundle (SSR). On local, I don't face any issue but on Heroku I cannot get the client-app to work, while the SSR one does.

In the logs, we can see that the compilation failed:


[Shakapacker] Compiling...
[Shakapacker] 
COMPILATION FAILED:
EXIT STATUS: pid 71 SIGABRT (signal 6)
OUTPUTS:
Loading ENV specific webpack configuration file /app/config/webpack/production.js
[React on Rails] Creating both client and server bundles.
<--- Last few GCs --->
[71:0x5cd24f0]     9372 ms: Scavenge 248.9 (257.7) -> 248.4 (258.0) MB, 0.61 / 0.00 ms  (average mu = 0.128, current mu = 0.021) allocation failure; 
[71:0x5cd24f0]     9374 ms: Scavenge 249.1 (258.0) -> 248.4 (258.2) MB, 0.49 / 0.00 ms  (average mu = 0.128, current mu = 0.021) allocation failure; 
[71:0x5cd24f0]     9471 ms: Mark-Compact 249.2 (258.2) -> 245.5 (258.5) MB, 96.20 / 0.00 ms  (average mu = 0.220, current mu = 0.393) allocation failure; scavenge might not succeed
<--- JS stacktrace --->
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
 1: 0xc8d700 node::Abort() [webpack]
 2: 0xb6b8f3  [webpack]
 3: 0xeac370 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [webpack]
 4: 0xeac657 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [webpack]
 5: 0x10bdcc5  [webpack]
 6: 0x10be254 v8::internal::Heap::RecomputeLimits(v8::internal::GarbageCollector) [webpack]
 7: 0x10d5144 v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::internal::GarbageCollectionReason, char const*) [webpack]
 8: 0x10d595c v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [webpack]
 9: 0x10abc61 v8::internal::HeapAllocator::AllocateRawWithLightRetrySlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [webpack]
10: 0x10acdf5 v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [webpack]
11: 0x108a366 v8::internal::Factory::NewFillerObject(int, v8::internal::AllocationAlignment, v8::internal::AllocationType, v8::internal::AllocationOrigin) [webpack]
12: 0x14e5196 v8::internal::Runtime_AllocateInYoungGeneration(int, unsigned long*, v8::internal::Isolate*) [webpack]
13: 0x191cef6  [webpack]
I, [2023-06-09T14:38:39.215615 #2]  INFO -- : [ebed93eb-574f-45b3-9cd3-f86438d5dab6]   Rendered layout layouts/client.html.erb (Duration: 10319.8ms | Allocations: 3480)
I, [2023-06-09T14:38:39.215809 #2]  INFO -- : [ebed93eb-574f-45b3-9cd3-f86438d5dab6] Completed 500 Internal Server Error in 10393ms (ActiveRecord: 31.1ms | Allocations: 35843)
F, [2023-06-09T14:38:39.216302 #2] FATAL -- : [ebed93eb-574f-45b3-9cd3-f86438d5dab6]   
[ebed93eb-574f-45b3-9cd3-f86438d5dab6] ActionView::Template::Error (Shakapacker can't find client-bundle.js in /app/public/packs/manifest.json. Possible causes:
1. You forgot to install node packages (try `yarn install`) or are running an incompatible version of Node
2. Your app has code with a non-standard extension (like a `.jsx` file) but the extension is not in the `extensions` config in `config/shakapacker.yml`
3. You have set compile: false (see `config/shakapacker.yml`) for this environment
   (unless you are using the `bin/shakapacker -w` or the `bin/shakapacker-dev-server`, in which case maybe you aren't running the dev server in the background?)
4. webpack has not yet FINISHED running to reflect updates.
5. You have misconfigured Shakapacker's `config/shakapacker.yml` file.
6. Your webpack configuration is not creating a manifest.
Your manifest contains:
{
}
):
[ebed93eb-574f-45b3-9cd3-f86438d5dab6]     3:   <head>
[ebed93eb-574f-45b3-9cd3-f86438d5dab6]     4:     <title>Sander</title>
[ebed93eb-574f-45b3-9cd3-f86438d5dab6]     5:     <%= csrf_meta_tags %>
[ebed93eb-574f-45b3-9cd3-f86438d5dab6]     6:     <%= javascript_pack_tag 'client-bundle' %>
[ebed93eb-574f-45b3-9cd3-f86438d5dab6]     7:     <%= stylesheet_pack_tag 'client-bundle' %>
[ebed93eb-574f-45b3-9cd3-f86438d5dab6]     8:     <style>
[ebed93eb-574f-45b3-9cd3-f86438d5dab6]     9:       body: {
[ebed93eb-574f-45b3-9cd3-f86438d5dab6]   
[ebed93eb-574f-45b3-9cd3-f86438d5dab6] app/views/layouts/client.html.erb:6

Also saw the suggestions:
1 - Yarn ran
2 - All extensions are included
3 - Compile is set to true for production
4 - Not sure about this one
5 - Looks fine to me, inspired from: https://github.com/shakacode/react_on_rails_demo_ssr_hmr
6 - Manifest looks indeed empty?

Not sure what could have gone wrong here, would greatly appreciate some help for this one.

Thanks!

Answered by ahangarha

Jun 12, 2023

Wait!
Which version of Shakapacker do you use? It seems you are using 7.0.0.rc.0, which has this bug! If you still want to use pre-released version 7, please ensure you use the latest code on the master branch.

We are running the last round of tests before making the final release.

View full answer

ahangarha · 2023-06-12T09:17:26Z

ahangarha
Jun 12, 2023

Please check Shakapacker docs for deployment.

Your production build process is responsible for running yarn install before rake assets:precompile.

Let us know if you still have an issue.

3 replies

NelsonEU Jun 12, 2023
Author

Thanks for your answer! I just had a look, the buildpacks seems well configured & yarn install is running before the precompile task.

-----> Using buildpacks:
       1. heroku/nodejs
       2. heroku/ruby

-----> Installing dependencies
       Installing node modules (yarn.lock)
       yarn install v1.22.19

-----> Preparing app for Rails asset pipeline
       Running: rake assets:precompile
       Asset precompilation completed (1.57s)
       Cleaning assets
       Running: rake assets:clean

ahangarha Jun 12, 2023

Wait!
Which version of Shakapacker do you use? It seems you are using 7.0.0.rc.0, which has this bug! If you still want to use pre-released version 7, please ensure you use the latest code on the master branch.

We are running the last round of tests before making the final release.

Answer selected by NelsonEU

justin808 Jun 14, 2023
Maintainer

rc.1 is out

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

Unable to compile client app on Heroky #1543

Uh oh!

{{title}}

Uh oh!

Replies: 1 comment 3 replies

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

Uh oh!

Unable to compile client app on Heroky #1543

Uh oh!

NelsonEU Jun 12, 2023

Replies: 1 comment · 3 replies

Uh oh!

Uh oh!

ahangarha Jun 12, 2023

Uh oh!

NelsonEU Jun 12, 2023 Author

Uh oh!

ahangarha Jun 12, 2023

Uh oh!

justin808 Jun 14, 2023 Maintainer

NelsonEU
Jun 12, 2023

Replies: 1 comment 3 replies

ahangarha
Jun 12, 2023

NelsonEU Jun 12, 2023
Author

justin808 Jun 14, 2023
Maintainer