node-flyway icon indicating copy to clipboard operation
node-flyway copied to clipboard

Apply version control to databases from within a Node.js application.

Results 15 node-flyway issues
Sort by recently updated
recently updated
newest added

My DB migration script failed with the following error ```bash $ bun run ./migrate.ts 50 | throw new Error(`Unable to find an executable Flyway CLI in target directory: ${directory}`); 51...

There are some path separator issues occurring when running `node-flyway` on Windows machines. This adds an additional job to the CI pipeline which runs the integration tests on a Windows...

There have been a bunch more flyway versions since this library was last published. It'd be great to update the enum for the updated versions.

## Problem Users running commands through the wrapper have been reporting errors such as ``` node-flyway:FlywayExecutable Received response from Flyway CLI: +0ms node-flyway:ConvertJsonToResponse SyntaxError: Unexpected end of JSON input node-flyway:ConvertJsonToResponse...

## Fix: Add Logging for Unparseable JSON Responses ### Description This PR addresses [issue #32](https://github.com/domdinnes/node-flyway/issues/32), which reports errors when users run commands through the wrapper, resulting in unparseable JSON responses....

Greetings, Does node-flyway implement the Flyway dryRun feature? Great library btw.

Are there any plans to update this to allow Flyway versions higher than 9.0.0?

The dependency `[email protected]` depends on `[email protected]` which is not supported any more: https://www.npmjs.com/package/inflight ``` This package has been deprecated Author message: This module is not supported, and leaks memory. Do...

```Error: Unable to migrate {"url":"jdbc:postgresql://postgres:6678/mydb","user":"myuser","password":"xxx","defaultSchema":"public","migrationLocations":["src/flyway/migrations"]} {"errorCode":"UNABLE_TO_PARSE_RESPONSE","message":"Command successful but unable to parse Flyway response."}``` this is from a docker container the command was not successful as I checked in the db...

This PR upgrades `glob` to version 11.0.0. This eliminates the need for the `globPromise` utility function, as starting with glob v9 it uses promises rather than callbacks. It also removes...