[Bug]: Fronted build errors in v0.16.4.7

[tomfrenzel]

Bug Description

Building the Fronted in v.0.16.4.7 does not succeed because of build errors

Steps to Reproduce

Steps to reproduce the behavior:

1. run npm run build inside SparkyFitnessFrontend
2. See errors

Expected Behavior

There should not be any errors

Actual Behavior

npm run build

> sparkyfitnessfrontend@0.16.4.7 build
> tsc -b && vite build

src/api/Exercises/exerciseEntryService.ts:254:12 - error TS2304: Cannot find name 'ExerciseProgressData'.

254 ): Promise<ExerciseProgressData[]> => {
               ~~~~~~~~~~~~~~~~~~~~

src/api/Exercises/exerciseEntryService.ts:267:31 - error TS2304: Cannot find name 'ExerciseProgressData'.

267   return response.map((entry: ExerciseProgressData) => ({
                                  ~~~~~~~~~~~~~~~~~~~~

src/pages/Settings/CalculationSettings.tsx:45:38 - error TS2307: Cannot find module '@/hooks/Diary/useDiaryInvalidation' or its corresponding type declarations.

45 import { useDiaryInvalidation } from '@/hooks/Diary/useDiaryInvalidation';
                                        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

src/pages/Settings/CalculationSettings.tsx:73:35 - error TS2304: Cannot find name 'useDailyProgressInvalidation'.

73   const invalidateDailyProgress = useDailyProgressInvalidation();
                                     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~


Found 4 errors.

Additional Context

The build with the main version is working, just the release version is not. I'm not sure how the docker build for the official image could have succeeded building the released version 😄

[CodeWithCJ]

This is fixed and I forget to release a fresh code again

[tomfrenzel]

Yes, i just saw that f3196b2 fixed the issue 👍🏽

I'm not sure how the docker build for the official image could have succeeded building the released version

Just out of interest, how can the image tag in docker hub be 0.16.4.7 but the GH action that pushed the image failed?

[CodeWithCJ]

It's just old. I push next version for my testing frequently specially when I ask others to retest.
And it becomes final when I finally create a release in GitHub

[tomfrenzel]

Alright. Thanks for the clarification 👍🏽

[CodeWithCJ]

plz use next release.

[CodeWithCJ]

I also updated npm to pnpm for frontend. and server and mobile also be switched in the upcoming release. does that impact proxmox script you have setup?

[tomfrenzel]

Yes, the switch makes problems as the script still uses the npm command. But no worries, I'm already implementing the update 😄

[tomfrenzel]

@CodeWithCJ It seems like there a new error:

This is what i see when opening the frontend. Other than that, i get a blank page

The new pnpm ran through fine. Any idea what that could be?

This also happens using the docker-compose.prod.yml