Chunpeng Huo
Chunpeng Huo
I know nothing about TS (one less problem for me than all of you) :-) But I don’t mind someone to convert the code base. The main problem of the...
I think our webpack loader should support the result of html-loader, so that we can chain them. Let the html-loader process it first, then our loader. I will get back...
I am aware of that. I meant "should add support of ...".
Troublesome, not sure how to deal with the output of html-loader. An example of the output of html-loader. ```js // Imports import ___HTML_LOADER_GET_SOURCE_FROM_IMPORT___ from "file:///Users/huocp/playground/my-app/node_modules/html-loader/dist/runtime/getUrl.js"; var ___HTML_LOADER_IMPORT_0___ = new URL("./test.jpg",...
Thought about similar approach, then we need to expose all html-loader options.
I think this issue is more than just ``. The bottom conflict is that Aurelia 2 needs to preprocess html string because we moved conventions from runtime (Aurelia 1) to...
It's difficult to support webpack loader chaining. I think the only practical solution is to wrap html-loader in our loader as @MaximBalaganskiy suggested. It's not pretty but could work. Other...
BTW, local template can add runtime support of `` too. Conventions would not process anything on (or inside) the local template tag.
Thx. I only tried latest webpack skeleton, not the old one. I am not sure when was this stopped working.