Vite runs on development but fails on production

[rockwellll]

• I have tried upgrading by running bundle update vite_ruby.
• I have read the troubleshooting section before opening an issue.

Description 📖

Hi, hoping you're having a good day. I've setup vite-rails for my application. Everything runs okay in development, however, when pushing the app to production. The build fails and i get this error,

ViteRuby::MissingEntrypointError
Vite Ruby can't find entrypoints/application.js in public/vite/manifest.json or public/vite/manifest-assets.json.

Possible causes:
  - The file path is incorrect.
  - The file is not in the entrypoints directory.
  - Some files are outside the sourceCodeDir, and have not been added to watchAdditionalPaths.
  - You have not run `bin/vite dev` to start Vite, or the dev server is not reachable.
  - "autoBuild" is set to `false` in your config/vite.json for this environment.

Visit the Troubleshooting guide for more information:
  https://vite-ruby.netlify.app/guide/troubleshooting.html#troubleshooting

I have read everywhere on the documentation but could not solve this. Anything would really help.

Thank you

[ElMassimo]

Hi Ahmed!

The build fails

Please provide a trace of how the build fails. In most deployment configurations, if the build step fails, the deployment would be aborted.

and i get this error

Based on the error message, it looks like vite:build (or assets:precompile) was not run on deployment.

If the build actually run and failed, the error message would explicitly mention The last build failed.

Verify that public/vite exists and contains the expected files (manifest.json and an assets dir).

[rockwellll]

Hi, thank you for your fast response! Much needed!

We're using a Dockerfile that runs asset:precompile and deployed using K8.'

Please provide a trace of how the build fails. In most deployment configurations, if the build step fails, the deployment would be aborted.

The pods are deployed but never started because of the error above. Sorry, i did not understand your question.

Verify that public/vite exists and contains the expected files (manifest.json and an assets dir).

I've been looking into it and there's a public/vite-dev directory but no public/vite. I tried running the command bin/vite build inside the pod and i got this error,

<--- JS stacktrace --->

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
 1: 0xa3ad50 node::Abort() [node]
 2: 0x970199 node::FatalError(char const*, char const*) [node]
 3: 0xbba90e v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [node]
 4: 0xbbac87 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [node]
 5: 0xd76ea5  [node]
 6: 0xd77a2f  [node]
 7: 0xd8586b v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [node]
 8: 0xd8942c v8::internal::Heap::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [node]
 9: 0xd57b0b v8::internal::Factory::NewFillerObject(int, bool, v8::internal::AllocationType, v8::internal::AllocationOrigin) [node]
10: 0x10a02b0 v8::internal::Runtime_AllocateInOldGeneration(int, unsigned long*, v8::internal::Isolate*) [node]
11: 0x1449379  [node]

pid 50 SIGABRT (signal 6) (core dumped)
Build with Vite failed! ❌

[ElMassimo]

there's a public/vite-dev directory but no public/vite

Verify that RAILS_ENV is production when precompiling assets for the Docker image.

Vite Ruby will not create public/vite-dev if you are building for production.

[rockwellll]

I ran the bin/vite build command on dev and it successfully generated a public/vite directory

[rockwellll]

Verify that RAILS_ENV is production when precompiling assets for the Docker image.

Vite Ruby will not create public/vite-dev if you are building for production.

Thanks for this note! Indeed, we were not running the command in production mode.