-
Notifications
You must be signed in to change notification settings - Fork 23
preloaders versus postloaders #1
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
Comments
Hi! I recommended to use it in |
Hmm I guess there's no way to pipe through additional loaders just once since TypeScript doesn't use WebPack's |
I'm not typescript compiler expert. I know that typescript itself uses |
@AppShipIt is your question answered? Did you get any more info from typescript experts? |
The root issue is TypeScript doesn't use WebPack to look up modules so this must be run in |
I'm trying to use this loader in my preLoaders but I'm still getting module not found error:
Here is my webpack config: Any idea why I'm getting this error? |
I will try this loader out, If i hit the above error I will try to fix it and submit a PR |
I believe my PR #8 fixed this issue. |
Hi, guys! FYI: I merged #8 and released |
Fix path issue for Node 6
Getting ready to try this out and wondered why you recommend
preloaders
instead ofpostloaders
? Should I not run it after PostCSS? I suppose it wouldn't get picked up by TypeScript then? Does that mean I should compile all my CSS inpreloaders
?The text was updated successfully, but these errors were encountered: