ts-loader / webpack 2 #912

New Issue

fergalmoran · 2025-08-09T17:18:09Z

fergalmoran commented

2025-08-09 17:18:09 +00:00

Originally created by @johnnyreilly on 3/23/2017

Hello!

I'm one of the maintainers of ts-loader. Listening to the live asp net show I realised you're using it in your templates. (Super cool BTW!)

There's 2 observations I'd make:

At present you're using the 0.8^ version of ts-loader. I'd probably advise switching to the 1.x version if you're targeting webpack 1. The "breaking changes" version change was only really about dropping official support for node 0.12 (which has now been end of lifed). I'd be happy to submit a PR to do this if you'd like?
webpack 2 has now been released (around Christmas time). It might be good to move to using webpack 2 in the templates. ts-loader moved to 2.x for webpack 2.

*Originally created by @johnnyreilly on 3/23/2017* Hello! I'm one of the maintainers of ts-loader. Listening to the live asp net show I realised you're using it in your templates. (Super cool BTW!) There's 2 observations I'd make: 1. At present you're using the 0.8^ version of ts-loader. I'd probably advise switching to the 1.x version if you're targeting webpack 1. The "breaking changes" version change was only really about dropping official support for node 0.12 (which has now been end of lifed). I'd be happy to submit a PR to do this if you'd like? 2. webpack 2 has now been released (around Christmas time). It might be good to move to using webpack 2 in the templates. ts-loader moved to 2.x for webpack 2.

fergalmoran closed this issue

2025-08-09 17:18:09 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/JavaScriptServices#912