Closed noahnu closed 2 years ago
The only proposal I that I will consider is the Peer Dependency, is this something that impacts only Yarn users though?
It might impact pnpm as well, I'm not sure since I don't use pnpm. I imagine it prints warnings in npm. Definitely impacts Yarn though.
I can revert the lodash change, it was a bit opportunistic. What's the reasoning behind pinning the dependencies though?
Sorry I failed to mention that. axe-core can change it's output and break builds even with semver so that definitely needs to be pinned. I think when I did that I just did a blanket pin to make builds more deterministic but I'd be open to changing the others if you think the value is there just not axe-core.
I reverted the axe-core semver change and reverted the switch to the general lodash package.
I noticed axe-core requires node >12, so jest-axe's min node version could probably be raised
Updated dependencies recently, keeping it simple for now.
Changes
lodash
instead oflodash.merge
.lodash
is a common dependency and so it's very likely the consumer has it loaded as a transitive dependency of another package at a minimum, so this doesn't consume more disk space.lodash
is more popular thanlodash.merge
.@nickcolley If you're open to it, I have some other improvements/general maintenance I can put up PRs for. I can keep the PRs small and focused if you'd like. Right now the TypeScript types live in DefinitelyTyped. Would you be open to a PR which migrates this project to TypeScript? and if not that, what about maintaining the types in this repository in a separate declaration file?