Hello,
I have created a new project with frontity but the browser does not automatically update the code I write in the editor.
Console: Uncaught TypeError: fixRegExpWellKnownSymbolLogic is not a function
and without refresh the updates does not load.
I have created new projects several times and every time I see this error
I had same trouble. I think there might be an error in some newly released frontity/@frontity/core. I downgraded frontity to 1.15 version and frontity/core to 1.13.0 and everything works againā¦
Detailing the info suggested here when having issues will help the community to provide the best possible help as quickly and as efficiently as possible.
I am almost sure that problem is with newest @frontity/core@1.14.1. I cloned repo from frontity tutorial GitHub - frontity-demos/tutorial-hello-frontity. Then I installed fresh frontity locally and when ran there was exact same error. The problem was also with my own project, and mars theme.
I am sorry I didnāt say Hiā¦ I started playing with Frontity some time ago and i loved it. I am planning to use it on my company new website.
Thank you @juanma for your test, but I still got same error when run npx frontity create in clean directory with frontity/core1.14.1 and mars-theme
Maybe itās Os or Node or core-js version related? Or maybe i am doing something wrong
This error cost me a lot of frustration past weekend so i keep digging
Here are outputs from my cli npx frontity info, for this config with clean mars-theme I got fixRegExpWellKnownSymbolLogic error :
@David I havenāt been able to reproduce this issue (maybe itās a Windows issue as Iām reproducing it in. Mac) but it seems to be happening to some users
Can you please have a look at it to check if thereās a bug to be fixed here?
and the errors I get in my console errors:
es.string.match.js?466d:10 Uncaught TypeError: fixRegExpWellKnownSymbolLogic is not a function
at eval (es.string.match.js?466d:10)
at Objectā¦/node_modules/core-js/modules/es.string.match.js (new-project.module.js:3643)
at webpack_require (new-project.module.js:833)
at fn (new-project.module.js:130)
at eval (engine-v8-version.js:1)
at Objectā¦/node_modules/core-js/internals/engine-v8-version.js (new-project.module.js:2441)
at webpack_require (new-project.module.js:833)
at fn (new-project.module.js:130)
at eval (native-symbol.js?4930:2)
at Objectā¦/node_modules/core-js/internals/native-symbol.js (new-project.module.js:2806)
For 1.14.0 version of frontity/core I am doing this with:
npm install @frontity/core@1.14.0
inside the directory with project (I donāt have frontity installed globally). Forgive me if itās kind of ābrutalā solution, but for me itās working
I have made a PR with that branch, including also a fix for the regular expression used to exclude ts-node files.
@santosguillamot, I took the liberty to mark this as critical because it is preventing people from developing with the latest version of Frontity on Windows