-
-
Notifications
You must be signed in to change notification settings - Fork 431
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[RFC] fix #270, support appendTsSuffixTo
config
#354
Conversation
appendTsSuffixTo
configappendTsSuffixTo
config
Don't worry; our test pack already caters for this
|
Is this ready for me to take a look at? I've been holding off until you give me the go-ahead. |
Yes, I have had flaky mark to vue's test. I think as long as the test does not exit with error. It is ok. The problem is |
appendTsSuffixTo
configappendTsSuffixTo
config
if (!hotAPI.compatible) return | ||
module.hot.accept() | ||
if (!module.hot.data) { | ||
hotAPI.createRecord("data-v-39ef11c7", __vue_options__) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here, the hash code is even emitted in bundle.js
Ah - in that case we can probably amend the test pack to cater for hashes in the bundle output as well. Actually this is kind of handy as this is the first example of a hot module reloading test in the test pack that I'm aware of. But I can take a look at that later |
Looks good to me 👍 |
Thanks! |
My pleasure; I've invited you to join TypeStrong so you'd have commit rights on ts-loader. In order that we can release I think we just need to do the following:
|
Do you fancy handling that? I'd propose that this should become ts-loader v1.1.0 |
I think I would provide the doc part. But releasing version goes to you 😉 |
That's fine 😄 - let me know when the docs are updated and I'll handle it |
Tests need more handling. Vue loader will produces absolute file path that is path dependent.And it even produce hash that is machine specific! How can I handle these cases?
Added _flaky mark to vue's test