Using in both 'dev' and 'build' modes

I’ve just installed module-alias and it works great with my TypeScript app using path aliases after I build the app.

tsconfig.json:

    "baseUrl": "./src",
    "paths": {
      "@src/*": ["./*"],
      "@utils/*": ["utils/*"]
    }

package.json

  "_moduleAliases": {
    "@src": "dist",
    "@utils": "dist/utils"
  },

However now dev mode the app is not working, it seems like module-alias completely takes over the path alias resolutions and even in dev mode the app tries to pull .js files from dist (instead of using .ts from src).

For development I use ts-node-dev:

ts-node-dev --respawn --no-notify -r tsconfig-paths/register ./src/index.ts

Am I doing something wrong?

[jazzfog]

Makes sense. Thank you!

[jazzfog]

Thanks @Kehrlann, I will give it a shot. Thought I see that it will require customization to the command I use to start the app, if it is the case and I can’t just run node dist/index.js then I could just probably customize my yarn start command starting my dev server and just add some ENV variable, then check it’s existence in my code and omit module-alias/register then it should work in dev as well. It is even kinda better because it does not restrict you in the way you start the final build, if it makes sense.