pharos
pharos copied to clipboard
JSTOR's design system
**The problem** Situations can arise where a bugfix or new feature needs to be released during work towards a new major release. We should have a defined process for doing...
**The problem** I want to be on recent and maintained versions of dependencies to ensure security and maintainability. **The solution** Upgrade to Storybook 8, possibly eagerly with the latest release...
**This change:** (check at least one) - [ ] Adds a new feature - [x] Fixes a bug - [ ] Improves maintainability - [ ] Improves documentation - [...
**The problem** I want to use the latest versions of our dependencies so that I can take advantage of their new features, security, and ecosystem. **The solution** Upgrade to MDX...
**Expected behavior** Running `yarn site:develop` should run pharos site successfully locally **Actual behavior** Locally, I am seeing blank page and console errors after running `yarn site:develop`. (More in Additional Information)...
**The problem** A few weeks ago we were looking to have a change with the tabs component available for us to use in our project but the ability to use...
**The problem** Managing the React components is a maintenance burden and prone to error. Doing this ourselves incurs a whole area of work around duplicating component stories for React and...
**Expected behavior** The release goes off without a hitch **Actual behavior** Errors encountered during the release process **Steps to reproduce the issue** 1. Visit [the Actions log for the v14.0.0...
**Expected behavior** Hot reloading of storybook works with a single command **Actual behavior** We need to run two commands to get hot reloading to work **Steps to reproduce the issue**...
**Expected behavior** `animate` is understood to be a function for the spinner and tests pass locally. Alternatively we have setup our application to avoid alerting on this type error altogether....