feat(paths): use TypeScript absolute paths

[C0ZEN]

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines
• Tests for the changes have been added/updated (for bugfix/feature)
• Docs have been added/updated (for bugfix/feature)

PR Type

What kind of change does this PR introduce?

• Feature (a new feature)
• Bugfix (a bug fix)
• Style (changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc))
• Refactor (a code change that neither fixes a bug nor adds a feature)
• Perf (a code change that improves performance)
• Test (adding missing tests or correcting existing tests)
• Build (changes that affect the build system, CI configuration or external dependencies)
• Chore (anything else), please describe:

What is the current behavior?

What is the new behavior?

Does this PR introduce a breaking change?

• Yes
• No

Other information

Fixes #267.

[C0ZEN]

The feature is all good except for one thing:
Running the production.

Parcel 1 can not handle for now the custom TypeScript paths.
A plugins exists nevertheless there are a lot of compilation errors and anyway, it is not maintained anymore.

It lead to two solutions:

• Wait for Parcel 2 (an official feature exists for the support)
• Remove parcel to use something else to build the production

For now, I prefer the first solution since this feature is not a must have.

[C0ZEN]

Waiting parcel-bundler/parcel#202

[C0ZEN]

@vvalembois no need to review it, the label waiting it set because it is not yet finished.