Closed crypt0grapher closed 3 years ago
weird.. the automated build should have picked this up.. as it is using npm . does this happen with the new PR in there?
yep, it was, I've tested on a few more images with the latest PR and it worked out just fine. So, once the npm registry is updated with the v2 of anchor-earn, I'll test once more and close the thread.
they don't let me do that kinda thing @cosullivan .. any chance of pushing it?
@petes-fan-club I've published this to NPM as 2.0.0-alpha1
Thanks @cosullivan , @petes-fan-club. It works perfectly fine for me with the regular npm package. I'm closing the ticket.
Once pulled,
npm install
givessh: husky: command not found
. That's because husky 5 is both set as a dev dependency and part ofprepare
script inpackage.json
. yarn installs husky and doesn't give an error. Howeverprepare
is not the yarn 2+ lifecycle script anymore.This shouldn't be the case for husky v4, but for v5
prepare
could run a shell script executing husky installation withnpx
if no.husky
folder is preset. Also, ifyarn
is still recommended as per readme file, probably using getting rid ofprepare
and usingprepublish
only would unify the usage for bothnpm
andyarn
.