[ESCONF-30] 6.3.x must lock to stripes-webpack ~4.1 (without stripes-ui) Created: 15/Feb/23 Updated: 15/Feb/23 Resolved: 15/Feb/23 |
|
| Status: | Closed |
| Project: | eslint-config-stripes |
| Components: | None |
| Affects versions: | None |
| Fix versions: | 6.3.2 |
| Type: | Bug | Priority: | TBD |
| Reporter: | Zak Burke | Assignee: | Zak Burke |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||
| Sprint: | |||||||||
| Story Points: | 1 | ||||||||
| Development Team: | Stripes Force | ||||||||
| Release: | Orchid (R1 2023) | ||||||||
| RCA Group: | TBD | ||||||||
| Description |
|
Overview: 6.3.x must lock to stripes-webpack ~4.1 (without stripes-ui) in order to remain backwards-compatible with Nolana (2022-R3). Details: stripes-webpack beginning in v4.2.0 looks for its entrypoint in stripes-ui instead of stripes-core. stripes-ui wasn't added to @folio/stripes until v8.0.0, the Orchid (2023-R1) release. Given that eslint-config-stripes v6.3.x was available at the time of the Nolana release, everything in the eslint-config-stripes v6.3.x line should continue to leverage stripes-webpack v4.1 in order to build @folio/stripes v7.x. Additional details: Slack conversation |