Implicit Dependency Issue in babel-preset-react-app Causes Docker Container Failure on EC2

[choijw1004]

I am experiencing an issue with the babel-preset-react-app package. It appears that this package relies on @babel/plugin-proposal-private-property-in-object without explicitly listing it as a dependency. In my local development environment, this hasn't caused issues because the plugin is present in my node_modules for other reasons. However, this implicit dependency may lead to unexpected problems.

Locally, I resolved the warning by adding @babel/plugin-proposal-private-property-in-object to my devDependencies. Despite this workaround, when I deploy my React project to an AWS EC2 instance using a Docker image built from my repository, the container fails to start. Although the build completes successfully, the application does not run on EC2.

Here is the relevant snippet from my package.json:

json
"devDependencies": {
"eslint-config-prettier": "^8.10.0",
"eslint-plugin-prettier": "^4.2.1",
"prettier": "^2.8.8",
"@babel/plugin-proposal-private-property-in-object": "^7.21.0"
}

Summary:

Locally, with the above devDependencies, everything works fine.
When deploying the Docker container to EC2 without explicitly including @babel/plugin-proposal-private-property-in-object (beyond the local workaround), the application fails to start.
The build succeeds, but the container does not run on EC2.
Could you please provide guidance on why this dependency issue might cause the application to fail on EC2 but not locally, and how to properly resolve it?

Best regards,
Choi Jang-Woo