You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 22, 2024. It is now read-only.
Peer dependancy error when installing slinkity with recent 11ty versions.
npm install --save-dev slinkity
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: project@1.0.0
npm ERR! Found: @11ty/eleventy@2.0.1
npm ERR! node_modules/@11ty/eleventy
npm ERR! dev @11ty/eleventy@"^2.0.1" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @11ty/eleventy@"^1.0.0" from slinkity@0.8.3
npm ERR! node_modules/slinkity
npm ERR! dev slinkity@"*" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /Users/------/.npm/_logs/2024-01-29T11_27_04_400Z-eresolve-report.txt
Can always force or use legacy parameters, but not ideal.
This leads me to the question, is this project still being maintained or worked on even on a minor level?
The text was updated successfully, but these errors were encountered:
Thanks for the thorough logs @aaronstezycki! I am sorry to say that Slinkity is no longer maintained. To make this clear to new users, I have archived the repository, and I have updated the project README to reflect the current status.
If the community would like to fork and keep Slinkity alive, all code is open and MIT licensed. I apologize for the radio silence, but I hope this clarifies everything!
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe the bug
Peer dependancy error when installing slinkity with recent 11ty versions.
Can always force or use legacy parameters, but not ideal.
This leads me to the question, is this project still being maintained or worked on even on a minor level?
The text was updated successfully, but these errors were encountered: