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.
Keep getting this error whenever I try to run my freshly created project. I get the same error when running other frontity projects as well. I have followed the exact steps on the docs multiple times. Please help.
Warning: Closing file descriptor 25 on garbage collection
(Use node --trace-warnings ... to show where the warning was created)
(node:26897) [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.
2 Likes
v4deus2
Yes, I’ve got the same problem. May it happen because I’m still using windows 8.1 ?
Text from temminal:
f:\Junior\2022\frontity>npx frontity dev
(node:16340) Warning: Closing file descriptor 3 on garbage collection
(Use node --trace-warnings ... to show where the warning was created)
(node:16340) [DEP0137] DeprecationWarning: Closing a FileHandle object on garbag
e collection is deprecated. Please close FileHandle objects explicitly using Fil
eHandle.prototype.close(). In the future, an error will be thrown if a file desc
riptor is closed during garbage collection.
Error: error:0308010C:digital envelope routines::unsupported
at new Hash (node:internal/crypto/hash:67:19)
at Object.createHash (node:crypto:130:10)
at module.exports (f:\Junior\2022\frontity\node_modules\webpack\lib\util\cre
ateHash.js:135:53)
at NormalModule._initBuildHash (f:\Junior\2022\frontity\node_modules\webpack
\lib\NormalModule.js:417:16)
at handleParseError (f:\Junior\2022\frontity\node_modules\webpack\lib\Normal
Module.js:471:10)
at f:\Junior\2022\frontity\node_modules\webpack\lib\NormalModule.js:503:5
at f:\Junior\2022\frontity\node_modules\webpack\lib\NormalModule.js:358:12
at f:\Junior\2022\frontity\node_modules\loader-runner\lib\LoaderRunner.js:37
3:3
at iterateNormalLoaders (f:\Junior\2022\frontity\node_modules\loader-runner
lib\LoaderRunner.js:214:10)
at iterateNormalLoaders (f:\Junior\2022\frontity\node_modules\loader-runner
lib\LoaderRunner.js:221:10)
f:\Junior\2022\frontity>
yks3
I am using MacOS so doubt that is the problem.
v4deus4
Ok, problem was solved. I tried to use latest node instead of recommended. And that was the issue. Since I change node to recommended version everything is going ok.
1 Like
yks5
Thank you I will try this.
jacopo.riccioni6
Hi all
same problem here, but I can’t find which node version should I use.
now I have:
node v17.2.0
npm: 8.3.0
thanks
1 Like
jacopo.riccioni7
with versions 16.14.2 and 14.18.1
works great
1 Like
general8
Hi, I also seem to be running into the same issue.
I’m running npx frontity dev but soon after I get this in Terminal:
SERVER STARTED -- Listening @ http://localhost:3000
- mode: development
- target: module
- public-path: /static/
(node:8822) Warning: Closing file descriptor 25 on garbage collection
(Use `node --trace-warnings ...` to show where the warning was created)
(node:8822) [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.
I have a demo project setup and it runs perfectly. I also have this same project setup on a separate Mac and that works fine too. I have tried deleting and re-cloning my repo but it doesn’t make any difference.
Not sure why this is happening.
hyudha9
Yes, I also get the same error… what should I do…?