Skip to content
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

build: update Nx 19 & other dependencies #811

Merged
merged 45 commits into from
Dec 9, 2024
Merged

build: update Nx 19 & other dependencies #811

merged 45 commits into from
Dec 9, 2024

Conversation

vmasek
Copy link
Collaborator

@vmasek vmasek commented Sep 4, 2024

closes #771
closes #776
closes #835

@vmasek vmasek added the 🌊 Nx Nx related issues label Sep 4, 2024
@vmasek vmasek self-assigned this Sep 4, 2024
@vmasek
Copy link
Collaborator Author

vmasek commented Sep 4, 2024

Investigation of failing CI in progress 👀

@vmasek vmasek force-pushed the nx-19-update branch 4 times, most recently from f30595f to 6e16658 Compare September 5, 2024 18:27
@vmasek vmasek force-pushed the nx-19-update branch 3 times, most recently from cd2ca75 to b3dd03d Compare September 6, 2024 18:02
@github-actions github-actions bot removed the 🧩 core label Sep 6, 2024
@vmasek vmasek force-pushed the nx-19-update branch 2 times, most recently from 9218855 to b994b9f Compare September 6, 2024 18:45
@github-actions github-actions bot removed 📖 Project documentation improvements or additions to the project documentation 🧩 utils labels Sep 6, 2024
@vmasek vmasek force-pushed the nx-19-update branch 3 times, most recently from d0422c3 to 537362d Compare December 8, 2024 16:22
Copy link
Collaborator

@BioPhoton BioPhoton left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we really need to touch all imports in the code base to migrate to nx v19?

I would really want to avoid this.

@vmasek
Copy link
Collaborator Author

vmasek commented Dec 9, 2024

Do we really need to touch all imports in the code base to migrate to nx v19?

I would really want to avoid this.

I know it is quite big change but is seems like the best direction we could go.
We are dropping a bundler and going for pure TS compilation getting errors more streamlined (accurate) and consistent import behavior.

@vmasek vmasek merged commit 9099514 into main Dec 9, 2024
16 checks passed
@vmasek vmasek deleted the nx-19-update branch December 9, 2024 13:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Don't bundle build output reduce dependencies ci: migrate to Nx 19
3 participants