Oh, thanks. Did you solve the error that React is showing in the console?: http://fb.me/react-invalid-hook-call
Regarding the Webpack warning, it seems like you have more than one folder in node_modules with the same name but different casing. Have you checked that error? Did you find the offending modules?
@floydhartford Did you get this working?
I’m having exactly the same issue.
Following quick start, or cloning a project that works on mac both have exactly the same result.
npm ls react:
-- @frontity/core@1.14.3 – react@17.0.2
Node.js v14.15.1
It seems like a problem with npm 7 and how it handles the peerDependencies, which differs from npm 6. Do you have a React package installed with a peerDependency of React 16 or lower?
No, it’s a straight up clone of the repo and following the getting started steps that causes this - I didnt get to the point where I could do anywork!
Also, sorry for the late reply, work directed my attention elsewhere!