Fix getOptionsHash when two options has different props but same values.

[meowtec]

Fix the issue when I use both lang="tsx" and lang="ts" in vue single file components.
For lang="ts":

{
  appendTsSuffixTo: [/\.vue$/],
  transpileOnly: true,
}

For lang="tsx":

{
  appendTsxSuffixTo: [/\.vue$/],
  transpileOnly: true,
}

They get the same hash because getOptionsHash use only values for hashing.
So for tsx vue file, it reuses the loader options which is only for ts vue, which add .ts suffix not .tsx.
That can lead to wrong compilation result.

[meowtec]

There is still something wrong, let me find it out.

[meowtec]

The another issue is that I using thread-loader with ts-loader. It serializes the RegExp object to {}.

[johnnyreilly]

For some reason the Travis build has failed...

[meowtec]

Allow to use string in appendTsSuffixTo.

If ts-loader runs in child process, the RegExp object will be serialized and unserialized to {}, then the match result will always be True.

'/User/xxx/project'.match({})
// ["e", index: 2, input: "User", groups: undefined]

In this case we should use string instead of RegExp.

[johnnyreilly]

Looks good - do you want to add an entry to the CHANGELOG.md and increment the package.json?

By the way, you might not need thread-loader:

https://blog.johnnyreilly.com/2018/12/you-might-not-need-thread-loader.html

[johnnyreilly]

Just published https://github.com/TypeStrong/ts-loader/releases/tag/v8.0.3 - thanks for your work! 🤗🌻