Client compile errors with uaa

UAA
1

Hello. I have recently updated to the 2023.06 ext4 update and now get following problems when compiling the client:

uaa-dependency-errors
uaa-dependency-errors1938×143 11.7 KB

I am using the uaa-authentication-client of version 7.3.3. Is this issue known? What am i doing wrong?

2

Hi @nick-linked-tensor,

It’d be really helpful if you could provide your package json.

3

Hi, here is my current package.json:

package.json (4.7 KB)

4

The last error could be fixed by running npm i @types/crypto-js as it suggested. The rest still remains.

5

Hi @nick-linked-tensor,

My npm setup is against mgm internal artifactory.

Following these steps, I tried reproducing it in the current project template but could not.

  1. Get your packagejson located in template/client
  2. Remove node_modules
  3. Execute npm install, then npm compile. In addition, npm start is also working

The differences might be in the tsconfig, I’m not sure. Could you please check?

6

Hi @loi-risen-dale, I already tried deleting the node_modules folder and executed npm install but i did not execute a npm compile. I will give this a try. In the meanwhile here is our tsconfig file: tsconfig.json (508 Bytes)

The artifactory setup should work identical to the mgm internal artifactory but I could still double check this with DevOps.

If there are any problems with the tsconfig please tell me. In the meantime i will try your provided steps.

7

Ok I tried the steps and it concludes to the same error message when executing npm compile. npm start also shows both errors when it is finished starting. We did not have this problem with our versions prior to the workflows rework. Could this be a cause?

9

Hi,

I tried out with your tsconfig (with a change "jsx": "react"), the npm compile:typescript is succeeding still. Quite hard to determine where’s issue is because we did not run against the same code base.

I think it shouldn’t be the case but uaa-authentication-client ext4 is 7.4.1, as successfully integrated into the project template.

I’ll forward this question to UAA if they have any ideas.

10

I am a UAA member. I have tested the uaa-authentication-client version 7.3.3 with our example code, and everything is working well. Which previous version did you use?

11

To my knowledge the 7.3.3 version was our previous version where it worked fine. I upgraded the version to 7.4.1 and the error still remains. Even switching back to the old working version throws the error which is odd.

12

I think you need to try ‘Invalidate Caches’ if you’re using IntelliJ since it seems a bit weird. I tried reproducing with 7.3.3 and 7.4.1 but have no error

13

Hi @luc-nimble-cedar, I tried a lot of stuff now and the Fullstack-Template does work correctly with that version. Using the mgm-artifactory results in the same error.

When i oben the folder in node_modules i get an error in the tsconfig of uaa-authentication-client that looks like this: “Cannot find type definition file for ‘node’.
The file is in the program because:
Entry point of type library ‘node’ specified in compilerOptions”

Could this be somewhat causing the error? If not could there be a part of our code that causes it?

14

I am going to answer my own question: Yes it had to do with the code. In one of our components there were imports that directly referenced the internal files of the uaa library. This caused the errors. Removing the imports and adding the correct ones fixed it.

Thank you guys really much for the swift help :smiley: