db-migrate / db-migrate/plugin-typescript

Usage with non-default tsconfig config

Abierto
#13 0 comentarios 0 reacciones 0 asignados Ver en GitHub
Lenguaje dominante
JavaScript
Estrellas
7
Forks
10
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

Hi, we are happily using db-migrate in an nx mono-repo. When we started using tsconfig-paths, our migrations stopped working. As we have a custom tsconfig we need to point the script to, we tried using: `npx ts-config --project tsconfig.migration.ts -r tsconfig-paths/require -r -- node_modules/db-migrate/bin/db-migrate`. This still didn't work correctly.

So digging deeper, we found out that db-migrate-plugin-typescript requires ts-node again and this time without configuration. This seems to overwrite whatever we have configured in the command line. By simply forking this repo and commenting out the require, we were able to get things running again.

**My questions**:
- Do I need to register the `.ts` extension via a plugin and keep my fork?
- Could this plugin only require ts-node if it was not already registered?

Thank you!

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/81615705-usage-with-non-default-tsconfig-config?utm_campaign=plugin&utm_content=tracker%2F45756452&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F45756452&utm_medium=issues&utm_source=github).

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.