I haven't been able to get this loader to function. I set it up as described in the docs, require a jade file, and get a parse error with "unexpected token". It seems like webpack is trying to parse the html as javascript. Even the most basic and bare bones setup is giving me this error.
That being said, I did go into the source and log some things out. It is without a doubt compiling the jade and returning the source correctly as a string. It doesn't seem like a bug in the loader, I'm just curious whether it's actually possible to require something that is not javascript and have webpack not crash, which doesn't appear to be the case for me. But of course I might be missing something, if I am please let me know!
selkinvitaly
commented
8 years ago
I haven't been able to get this loader to function. I set it up as described in the docs, require a jade file, and get a parse error with "unexpected token". It seems like webpack is trying to parse the html as javascript. Even the most basic and bare bones setup is giving me this error.
That being said, I did go into the source and log some things out. It is without a doubt compiling the jade and returning the source correctly as a string. It doesn't seem like a bug in the loader, I'm just curious whether it's actually possible to require something that is not javascript and have webpack not crash, which doesn't appear to be the case for me. But of course I might be missing something, if I am please let me know!