The Bun runtime was causing react-scripts build to fail silently during the Docker build process. The build would hang at 'Creating an optimized production build...' and never complete, resulting in an incomplete build directory with only public assets (favicon, logos, manifest) but no compiled JS/CSS bundles. Changes: - Changed builder base image from oven/bun:1-alpine to node:20-alpine - Changed install command from 'bun install' to 'npm ci' - Changed build command from 'bun run build' to 'npm run build' - Fixed health check from wget to curl (wget not available in Alpine) Result: - React build completes successfully with 'Compiled successfully' message - Build directory now contains: - index.html (753 bytes - React build) - asset-manifest.json - static/js/ and static/css/ directories with compiled bundles - Frontend serves the React application correctly Tested: Frontend accessible at http://app.adopt-a-street.192.168.153.241.nip.io showing the Adopt-a-Street React application. 🤖 Generated with AI Assistant Co-Authored-By: AI Assistant <noreply@ai-assistant.com>
Getting Started with Create React App
This project was bootstrapped with Create React App.
Available Scripts
In the project directory, you can run:
bun start
Runs the app in the development mode.
Open http://localhost:3000 to view it in your browser.
The page will reload when you make changes.
You may also see any lint errors in the console.
bun test
Launches the test runner in the interactive watch mode.
See the section about running tests for more information.
bun run build
Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.
The build is minified and the filenames include the hashes.
Your app is ready to be deployed!
See the section about deployment for more information.
bun run eject
Note: this is a one-way operation. Once you eject, you can't go back!
If you aren't satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.
Instead, it will copy all the configuration files and the transitive dependencies (webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you're on your own.
You don't have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn't feel obligated to use this feature. However we understand that this tool wouldn't be useful if you couldn't customize it when you are ready for it.
Learn More
You can learn more in the Create React App documentation.
To learn React, check out the React documentation.
Code Splitting
This section has moved here: https://facebook.github.io/create-react-app/docs/code-splitting
Analyzing the Bundle Size
This section has moved here: https://facebook.github.io/create-react-app/docs/analyzing-the-bundle-size
Making a Progressive Web App
This section has moved here: https://facebook.github.io/create-react-app/docs/making-a-progressive-web-app
Advanced Configuration
This section has moved here: https://facebook.github.io/create-react-app/docs/advanced-configuration
Deployment
This section has moved here: https://facebook.github.io/create-react-app/docs/deployment
bun run build fails to minify
This section has moved here: https://facebook.github.io/create-react-app/docs/troubleshooting#bun-run-build-fails-to-minify