Description
When the new token structure graduates from beta and ships as the stable 3.0.0 major, run npm deprecate on the old @equinor/eds-tokens 2.x range so consumers get an explicit signal at install time:
npm deprecate @equinor/eds-tokens@"<3.0.0" "eds-tokens 2.x still works and has no known issues, but is no longer maintained. It is superseded by the new token structure in 3.0.0 — migrate at your own pace: <migration guide URL>"
The message wording matters: it is the only thing consumers see in their install logs, and an alarming or vague message causes unnecessary escalations (compliance tooling flags deprecated dependencies automatically). Keep it factual and reassuring, with a direct link.
Context
This was deliberately deferred when the old token systems were marked "do not use" in #5191 (published as 2.3.2): deprecating the 2.x range while it is still the supported stable line would print install warnings for every consumer, including transitively via @equinor/eds-core-react 2.x which requires these tokens. The right time is when 3.0.0 ships and 2.x is genuinely superseded.
See the closing comment on #5120 for the full transition state.
Definition of Done
The order below is deliberate — the install warning should never be the first time a team hears about the transition:
Note: deprecation is reversible (npm deprecate <pkg>@<range> "" clears it), so this is low-risk to apply.
Timeline: blocked until 3.0.0 graduation (stable major not planned this year).
Description
When the new token structure graduates from beta and ships as the stable
3.0.0major, runnpm deprecateon the old@equinor/eds-tokens2.x range so consumers get an explicit signal at install time:The message wording matters: it is the only thing consumers see in their install logs, and an alarming or vague message causes unnecessary escalations (compliance tooling flags deprecated dependencies automatically). Keep it factual and reassuring, with a direct link.
Context
This was deliberately deferred when the old token systems were marked "do not use" in #5191 (published as
2.3.2): deprecating the 2.x range while it is still the supported stable line would print install warnings for every consumer, including transitively via@equinor/eds-core-react2.x which requires these tokens. The right time is when 3.0.0 ships and 2.x is genuinely superseded.See the closing comment on #5120 for the full transition state.
Definition of Done
The order below is deliberate — the install warning should never be the first time a team hears about the transition:
3.0.0is released as stable (latest)npm deprecateapplied to the 2.x range with a factual, reassuring message linking the migration guidenpm install @equinor/eds-tokens@2shows the deprecation warningNote: deprecation is reversible (
npm deprecate <pkg>@<range> ""clears it), so this is low-risk to apply.Timeline: blocked until 3.0.0 graduation (stable major not planned this year).