Fixed getMigration filetype for built versions

[d-tsaruk]

Pull Request Description:

Subject: [PATCH] Fixed getMigrations filetype for built versions

Summary:

This patch addresses an issue with the getMigrations function in src/migrator.ts where it was only filtering .ts files for migrations. The fix now allows the function to correctly handle both .ts and .js files, ensuring compatibility with built versions of the application that use JavaScript files instead of TypeScript.

Changes:

• Updated the getMigrations method to filter both .ts and .js files in the migrations folder.
• Introduced a conditional check to support both development and production environments, ensuring that migrations can be found whether the application is running with TypeScript or after being built to JavaScript.

Impact:

This change ensures that migrations can be correctly loaded regardless of whether the application is running in development mode (using TypeScript) or in production (using JavaScript after the build).

Related Issues:

• Fixes migration file loading issue for production builds.

Testing:

• Ensure that both .ts and .js migration files are correctly detected and processed when the application is built and deployed.

Additional Notes:

• The modification simplifies handling of migration files across environments and ensures smoother operation during the build and deployment phases.

[ilovepixelart]

Hello @d-tsaruk thanks for the contribution, I see the issue you trying to solve, can I ask you to include some test in scope of this change.

Also in case you are not aware, you don't actually need to compile migration files, you can simply put them outside of your src folder and exclude them from tsconfig.json like shown here: https://github.com/ilovepixelart/ts-express-swc this is the intended way to use this package

To test what described above you can clone mentioned project and just run commands bellow

npm i
npm run build:ts
npm run start

[d-tsaruk]

Hello @d-tsaruk thanks for the contribution, I see the issue you trying to solve, can I ask you to include some test in scope of this change.

Also in case you are not aware you don't actually need to compile migration files, you can simply put them, outside of your src folder like shown here: https://github.com/ilovepixelart/ts-express-swc this is the intended way to use this package

npm i
npm run build:ts
npm run start

Hi. I'll add tests

Yep I understand that i can move migration files from my main source folder to not build its. but it make some another problems.

In this case i can use mongoose models in migrations and it very comfortable for me in case my application. but if i'm not build migration files - i should not build (or copy) mongoose model files...

[ilovepixelart]

Regarding biome issue in approved run, you can simply run command bellow, it should handle the case automatically

npm run biome:fix

[d-tsaruk]

@ilovepixelart biome fixed

[d-tsaruk]

i think that we don't need add tests for .js extension, because its just for builded files

[ilovepixelart]

Ok, we are not generating .js files anyway lets push