Repository navigation
Deprecate @equinor/eds-data-grid-react #5390
Description
Background
The team has decided to stop maintaining @equinor/eds-data-grid-react: with a team of two web developers we do not have the resources to maintain a component of this complexity, so no further fixes or development will be done. We will deprecate the package and recommend that consumers use a third party grid directly styled with EDS components and tokens.
Deprecation is non-breaking: the package stays on npm and keeps working as-is, but will receive no bug fixes, new features, or security updates.
Checklist
1. Prepare the message (write once, reuse everywhere)
- Draft the standard message covering: status (development frozen, package deprecated), what it means in practice (still works, no fixes/features/security updates), the recommended alternative (
@tanstack/react-tablestyled with EDS), and where to ask questions - Be honest about the why: small team, complex component, prioritisation
2. Announce (Slack first, then the rest the same day)
- Post the announcement in the EDS Slack channel a week before running
npm deprecate, so people read the explanation before warnings show up in their CI logs - In the Slack post, invite teams that are heavy users to reach out if they want to take over maintenance
- Add a deprecation banner at the top of
packages/eds-data-grid-react/README.md(visible on both GitHub and npm) - Mark the package as deprecated on the docs site (
apps/design-system-docs/docs/resources/resources.mdx) -
Create a pinned GitHub announcement issue explaining the decision and what users can expectThe announcement is posted as a comment on this issue, and the replacement recommendation is tracked in Recommend a replacement for the deprecated @equinor/eds-data-grid-react #5649
3. Deprecate on npm
- Run
npm deprecate @equinor/eds-data-grid-react "<standard message>"
4. Clean up
- Close open bugs and feature requests against the package, pointing to the pinned announcement issue
- Remove the package from the release-please config (or add it to
exclude-paths) so a stray commit doesn't trigger a new release of a deprecated package -
Optional: one final patch release updating theSkipped: the npm deprecation message already shows on npmjs.com and at installpackage.jsondescription and changelog to mention the deprecated status
Activity
claude commentedon Sep 2, 2026
These existing issues look related and may be worth linking from the deprecation checklist (especially step 4, "Close open bugs and feature requests against the package"):
This comment was generated by an LLM and may be inaccurate. Please verify that the linked issues are actually relevant.
pomfrida commentedon Oct 6, 2026
Slack message draft for #eds-design-system channel
Development is frozen. The package stays on npm and keeps working exactly as it does today, but it gets no bug fixes, no new features and no security updates from us.
Why: we do not have the resources to maintain a component of this size. A data grid is one of the largest things a design system can own, and keeping it at the quality we want would take capacity we need for the core components and tokens.
What to use instead: we are working out a proper recommendation, following the direction from the table workshop, EDS Table for the everyday cases and a third-party grid for the advanced ones, with tokens and guidance on when to use what. Follow #4656 for that. Nothing has to change in your app today.
Next week we run npm deprecate on the package, so you will start seeing a warning in your install and CI logs. Nothing breaks.
Two asks:
Background: #5390
pomfrida commentedon Oct 14, 2026
@equinor/eds-data-grid-reactwas deprecated on npm on 14 October for all 34 versions. The deprecation message and the banners added in #5599 point to #5649, where the replacement recommendation is tracked.