postinstall task fails when installing on windows

How to repro Run npm install axe-core on a Windows machine in regular cmd (not Bash on Windows).

This is the output:

C:\Projects\tests>npm install axe-core

> axe-core@2.4.0 postinstall C:\Projects\tests\node_modules\axe-core
> ./bin/postinstall.sh

'.' is not recognized as an internal or external command,
operable program or batch file.
npm WARN enoent ENOENT: no such file or directory, open 'C:\Projects\tests\package.json'
npm WARN tests No description
npm WARN tests No repository field.
npm WARN tests No README data
npm WARN tests No license field.

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! axe-core@2.4.0 postinstall: `./bin/postinstall.sh`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the axe-core@2.4.0 postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\antonmo\AppData\Roaming\npm-cache\_logs\2017-09-09T03_30_18_327Z-debug.log

This is the npm debug log: 2017-09-09T03_30_18_327Z-debug.txt

We are looking into updating to the latest version in https://github.com/sonarwhal/sonar, but the tool needs to run in any OS so we can’t at the moment 😦

[Landen13]

+1. Also postinstall script doesn’t work on Git Bash.

[marcysutton]

Maybe have a small script that modifies package.json and removes the postscript action before publishing on npm and then restores it back?

That sounds good. I’ll work on it for our next patch release.

Really surprising it doesn’t work in Git Bash…as an action item moving forward we’ll see what we can do about running our tests on Windows using CI to catch this kind of stuff with minimal effort. https://github.com/dequelabs/axe-core/issues/519