Run migration files as JS files instead of TS

[mohammadranjbarz]

[jainkrati]

@mohammadranjbarz is this solved by the PR you linked? if not, let @Meriem-BM progress on this further.

[mohammadranjbarz]

@mohammadranjbarz is this solved by the PR you linked? if not, let @Meriem-BM progress on this further.

No it's not solved(I read the related PR it seems unrelated to this) but I think https://github.com/Giveth/impact-graph/issues/1481 can be a better (easier with bigger impact issue) one for Meriem, WDYT?

[jainkrati]

@mohammadranjbarz pls guide Ali Ebrahmi to take this up

[mohammadranjbarz]

Automatically

Cool, I messaged him in DM will schedule a call about this issue

[mohammadranjbarz]

@ae2079 This lie in package.json do the job, please modify it to run migrations as JS files "db:migrate:run:production": "NODE_ENV=production npx typeorm-ts-node-commonjs migration:run -d ./src/ormconfig.ts",

[maryjaf]

should this issue test from QA side? If yes please add more data

[ae2079]

@maryjaf I think it doesn't need any tests, if staging is working and no problem exists (like today's server internal error), it is ok.

[ae2079]

I just merged it and successfully deployed it on staging and it seems ok

[ae2079]

It seems there is an issue with running migration files in staging because of merging a PR related to this issue, And @mohammadranjbarz reverted it to fix staging migrations

[RamRamez]

@mohammadranjbarz is this issue still relevant?

[mohammadranjbarz]

@mohammadranjbarz is this issue still relevant?

I think we can ignore this, as we had problem when @ae2079 implemented it