[FOLIO-1569] CI stripes build should fail on unmet peerDependency for stripes framework Created: 10/Oct/18 Updated: 07/Feb/19 |
|
| Status: | Open |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | P3 |
| Reporter: | Wayne Schneider | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | ci | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||
| Sprint: | |||||||||
| Development Team: | Core: Platform | ||||||||
| Description |
|
Here is an example of a warning produced during a yarn install of a platform: warning " > @folio/users@2.17.9000539" has incorrect peer dependency "@folio/stripes@^1.0.0". I generated this warning with platform-core that depends on stripes 2.0, but I modified the package.json to include an older version of ui-users that I know still targets stripes 1.x Normally we we not want to encounter these warnings for builds from `npm-folio`. However, given the nature of snapshot builds, such warnings may be somewhat acceptable on `npm-folioci` during the roll-out of a new stripes framework version. |
| Comments |
| Comment by Matthew Jones [ 10/Oct/18 ] |
|
Assigning this to myself until I have a chance to fill in the description. |