"Error: EBUSY: resource busy or locked" in Powershell 7

[lwojcik]

While starting the project with npm run dev in Powershell 7 on Windows 10, the following error is displayed and the command fails:

Until the issue is solved, the following workarounds seem to work:

• Use older version of Powershell or git on Windows
• open separate Powershell 7 window and run npm run watch:eleventy directly

[joel-lbth]

i use your template (and very nice it is too) and sometimes encounter the same "EBUSY: resource busy or locked" scenario, and it is always to do with the favicon, though it is also intermittent. it happens in git bash as well as powershell in windows 10, and also happens with npm run build - it usually goes away after a retry. not sure what to add really as it's not happening currently!

[lwojcik]

Since this issue has to do with an unresolved bug in an external plugin and I can't put enough time to diagnose and fix it, starting from v2.4.0 Bliss no longer ships with automatic favicon generation.

If you liked the feature, feel free to reimplement it on your own - consult change history from this PR to get it back.

[Bouali-Ramzi]

Thank you Le sam. 2 mars 2024 à 00:43, Łukasz Wójcik ***@***.***> a écrit :

…

Since this issue has to do with an unresolved bug in an external plugin and I can't put enough time to diagnose and fix it, starting from v2.4.0 Bliss no longer ships with automatic favicon generation. If you liked the feature, feel free to reimplement it on your own - consult change history from this PR <#99> to get it back. — Reply to this email directly, view it on GitHub <#91 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AWBQEYLFGMLJTJDH7EGNLLDYWEHDJAVCNFSM6AAAAABDJEX74OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZUGA4DMMJSHA> . You are receiving this because you commented.Message ID: ***@***.***>