Replies: 9 comments 11 replies
-
|
interested |
Beta Was this translation helpful? Give feedback.
-
|
Would like to work on this. |
Beta Was this translation helpful? Give feedback.
-
|
@crocmons As this is a big task and I think by collaborating you can do this easily so I would suggest u to collaborate with him |
Beta Was this translation helpful? Give feedback.
-
|
@s2sharpit Hey were u suggesting to migrate css to tailwind css? |
Beta Was this translation helpful? Give feedback.
-
|
@s2sharpit Hey were u suggesting to migrate css to tailwind css? |
Beta Was this translation helpful? Give feedback.
-
|
Yes, Since the current website already utilizes Tailwind CSS, it makes sense to continue using it during the migration process for consistency and a smoother transition. |
Beta Was this translation helpful? Give feedback.
-
|
@s2sharpit Sounds good, but converting this hardcoded CSS into complete Tailwind CSS is quite a hectic task. How can it be done? |
Beta Was this translation helpful? Give feedback.
-
|
Absolutely @rohansx! I'm confident that I can handle the migration process to Next.js and TypeScript, including the gradual refactoring and implementation of Tailwind CSS. I'm also willing to assist in any way possible to ensure a smooth transition. To get started, I kindly request that we create a new branch in the repository specifically for the migration work. This will allow us to work collaboratively without disrupting the main codebase. It's a best practice to separate the migration efforts from the existing code until the process is complete and thoroughly tested. @crocmons and @rohansx, as you are also working on the project, I believe it would be beneficial for us to collaborate on this task. Your expertise and insights will be invaluable during the migration process. Let's coordinate our efforts and ensure a successful migration to Next.js, TypeScript, and TailwindCSS. Once the branch is created, we can begin by adding the code for the Next.js migration that has been completed so far by @crocmons. By doing this, we'll have a clear starting point and can continue building upon it. @rohansx, I kindly request that you add me as a collaborator in the repository on GitHub. This will enable me to contribute directly to the migration process and work seamlessly with the team. Please let me know your thoughts on this plan, and if you have any additional suggestions or considerations. I'm eager to get started and work together to accomplish this migration smoothly. |
Beta Was this translation helpful? Give feedback.
-
|
@s2sharpit sorry for the late response actually today is our Eid ul-Adha holiday... That's why I'm unable to reply to you... And sure, you can collaborate on this issue with me. |
Beta Was this translation helpful? Give feedback.
-
|
@rohansx, Looking forward to your response! |
Beta Was this translation helpful? Give feedback.
-
|
@s2sharpit Ok tushar, I'm adding you as a collaborator to this project and go ahead with ur plan. Create a new branch and make all the changes in that branch only regarding the migration process and after completing we will merge into the main branch. @crocmons While creating a PR make sure to request it into that new branch and belated Eid-ul-Adha mubarak! |
Beta Was this translation helpful? Give feedback.
-
|
Dear @rohansx, Thank you so much for your response and for adding me as a collaborator to the project. I truly appreciate the opportunity to work on the migration process and contribute to the project. |
Beta Was this translation helpful? Give feedback.
-
|
Hello @rohansx, I hope this message finds you well. I wanted to seek some clarification regarding the use of TypeScript in our project. While reviewing the recent comment by @crocmons on #659, they mentioned that TypeScript may not be necessary based on this message. Considering the benefits that TypeScript offers, such as enhanced type checking and improved tooling, I believe it could greatly contribute to the project's overall maintainability and developer experience. Hence, I wanted to inquire whether we should incorporate TypeScript into our project or proceed without it. Your guidance on this matter would be greatly appreciated, as you hold the role of project admin and have valuable insights into the project's goals and requirements. Your decision will help us align our development efforts effectively. Thank you for your time and consideration. I look forward to hearing your thoughts. |
Beta Was this translation helpful? Give feedback.
-
|
Subject: Request for Transitioning Contributors' Focus to the Newly Migrated Codebase Hi @rohansx, I hope this message finds you well. I wanted to discuss an important decision regarding our project's codebase migration to Next.js and seek your assistance as the Project Admin in transitioning the contributors' focus to the newly migrated codebase. The migration process has made significant progress, and we are approaching the point where the new codebase will be stable and ready for primary use on the website. In order to ensure a smooth transition, I believe it is crucial to align the efforts of our contributors. I kindly request your support in communicating and guiding the contributors to shift their focus from the main branch to the "next-ts-tw-migrate" branch, where we have been actively working on the codebase migration. By directing their efforts to the new codebase, we can fully leverage its benefits and foster a more streamlined development process. Your role as the Project Admin is crucial in driving this transition and ensuring its success. I greatly appreciate your guidance and leadership in coordinating with the contributors to facilitate this shift. I look forward to discussing this matter further and finding the best approach in collaboration with you. Thank you for your attention to this request. Best regards, |
Beta Was this translation helpful? Give feedback.
-
|
Hey @rohansx Your attention is required in the above message. |
Beta Was this translation helpful? Give feedback.
-
|
Hey @rohansx, Your attention is required in the above message. Please check it. 🙏 |
Beta Was this translation helpful? Give feedback.
-
|
@rohansx, I think the 'next-ts-tw-migrate' branch is almost done. So, you can merge it into the main branch. We will do the rest of the implementation on the main branch so that other contributors can continue their work with this newly developed branch. |
Beta Was this translation helpful? Give feedback.
-
|
@rohansx Is There Anything I Can Work On Regarding This? |
Beta Was this translation helpful? Give feedback.
-
We are currently running a project built on ReactJS, and we would like to migrate to the latest version of Next.js, specifically Next.js 13. We believe that this migration will bring significant benefits to our project, such as improved performance, enhanced developer experience, and access to new features provided by Next.js.
To ensure a smooth transition, we would like to outline the necessary steps and considerations for migrating our ReactJS project to Next.js 13
Key objectives:
Upgrade React and related dependencies: In order to migrate to Next.js 13, we need to ensure that our project is running on the latest version of React and any other dependencies that may require an upgrade.
Configure Next.js environment: We will need to set up a Next.js environment and configure it properly to align with our project's specific requirements. This includes configuring routing, server-side rendering (SSR), and any other necessary Next.js features.
Update project structure: Next.js has its own folder structure and conventions that differ from traditional React projects. We will need to update our project structure accordingly to leverage the full capabilities of Next.js.
Migrate components and pages: Next.js uses a pages directory to handle routing and rendering. We will need to migrate our existing React components and pages to fit this new structure and ensure they function correctly.
Refactor APIs and data fetching: Next.js provides built-in API routes and serverless functions, which we should consider utilizing for handling backend requests and data fetching. We will need to refactor our existing API calls to align with these Next.js features.
Handle static assets and CSS: Next.js has its own mechanism for handling static assets and CSS, including support for CSS modules and CSS-in-JS libraries. We will need to update our asset and CSS handling to match the Next.js conventions.
Optimize performance and SEO: Next.js offers various performance optimizations and SEO features out of the box. We should explore and implement these optimizations to enhance the performance and discoverability of our application.
Please note that this migration will require careful planning and testing to ensure a seamless transition. We should thoroughly test the application after each step to identify and resolve any compatibility or functionality issues that may arise.
This GitHub issue will serve as a central place for discussing and tracking the progress of the migration process. Please feel free to share any suggestions, concerns, or questions related to this migration. Let's work together to successfully migrate our ReactJS project to Next.js 13 and take advantage of the benefits it offers.
Thank you for your collaboration.
Beta Was this translation helpful? Give feedback.
All reactions