[FEAT] Optionally output migrations as Javascript files instead of TypeScript

[foxxor]

Description of change

This is a proposal that attempts to address the discussion here: #1675

Added a new -o / --outputJs option to the migrate:create and migrate:generate commands, to be able to output directly to Javascript. This would help for Javascript only projects in which having TypeScript files as part of the project would complicate maintenance, and eliminates the need for an extra ts-node transpiling command to run the migrate:run.

Tested locally the migrate:create, by manually running the compiled project cli.js file. I didn't manage to link my local build version to work with the generate. I'd like some help or instructions to be able to compile and test the other command.

Pull-Request Checklist

• Code is up-to-date with the master branch
• npm run lint passes with this change
• npm run test passes with this change
• This pull request links relevant issues as Fixes #0000
• There are new or updated unit tests validating the change
• Documentation has been updated to reflect this change
• The new commits follow conventions explained in CONTRIBUTING.md

[nebkat]

Code wise looks good, you should squash the commits into a single feat: Javascript file migrations output.

[foxxor]

@nebkat Done 👍

[pleerock]

Thank you for contribution! 🎉

Can you please add docs about this feature in a separate PR?
Also would be really great if you can add tests to this feature.

[foxxor]

Thanks @pleerock I will add the docs, tests and will submit a PR then. 👍

[foxxor]

Added documentation and tests on: #7294

cc @pleerock

[ajesicus]

@foxxor Great job, I'm expecting this feature for sometime. Thank you very much.

It would be great if you could also update sample repo for javascript+babel.
I would suggest

• few migration scripts
• add migration scripts into package.json

[foxxor]

@ajesicus Sure!