The team is now working on the WordPress Interactivity API. This unblocks the same UX Frontity framework enabled but directly in WordPress Core, fully compatible with the new Site Editor.
I’ve updated all the packages on the local environment, but when i run npm install i get the following errors:
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! Found: react@16.14.0
npm ERR! node_modules/react
npm ERR! peer react@"^16.5.0" from @frontity/lazyload@1.0.12
npm ERR! node_modules/@frontity/lazyload
npm ERR! @frontity/lazyload@"^1.0.12" from the root project
npm ERR! peer react@"^16.14.0" from react-dom@16.14.0
npm ERR! node_modules/react-dom
npm ERR! peer react-dom@"^16.5.0" from @frontity/lazyload@1.0.12
npm ERR! node_modules/@frontity/lazyload
npm ERR! @frontity/lazyload@"^1.0.12" from the root project
npm ERR! peer react-dom@"^16.8 || ^17.x" from @kunukn/react-collapse@2.2.9
npm ERR! node_modules/@kunukn/react-collapse
npm ERR! @kunukn/react-collapse@"^2.2.9" from the root project
npm ERR! 3 more (@kunukn/react-collapse, @loadable/component, @react-pdf/renderer)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! react-elastic-carousel@"^0.11.1" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: react@17.0.1
npm ERR! node_modules/react
npm ERR! peer react@"^15.0.0 || ^17.0.0" from react-elastic-carousel@0.11.1
npm ERR! node_modules/react-elastic-carousel
npm ERR! react-elastic-carousel@"^0.11.1" 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! See /Users/dejangeorgiev/.npm/eresolve-report.txt for a full report.
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/dejangeorgiev/.npm/_logs/2021-02-22T22_14_17_050Z-debug.log
I’ve been able to succesfully deploy your project to Vercel
(base) ⬢ ruthgeorgiev-frontity master ⦿ npx vercel login
Vercel CLI 21.2.3
We sent an email to juanmaXXXXXXX@XXXXXXXmail.com. Please follow the steps provided inside it and make sure the security code matches Happy Pond Skater.
✔ Email confirmed
Congratulations! You are now logged in. In order to deploy something, run `vercel`.
💡 Connect your Git Repositories to deploy every branch push automatically (https://vercel.link/git).
(base) ⬢ ruthgeorgiev-frontity master ⦿ npx vercel
Vercel CLI 21.2.3
? Set up and deploy “~/PROJECTS/2021/FRONTITY/COMMUNITY/FEBRUARY/ruthgeorgiev-frontity”? [Y/n] y
? Which scope do you want to deploy to? JuanMa
? Link to existing project? [y/N] n
? What’s your project’s name? ruthgeorgiev-frontity
? In which directory is your code located? ./
🔗 Linked to juanmaguitar/ruthgeorgiev-frontity (created .vercel and added it to .gitignore)
🔍 Inspect: https://vercel.com/juanmaguitar/ruthgeorgiev-frontity-8xtoe7d9w/juanmaguitar [3m]
✅ Production: https://ruthgeorgiev-frontity.vercel.app [copied to clipboard] [9m]
📝 Deployed to production. Run `vercel --prod` to overwrite later (https://vercel.link/2F).
💡 To change the domain or build command, go to https://vercel.com/juanmaguitar/ruthgeorgiev-frontity/settings
Hope this helps!
2 Likes
dejangeorgiev5
Hi @juanma
Thank you very much for your feedback.
I’ve tried the exact same as you did, but i get a different error - see below.
I guess this might be an issue with @frontity/lazyload@1.0.12 on my side.
Please let me know your thoughts on this.
Thanks.
Dejan
juanma7
Hi @dejangeorgiev
Have you updated your Frontity packages versions to the latest ones available? Here you have a guide that explains how to keep your project dependencies updated to their latest versions