Enable `strictNullChecks` in the console/frontend and fix all build errors. This is mandatory for the i18next >22 version upgrade and might be required for other console dependencies in the future. And in addition, this will further help prevent unexpected runtime errors caused by null or undefined values.

A.C.

• Investigate how wast the migration process will be. Create a logical parts in the core package, which contain the fix.
• Create an inventory of effected static plugins.
• Reach out to the owners to carry out the fix (TBD - lets discuss this item once we have a clear picture how to move forward)

 Open questions:

•  The total number of TypeScript errors in the console/frontend codebase after enabling `strictNullChecks` is 13,448. This is significantly large and requires proper planning and estimation. How do we want to handle this?  
  This command can be used to get the total number of TypeScript errors when `strictNullChecks` is enabled:

            `npx tsc --noEmit | wc -l`

• Should the console team be responsible for fixing static plugins' strictNullChecks errors?
• There could be possibilities of medium to large code segments requiring refactoring to fix the errors.