Skip to content

docker compose build --no-cache failing on frontend build step after cookiecutter generation #58

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
chtnnh opened this issue Jan 9, 2025 · 7 comments
Assignees

Comments

@chtnnh
Copy link

chtnnh commented Jan 9, 2025

Screenshot 2025-01-09 at 19 31 41

I was following the instructions here and reached the docker compose build --no-cache step, but the command fails with the above error.

Unsure why it's reacting to an OR like that

Any help fixing this would be great, maybe I've made a mistake in the cookiecutter step

@chtnnh
Copy link
Author

chtnnh commented Jan 9, 2025

The same error is in 4 files in total:

/frontend/app/components/settings/Profile.tsx
/frontend/app/components/settings/Security.tsx
/frontend/app/login/page.tsx
/frontend/app/reset-password/page.tsx

changing case 'minLength' || 'maxLength': to case 'minLength': ... case 'maxLength': ... works in building without an error

@dotone-101
Copy link

I am facing the exact same error.
Kindly share any resolution or workaround to this.
I am using M2 Mac.

12.38  ⨯ ESLint: Invalid Options: - Unknown options: useEslintrc, extensions - 'extensions' has been removed.
15.11 Failed to compile.
15.11 
15.11 ./app/login/page.tsx:29:10
15.11 Type error: This kind of expression is always truthy.
15.11 
15.11   27 |     case "required":
15.11   28 |       return <div className={style}>This field is required.</div>;
15.11 > 29 |     case "minLength" || "maxLength":
15.11      |          ^
15.11   30 |       return (
15.11   31 |         <div className={style}>
15.11   32 |           Your password must be between 8 and 64 characters long.
15.13 Static worker exited with code: 1 and signal: null
15.15 npm notice
15.15 npm notice New major version of npm available! 10.8.2 -> 11.0.0
15.15 npm notice Changelog: https://github.com/npm/cli/releases/tag/v11.0.0
15.15 npm notice To update run: npm install -g [email protected]
15.15 npm notice
------
failed to solve: process "/bin/sh -c npm run build" did not complete successfully: exit code: 1

@chtnnh
Copy link
Author

chtnnh commented Jan 16, 2025

The same error is in 4 files in total:

/frontend/app/components/settings/Profile.tsx
/frontend/app/components/settings/Security.tsx
/frontend/app/login/page.tsx
/frontend/app/reset-password/page.tsx

changing case 'minLength' || 'maxLength': to case 'minLength': ... case 'maxLength': ... works in building without an error

this is the workaround @dotone-101

@YvesleCurseur
Copy link

Hello, someone figure this out ?

@cat0ne
Copy link

cat0ne commented Feb 21, 2025

Hello, the build is not working, I am on Macbook M1.
I am getting this error : failed to solve: process "/bin/sh -c npm run build" did not complete successfully: exit code: 1

I have updated the following files as mentionned:

  • /frontend/app/components/settings/Profile.tsx
  • /frontend/app/components/settings/Security.tsx
  • /frontend/app/login/page.tsx
  • /frontend/app/reset-password/page.tsx

by changing case 'minLength' || 'maxLength': to case 'minLength': / case 'maxLength':

I am also seeing this error upper in the message stream:
13.10 Error: It looks like you're trying to use tailwindcss directly as a PostCSS plugin. The PostCSS plugin has moved to a separate package, so to continue using Tailwind CSS with PostCSS you'll need to install @tailwindcss/postcss and update your PostCSS configuration.

Does someone have a suggestion to make the build complete?

@Jibola
Copy link
Collaborator

Jibola commented Mar 7, 2025

Hey all, this should now be resolved with the merging of #61
Thank you for raising the issue. I will leave this ticket open for a little bit in case someone still reports and error, but if there's no response after some time, I will naturally close it.

@chtnnh
Copy link
Author

chtnnh commented Mar 7, 2025

will try and reproduce tomorrow (will take me some time to dig up my cookiecutter generation input), but will get back when I do! thank you @Jibola

@Jibola Jibola closed this as completed Mar 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants