-
Notifications
You must be signed in to change notification settings - Fork 91
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
Migrate build tooling to PNPM and NX #246
Comments
@NipuniBhagya, I would like to work on this issue. Could you please assign it to me? |
Hi @abhiram6121 , just assigned the issue to you. Please feel free to get back if there's anything to clarify. |
Do we need Lerna after migrating to PNPM? |
No, we don't. |
@abhiram6121 I updated the issue description to add integrating Changesets[1] to the task list. Please let me know if there are any concerns. Cheers! |
I am facing an error related to ES lint while building |
Did you attempt to update the eslint version? latest eslint version (v9) has some breaking changes that can cause existing eslint configs to break. Better if you can open a draft PR with your current changes so far, so that I can take a look and help. |
I tried downgrading the eslint version, but still getting the same error. PR : #255 |
@abhiram6121 I tried with your changes in the draft PR and sample app build worked for me. Try the following steps and see if it fixes the issue.
|
I am still getting the same error. I even tried recloning the repo from here. I am using Volta to install PNPM and node. Does that cause any issues? |
|
Resolved eslint error, but getting a new error related to jest. |
|
Is your feature request related to a problem? Please describe.
The current monorepo build tooling relies on Yarn, which, while effective, does not offer the same performance optimizations, workspace management, and task orchestration provided by newer tools like PNPM and NX. Additionally, the current release process lacks automation for managing versioning and changelogs, which can be improved with Changesets. As the project scales, upgrading the tooling will enhance the development workflow and ensure smoother releases.
Describe the solution you would prefer
We propose migrating the build tooling to use PNPM for efficient package management, NX for optimized build performance and task orchestration, and Changesets for automated versioning and changelog generation. The migration will include:
Additional context
This migration will involve updating developer documentation and ensuring all workflows operate seamlessly with the new tools. The transition is aimed at improving developer experience, build efficiency, and release management.
The text was updated successfully, but these errors were encountered: