fix(JS/TS): use webpack resolver instead of Node.js resolver

[ggodlewski]

PR Checklist

• The PR title follows our guidelines: https://github.com/NativeScript/NativeScript/blob/master/CONTRIBUTING.md#commit-messages.
• There is an issue for the bug/feature this PR is for. To avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it.
• You have signed the CLA.
• All existing tests are passing: https://github.com/NativeScript/nativescript-dev-webpack/blob/master/CONTRIBUTING.md#testing-locally-by-running-e2e-tests
• Tests for the changes are included.

What is the current behavior?

TS files for custom xml components are not budled.

What is the new behavior?

Fixes #627

[sis0k0]

test

[sis0k0]

Great work!

[radeva]

Hi @ggodlewski ,

Congratulations on being one of the winners in the {N} First-time contributors contest!

You can claim your prize by contacting us at nativescriptwinners[at]progress.com not later than Nov 30th 2018 . Make sure you send us the following info: 
👉Your full name 
👉Your email 
👉Your country or residence 

Best regards,
The NativeScript Team

[ggodlewski]

Thanks a lot :)

@sis0k0 I think something went wrong with merging into master? Can you check it?
I'd really appreciate if this issue is fixed in the next release.

[sis0k0]

Many thanks for the fix, @ggodlewski! It will be released as part of nativescript-dev-webpack v0.18.4.