Cant get past npx frontity dev

🙋Get Help
1

Hi everyone,
I’m following the step by step process from the get started documentation on frontity docs. I cant seem to able to run my development server.

I have followed the recommendation give by post forms:-

  1. change the port.
  2. Update Node and NPM
  3. Delete package-lock.json and run Npm install.

still there is no juice.

Here is the output on my windows Visual studio code Terminal

PS C:\Users\User\Desktop\Next.js\ReactWordpress\test-app> npx frontity dev

SERVER STARTED – Listening @ http://localhost:3000

  • mode: development
  • target: module
  • public-path: /static/

(node:30308) Warning: Closing file descriptor 3 on garbage collection
(Use node --trace-warnings ... to show where the warning was created)
(node:30308) [DEP0137] DeprecationWarning: Closing a FileHandle object on garbage collection is deprecated. Please close FileHandle objects explicitly using FileHandle.prototype.close(). In
the future, an error will be thrown if a file descriptor is closed during garbage collection.
Error: error:0308010C:digital envelope routines::unsupported
at new Hash (node:internal/crypto/hash:71:19)
at Object.createHash (node:crypto:133:10)
at module.exports (C:\Users\User\Desktop\Next.js\ReactWordpress\test-app\node_modules\webpack\lib\util\createHash.js:135:53)
at NormalModule._initBuildHash (C:\Users\User\Desktop\Next.js\ReactWordpress\test-app\node_modules\webpack\lib\NormalModule.js:417:16)
at handleParseError (C:\Users\User\Desktop\Next.js\ReactWordpress\test-app\node_modules\webpack\lib\NormalModule.js:471:10)
at C:\Users\User\Desktop\Next.js\ReactWordpress\test-app\node_modules\webpack\lib\NormalModule.js:503:5
at C:\Users\User\Desktop\Next.js\ReactWordpress\test-app\node_modules\webpack\lib\NormalModule.js:358:12
at C:\Users\User\Desktop\Next.js\ReactWordpress\test-app\node_modules\loader-runner\lib\LoaderRunner.js:373:3
at iterateNormalLoaders (C:\Users\User\Desktop\Next.js\ReactWordpress\test-app\node_modules\loader-runner\lib\LoaderRunner.js:214:10)
at iterateNormalLoaders (C:\Users\User\Desktop\Next.js\ReactWordpress\test-app\node_modules\loader-runner\lib\LoaderRunner.js:221:10)
at C:\Users\User\Desktop\Next.js\ReactWordpress\test-app\node_modules\loader-runner\lib\LoaderRunner.js:236:3
at context.callback (C:\Users\User\Desktop\Next.js\ReactWordpress\test-app\node_modules\loader-runner\lib\LoaderRunner.js:111:13)
at C:\Users\User\Desktop\Next.js\ReactWordpress\test-app\node_modules\babel-loader\lib\index.js:44:71

Can anyone help regarding this

1 Like
2

I am having the same problem. Were you able to get past this problem?

3

Same problem, very frustrating, never had such a problem with any framework

4

Same here. I did go to LTS node, npm update and forced the fix but doesn’t work.
My exact error:

Error: error:0308010C:digital envelope routines::unsupported
at new Hash (node:internal/crypto/hash:71:19)
at Object.createHash (node:crypto:133:10)
at module.exports (/Volumes/data/www/edu/react_/projects/lgth_frontity/node_modules/webpack/lib/util/createHash.js:135:53)
at NormalModule.initBuildHash (/Volumes/data/www/edu/react/projects/lgth_frontity/node_modules/webpack/lib/NormalModule.js:417:16)
at handleParseError (/Volumes/data/www/edu/react_/projects/lgth_frontity/node_modules/webpack/lib/NormalModule.js:471:10)
at /Volumes/data/www/edu/react_/projects/lgth_frontity/node_modules/webpack/lib/NormalModule.js:503:5
at /Volumes/data/www/edu/react_/projects/lgth_frontity/node_modules/webpack/lib/NormalModule.js:358:12
at /Volumes/data/www/edu/react_/projects/lgth_frontity/node_modules/loader-runner/lib/LoaderRunner.js:373:3
at iterateNormalLoaders (/Volumes/data/www/edu/react_/projects/lgth_frontity/node_modules/loader-runner/lib/LoaderRunner.js:214:10)
at iterateNormalLoaders (/Volumes/data/www/edu/react_/projects/lgth_frontity/node_modules/loader-runner/lib/LoaderRunner.js:221:10)

Any help, suggestions?

5

Maybe I missed it somewhere, but which version of node are you using?

If I’m not mistaken, Frontity does not work with node 18 or higher. So if that’s the case I’d try downgrading to node 16. Maybe that helps :slight_smile: