lru-cache npm conflict
mschipperheyn opened this issue · 3 comments
Quite a few libs use lru-cache. Recent versions started using a class based approach requiring new LRU([...]) instead of LRU([...]). I'm getting into npm conflicts because in my mono repo because of some hoisting variations.
dataloader is getting hoisted to the root with the correct lru-cache in the root as well. But my server package doesn't hoist some apollo-server components that reference lru-cache 5.x which is therefore present in the server package. Bc dataloader-sequelize is references from the server package it seems to use the 5.x version in the server package. Oh well.
I'm trying to work around it, but perhaps it's time to update lru-cache?
Sure, should be fine to upgrade
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.