Done
Details
Assignee
Dmitriy LitvinenkoDmitriy LitvinenkoReporter
Zak BurkeZak BurkePriority
P3Story Points
0.5Sprint
NoneDevelopment Team
VegaFix versions
Release
Nolana (R3 2022)TestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee
Dmitriy Litvinenko
Dmitriy LitvinenkoReporter
Zak Burke
Zak BurkePriority
Story Points
0.5
Sprint
None
Development Team
Vega
Fix versions
Release
Nolana (R3 2022)
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created July 8, 2022 at 7:16 PM
Updated October 24, 2023 at 11:58 AM
Resolved July 20, 2022 at 11:17 AM
Overview: One or more components are imported directly from their root
@folio/stripes-*
packages, which are not directly imported into the bundle, instead of via the@folio/stripes
wrapper package, which is so imported, e.g.must be replaced with
Note the
-
afterstripes
is converted to a/
. Likewise, imports from SSC would use@folio/stripes/smart-components
.The current import strategy is technically incorrect since individual modules like
@folio/stripes-components
are not direct dependencies or peer-dependencies. Somehowyarn
is not bothered and manages to provide webpack with what it needs to resolve the imports when creating the bundle. When creating the bundle withnpm
, however, this surfaces as an actual error and causes the job to fail. We anticipate migrating fromyarn
tonpm
within the next release or two, so while this is not urgent now, it will become so soon.