Issue with Windows

[twrighths]

Just came across an issue with how NPM runs in Windows and a way to work around it. Normally, if you install this via npm, it will create what are essentially wrappers to the commands you really want to call. In this case, we want to run flyway.cmd, but due to how npm pulls in the package, the node_modules/.bin folder gets 3 flyway executables [flyway, flyway.cmd, flyway.cmd.cmd]. Because of this, on windows, if you want to make use of this in your package.json scripts section, you have to use the .cmd.cmd script:

"scripts": {
  "migrate": "flyway.cmd.cmd -X -configFile=conf/flyway.conf migrate"
}

"scripts": {
  "migrate": "flyway.cmd.cmd -X -user=postgres -schemas=public,another migrate"
}

[sksethi25]

@sgraham785 any update on this?

[aldenquimby]

@twrighths @sksethi25 I'd be glad to try fixing this on my fork: https://github.com/aldenquimby/flywaydb-cli

But I haven't used Windows in a long time. Do you know how the package.json is supposed to be configured here? I imagine if we remove this line:

flywaydb-cli/package.json

Line 8 in 5d2fd9a

"flyway.cmd": "./bin/flyway.cmd"

Then on Windows flyway.cmd will end up pointing incorrectly to the unix executable 🤔