Skip to end of banner
Go to start of banner

Stripes roadmap planning

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Themes

Goals/objectives

Ideas for how/ Notes

Maintain

  • upgrade yarn from v1 to v4.1, or migrate to npm >= v10

  • upgrade react-router from v5 to v6

Innovation

  • transpile all modules on publish (update stripes-webpack)

Improved dependency handling support

  • enable dependabot in all modules

  • commit yarn.lock in all modules

Improved developer adoption

Accessibility

  • Review and address Deque accessibility results related to time-picker/date-picker/

  • Post-css revisions / will review color contract Deque accessiblity issues to determine resolution

Break tower of knowledge/support

Bolster UX consistency

Improved test coverage

DayJS - add it as an option for date handling

Popper -> convert to Floating UI

Downshift -> Update to most recent version (lots of breaking versions since)

react-highlight-words

redux-form and react-form and their related libraries have been abandoned. We already contend with some peer-dep warnings for related libraries that haven't provided a React v18 release (which means they've been out of date since at least March, 2022). The main contenders for replacement are formik and react-hook-form. We don't need a "thou shalt switch" decree, but we should do a spike to see how stripes-components interacts, pick our favorite, and write a guide. I would vote for RHF first. This work can be done incrementally.

react-router: needs to bump from v5 to v6. I suspect the impact will be very small or very large, as in, some repos won't be affected at all but others will have to do some heavy lifting. This work will have to be done all at once.

react-query: we're on v3; current is v5. Dunno the impact. This work may be doable incrementally but all at once is preferable.

  • No labels