@apollo/core-schema
Advanced tools
Changelog
v0.1.1
engines
specification for npm
which limited it to only working on npm@7
. The spirit of that specificity was to provide a hint to maintainers as to what version of npm
should be used to generate the package-lock.json
file and reduce churn on that file which happened between npm@6 and npm@7. Of course, while this was effective and harmless in the federation
monorepo (from which this was copied and pasted from), it obviously has implications on consumers in published packages. Fixed via ee1a330e
.