Closed binury closed 3 years ago
Just guessing/intuition but I'd wager the post-installation scripts are configured assuming the installation is done with NPM which causes a conflict for users who have opted into using the --yarn
flag.
Modifying preact-cli-plugin-flow/bin/index.js
to test for the existence of yarn.lock could then allow the post installation to complete using the user's chosen package manager and prevent npm from breaking the depedencies
Hi @teddy-error,
So sorry about the issue 😕
I will get on this today! It is probably what you are saying
Thank you for pointing it out!
hi, unfortunately this is still happening
Adding
preact-cli-plugin-flow
on a fresh installation ofPreact
causes the folder to be deleted.