Fix/docker frontend startup#8
Open
OmBharti999 wants to merge 4 commits intohyepartners-gmail:mainfrom
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #7
Title
Fix frontend Docker setup and resolve ESM
requireerrorDescription
The frontend Docker build was failing due to multiple issues:
package.jsonandpnpm-lock.yamlwere out of sync.ffmpeg-frontendfolder path was missing in the Docker configuration.require, which caused the error:ReferenceError: require is not defined in ES module scope.Changes Made
package.jsonandpnpm-lock.yaml.ffmpeg-frontendfolder path in Docker configuration.requireusage with ES module compatible imports.Scope
This PR focuses on fixing the frontend Docker environment and module compatibility issues to ensure the container builds and runs successfully.
Testing
Rebuilt containers using:
Verified the frontend container starts correctly.
Confirmed the ESM
requireerror no longer occurs.Logs / Screenshots
Attached logs showing: