test: frontend build gh action

[denishacquin]

Fixes #677

What

• added frontend build to gh actions

Why

• to make sure the frontend can build before we merge any branch

Testing done

N/A

Checks

• I have tested this code
• I have reviewed my own PR
• I have created an issue for this PR
• I have set a descriptive PR title compliant with conventional commits

Reviewing tips

User facing release notes

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[denishacquin]

Would this make sense to you @cristiam86 ?

[cristiam86]

Would this make sense to you @cristiam86 ?

yes, it makes sense. But aren't we already running frontend unit tests in the other workflows?

[denishacquin]

Would this make sense to you @cristiam86 ?

yes, it makes sense. But aren't we already running frontend unit tests in the other workflows?

Those are separate. I just ran unit tests locally and they succeed while the build fail.

[cristiam86]

Would this make sense to you @cristiam86 ?

yes, it makes sense. But aren't we already running frontend unit tests in the other workflows?

Those are separate. I just ran unit tests locally and they succeed while the build fail.

Yeah, the build part I get it, but in your action, you are also running the unit test in the front end: https://github.com/yeagerai/genlayer-studio/pull/678/files#diff-99e3486466e938171924bf1a5ede5aed83ee1548ece94123968ede576189e266R35