Closed nyalavarthi closed 3 months ago
Got the latest commits into my fork and now getting different error , i am trying this in two different accounts in two two different regions and have same error in both cases
2024-03-27T16:27:21.901Z [INFO]: # Completed phase: preBuild
# Starting phase: build
2024-03-27T16:27:21.902Z [INFO]: # Executing command: REACT_APP_CONNECT_REGION=${REACT_APP_CONNECT_REGION}
# Executing command: REACT_APP_CONNECT_INSTANCE_ID=${REACT_APP_CONNECT_INSTANCE_ID}
# Executing command: yarn run build
2024-03-27T16:27:22.033Z [INFO]: yarn run v1.22.0
2024-03-27T16:27:22.067Z [INFO]: $ craco build
2024-03-27T16:27:23.196Z [INFO]: Creating an optimized production build...
2024-03-27T16:27:26.825Z [WARNING]: [0;33mOne of your dependencies, babel-preset-react-app, is importing the
"@babel/plugin-proposal-private-property-in-object" package without
declaring it in its dependencies. This is currently working because
"@babel/plugin-proposal-private-property-in-object" is already in your
node_modules folder for unrelated reasons, but it [1mmay break at any time[0;33m.
babel-preset-react-app is part of the create-react-app project, [1mwhich
is not maintianed anymore[0;33m. It is thus unlikely that this bug will
ever be fixed. Add "@babel/plugin-proposal-private-property-in-object" to
your devDependencies to work around this error. This will make this message
go away.[0m
2024-03-27T16:28:16.614Z [INFO]: Failed to compile.
2024-03-27T16:28:16.620Z [INFO]: Attempted import error: '@aws-amplify/auth' does not contain a default export (imported as 'Auth').
2024-03-27T16:28:16.693Z [WARNING]: error Command failed with exit code 1.
2024-03-27T16:28:16.694Z [INFO]: info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
2024-03-27T16:28:16.739Z [ERROR]: !!! Build failed
2024-03-27T16:28:16.739Z [ERROR]: !!! Error: Command failed with exit code 1
2024-03-27T16:28:16.739Z [INFO]: # Starting environment caching...
I have successfully deployed the repo two weeks ago and able to test the solution . and now been trying to redeploy the same repo in a different aws account using amplify web hosting console which is the exact same process. I also tried the latest version of the repo and below is the error in both cases.