You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Run project via any means e.g. npm run dev or npm run build
Expected Behavior: build succeeds, application server runs with react-photoswipe-gallery
Observed Behavior: build fails with the following error:
-----> Installing dependencies
Installing node modules
> [email protected] postinstall /tmp/build_0f71b228/node_modules/core-js
> node -e "try{require('./postinstall')}catch(e){}"
> [email protected] postinstall /tmp/build_0f71b228/node_modules/react-photoswipe-gallery
> husky install
sh: 1: husky: not found
npm ERR! code ELIFECYCLE
npm ERR! syscall spawn
npm ERR! file sh
npm ERR! errno ENOENT
npm ERR! [email protected] postinstall: `husky install`
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the [email protected] postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
Notes: I was able to work around this temporarily by editing the index.js file this error references to continue execution without existence of .git folder, but I don't know if this is a problem with react-photoswipe-gallery or with its dependency husky.
The text was updated successfully, but these errors were encountered:
Hi, I encountered a build issue. It seems to be a problem with Husky. I tested this on both Linux and Windows.
Steps to reproduce:
npm install photoswipe react-photoswipe-gallery --save
npm run dev
ornpm run build
Expected Behavior: build succeeds, application server runs with react-photoswipe-gallery
Observed Behavior: build fails with the following error:
Notes: I was able to work around this temporarily by editing the
index.js
file this error references to continue execution without existence of.git
folder, but I don't know if this is a problem withreact-photoswipe-gallery
or with its dependencyhusky
.The text was updated successfully, but these errors were encountered: