Can't start dev or build after creating new project

[yiheyang]

Bug report

• I've updated both my project and my packages to the latest Frontity versions: https://docs.frontity.org/guides/keep-frontity-updated
• I've searched for existing issues.
• I've checked the documentation: https://docs.frontity.org
• I've checked the community forum: https://community.frontity.org

Expected behavior

Observed behavior

Error even in the StackBlitz

Steps involved to reproduce the problem

Info about your system

Possible solution

[ryanmathis]

I'm having the same issue. I was going to post on the community forum but the login/registration is not working.

[JasonS09]

I'm having the exact same issue and same is happening to me with the forum login.

[cbravobernal]

Hi @yiheyang! Which npm node version are you using?

I ran the same steps and for me was working fine. Maybe with that info I can try switching to your NodeJS - NPM versions.

[yiheyang]

Hi @yiheyang! Which npm node version are you using?

I ran the same steps and for me was working fine. Maybe with that info I can try switching to your NodeJS - NPM versions.

I'm currently running Node LTS v14.17.4.

Make sure you have no package-lock file and better run npm cache clean --force before you try.

[luisherranz]

I'm having the same issue. I was going to post on the community forum but the login/registration is not working.

Sorry about this. We fixed an issue with the log-in a few weeks ago so please try again.

[luisherranz]

Is someone experiencing this after upgrading to the latest version of Frontity?

[Etheliene]

I just made a fresh install on the following node / npm Versions:

node: 17.3.1
npm: 8.3.0

I get the same error :/

Even after installing nvm and using Node 16.5.0 it won't do it for me.

[luisherranz]

Even after installing nvm and using Node 16.5.0 it won't do it for me

Does it work with Node 14/12, or doesn't it work at all?

[kasperaamodt]

Every time I work with Frontity I have to downgrade node to 12.^

[luisherranz]

Could you please check if this is fixed now with the latest release?

[luisherranz]

Another ping here to see if this was successfully solved in the last release.