Open nwalters512 opened 11 months ago
@navateja-alagam @jaig-0911 can y'all take a look at this? I'm currently stuck in a situation where I cannot upgrade axe-core
because @sa11y/format
has pinned it at an older version. This is very uncommon in the JS package ecosystem, so unless there's a good reason it's pinned to an old version, I'd love to open a PR unpinning axe-core
.
I recently updated
axe-core
to4.8.2
in a project, but because the@sa11y/common
package pinsaxe-core
to4.7.0
, I end up with two distinct copies ofaxe-core
in my project which don't have compatible types (see https://github.com/dequelabs/axe-core/pull/4081). This causes TypeScript to complain:This library should almost definitely unpin
axe-core
to allow new minor versions to be used without@sa11y/common
needing to explicitly change.I'd be happy to make this change if a maintainer could confirm that it will be accepted. It's not clear to me why the
@sa11y/*
packages pin dependencies in the first place.