refactor: replace legacy ErrorMessage.js with messages/ErrorMessage.tsx

[SahilJat]

Thanks for submitting a PR! Please check the boxes below:

• [ x ] I have read the Contributing Guide.
• [ x ] I have added information to docs/ if required so people know about the feature.
• [ x ] I have filled in the "Changes" section below.
• [ x ] I have filled in the "How did you test this code" section below.

Changes

Closes #6891

Please describe.
deleted the component/ErrrorMessage.js file which was a legacy duplicate of current component/messages/ErrorMessage.tsx , the legacy duplicate was imported into 34 files , all of them now use the latest tsx version.

How did you test this code?

not required

Please describe.
not required

[claude]

⚠️ Code review skipped — your organization's overage spend limit has been reached.

Code review is billed via overage credits. To resume reviews, an organization admin can raise the monthly limit in Settings → Usage.

Once credits are available, reopen this pull request to trigger a review.

[vercel]

@SahilJat is attempting to deploy a commit to the Flagsmith Team on Vercel.

A member of the Team first needs to authorize it.

[talissoncosta]

Hey @SahilJat, thanks for tackling this — nice cleanup removing the old class component and updating the imports! 🎉

I spotted one issue: 4 files still import from the old path (./ErrorMessage), which breaks the build. These were missed because they live in web/components/ alongside the deleted file:

• web/components/NewVersionWarning.tsx
• web/components/SamlForm.js
• web/components/UsersGroups.tsx
• web/components/EditIdentity.tsx

They need to be updated to:

import ErrorMessage from 'components/messages/ErrorMessage'

Also, could you update the "How did you test this code?" section in the PR description? Even for mechanical refactors, a quick smoke test goes a long way. Something like:

Ran npm run dev, opened a few pages that display error states (e.g. submitting an invalid form), and confirmed the error messages render correctly.

Running the dev server locally would have caught the missing imports straight away — good habit that saves review cycles!

Could you push a fix for those four imports and update the test section? Happy to help if you get stuck!