Analysis and dev: update/replace popper.js
Description
Environment
None
Potential Workaround
None
relates to
Checklist
hideTestRail: Results
Activity
Show:
Khalilah Gambrell
updated the LabelsJanuary 22, 2025 at 7:56 PMdelegate_candidate
breaking_change delegate_candidate
Khalilah Gambrell
updated the ReleaseMarch 11, 2024 at 3:15 PMQuesnelia (R1 2024)
Not Scheduled
John Coburn
updated the DescriptionJanuary 4, 2024 at 8:33 PM*Summary:* Replace popper.js v1 with something that is actively maintained.
*Details:* popper.js v1 generates a console warning on install:
{quote}You can find the new Popper v2 at @popperjs/core, this package is dedicated to the legacy v1
{quote}
v1 has been [unmaintained for nearly three years|https://github.com/floating-ui/floating-ui/tree/v1.x]. v2 is occasionally maintained; the current incarnation has been rebranded as [Floating UI|https://github.com/floating-ui/floating-ui/tree/a7299d966934de0cb2820d672560cda5cbb8235c]. There are migration guides for both [v1->v2|https://popper.js.org/docs/v2/migration-guide/] and [v2->Floating UI|https://floating-ui.com/docs/migration].
Stripes-components uses Popper through its own 'Popper' primitive. A migration path that incurs as little effort on the part of ui-module code should be prescribed.
*Summary:* Replace popper.js v1 with something that is actively maintained.
*Details:* popper.js v1 generates a console warning on install:
{quote}You can find the new Popper v2 at @popperjs/core, this package is dedicated to the legacy v1
{quote}
v1 has been [unmaintained for nearly three years|https://github.com/floating-ui/floating-ui/tree/v1.x]. v2 is occasionally maintained; the current incarnation has been rebranded as [Floating UI|https://github.com/floating-ui/floating-ui/tree/a7299d966934de0cb2820d672560cda5cbb8235c]. There are migration guides for both [v1->v2|https://popper.js.org/docs/v2/migration-guide/] and [v2->Floating UI|https://floating-ui.com/docs/migration].
Stripes-components uses Popper through its own 'Popper' primitive. A migration path that incurs as little effort on the part of ui-module code should be prescribed.
If the development lift of this is too heavy, we can create another story for work beyond analysis.
John Coburn
updated the SummaryJanuary 4, 2024 at 8:33 PMupdate/replace popper.js
Analysis and dev: update/replace popper.js
John Coburn
updated the DescriptionJanuary 4, 2024 at 8:32 PM*Summary:* Replace popper.js v1 with something that is actively maintained.
*Details:* popper.js v1 generates a console warning on install:
{quote}You can find the new Popper v2 at @popperjs/core, this package is dedicated to the legacy v1
{quote}
v1 has been [unmaintained for nearly three years|https://github.com/floating-ui/floating-ui/tree/v1.x]. v2 is occasionally maintained; the current incarnation has been rebranded as [Floating UI|https://github.com/floating-ui/floating-ui/tree/a7299d966934de0cb2820d672560cda5cbb8235c]. There are migration guides for both [v1->v2|https://popper.js.org/docs/v2/migration-guide/] and [v2->Floating UI|https://floating-ui.com/docs/migration].
*Summary:* Replace popper.js v1 with something that is actively maintained.
*Details:* popper.js v1 generates a console warning on install:
{quote}You can find the new Popper v2 at @popperjs/core, this package is dedicated to the legacy v1
{quote}
v1 has been [unmaintained for nearly three years|https://github.com/floating-ui/floating-ui/tree/v1.x]. v2 is occasionally maintained; the current incarnation has been rebranded as [Floating UI|https://github.com/floating-ui/floating-ui/tree/a7299d966934de0cb2820d672560cda5cbb8235c]. There are migration guides for both [v1->v2|https://popper.js.org/docs/v2/migration-guide/] and [v2->Floating UI|https://floating-ui.com/docs/migration].
Stripes-components uses Popper through its own 'Popper' primitive. A migration path that incurs as little effort on the part of ui-module code should be prescribed.
John Coburn
updated the LabelsJanuary 4, 2024 at 8:29 PMNone
delegate_candidate
Khalilah Gambrell
updated the ReleaseSeptember 28, 2023 at 6:43 PMPoppy (R2 2023)
Quesnelia (R1 2024)
Zak Burke
updated the Linked IssuesMarch 7, 2023 at 12:06 PMNone
This issue relates to STRIPES-848
Zak Burke
created the IssueMarch 7, 2023 at 12:06 PMDetails
Details
Assignee
Unassigned
UnassignedReporter
Zak Burke
Zak BurkePriority
TBDDevelopment Team
Stripes Force
Release
Not Scheduled
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created March 7, 2023 at 12:06 PM
Updated January 22, 2025 at 7:56 PM
TestRail: Cases
TestRail: Runs
Summary: Replace popper.js v1 with something that is actively maintained.
Details: popper.js v1 generates a console warning on install:
v1 has been unmaintained for nearly three years. v2 is occasionally maintained; the current incarnation has been rebranded as Floating UI. There are migration guides for both v1->v2 and v2->Floating UI.
Stripes-components uses Popper through its own 'Popper' primitive. A migration path that incurs as little effort on the part of ui-module code should be prescribed.
If the development lift of this is too heavy, we can create another story for work beyond analysis.