core: Migrate to Next JS v15

[pingSubhajit]

This issue focuses on migrating the application from Next.js version 14 to the latest version, Next.js v15. This migration will allow the application to leverage the latest features, performance optimizations, and security enhancements provided by Next.js v15.

Success Criteria:

• The application successfully migrates to Next.js v15.
• All existing functionalities and features remain intact after the migration.
• The application's performance and user experience are improved or maintained.

Acceptance Criteria:

• Update the Next.js dependency in the package.json file to version 15.
• Update any outdated configurations or code according to the Next.js v15 documentation.
• Migrate any custom middleware or API routes to the new Next.js API routes framework.
• Thoroughly test the application after migration to ensure all features and functionalities work as expected.
• Address any compatibility issues or conflicts that arise during the migration process.

Additional Notes:

• Review the Next.js v15 release notes and documentation for a detailed understanding of the new features, updates, and potential breaking changes.
• Consider using a migration guide or tool to streamline the process and identify potential compatibility issues.
• Create a test plan to comprehensively evaluate the application's functionality and performance after the migration.
• Ensure that the migration process is well-documented for future reference and maintenance.

This migration will ensure that the application benefits from the latest advancements and capabilities offered by Next.js v15, resulting in improved performance, security, and overall developer experience.

[linear[bot]]

LET-21 core: Migrate to Next JS v15

This issue focuses on migrating the application from Next.js version 14 to the latest version, Next.js v15. This migration will allow the application to leverage the latest features, performance optimizations, and security enhancements provided by Next.js v15. **Success Criteria:** * The application successfully migrates to Next.js v15. * All existing functionalities and features remain intact after the migration. * The application's performance and user experience are improved or maintained. **Acceptance Criteria:** * Update the Next.js dependency in the `package.json` file to version 15. * Update any outdated configurations or code according to the Next.js v15 documentation. * Migrate any custom middleware or API routes to the new Next.js API routes framework. * Thoroughly test the application after migration to ensure all features and functionalities work as expected. * Address any compatibility issues or conflicts that arise during the migration process. **Additional Notes:** * Review the Next.js v15 release notes and documentation for a detailed understanding of the new features, updates, and potential breaking changes. * Consider using a migration guide or tool to streamline the process and identify potential compatibility issues. * Create a test plan to comprehensively evaluate the application's functionality and performance after the migration. * Ensure that the migration process is well-documented for future reference and maintenance. This migration will ensure that the application benefits from the latest advancements and capabilities offered by Next.js v15, resulting in improved performance, security, and overall developer experience.

[pingSubhajit]

With the stable release of NextJS v15, Vercel has released a migration guide to help safely migrate any NextJS app to the latest version. The guide features a codemod tool to automatically do the migration job. That codemod along with the migration guide is being used to perform the migration.

Upgrading: Version 15

[pingSubhajit]

Types of Framer Motions are broken with Next v15. Some HTMLAttributes do not exist on type MotionComponents. Type assertions has been used as a quick fix to make Typescript accept the HTML attributes with the intention to revisit and remove the type assertions once the types of the library (Framer Motion) is fixed

[pingSubhajit]

Framer Motion v12 aims to solve the issues regarding the incompatibility with React 19. Although v12 of the library is in Alpha, the version has been tested with the core application and every functionalities seem to work as expected without any weird behaviours. But because the version is in Alpha stage currently, it cannot be introduced as a dependency as of yet. Type assertions methods are being kept for the time being and a close eye is being kept on the stable release of Framer Motion v12.