Discussion on: How I simplified my import paths in TypeScript

[Ryan Dsouza]

Doesn't work. Created a simple example with absolute imports and then compiled it via tsc. On running node dist/index.js the compiled JS throws an error as the absolute paths are not resolved.

[Andy Coupe]

Let's see your example buddy?

[Pacharapol Withayasakpunt]

It can be fixed via babel-plugin-module-resolver, though. Actually, Babel can do much more than tsc, and typescript can run under it as well.

Only just it doesn't help with the IDE.

[Ryan Dsouza]

I have two files:

src/index.ts

import { add } from 'utils/math'

console.log(add(2, 3))

src/utils/math.ts

export const add = (a, b) => a + b

My tsconfig.json - the rest is omitted

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

After transpiling this to JS, it doesn't work just by calling node dist/index.js, where dist is the output folder. So the baseUrl is just for TypeScript as Node doesn't understand that.

[Pacharapol Withayasakpunt]

Now I really need to compile to JavaScript as you mentioned.

I summed up the solution, but not exactly that pretty.

TypeScript, simplified import paths, and what you have to be careful

Pacharapol Withayasakpunt ・ Jul 23 ・ 2 min read

#typescript #babel #webdev #node