Run npm deprecate on this package

[k2snowman69]

Just a suggestion but even your own readme does state this package is obsolete at this time. While it does seem the tail dropped off pretty hard in your weekly download stats, it might not be a bad idea to push it a bit further and run npm deprecate resolve-typescript-plugin "Use resolve.extensionAlias in webpack.config.js instead"

[djcsdy]

At the moment I'm still maintaining this for the benefit of people who use older versions of webpack. I'm not sure npm deprecate is the right thing to do for them.

[k2snowman69]

As in for 4.x.x, if so that's almost 3 years old now isn't it? If it's for 5.x.x, hopefully most people would be able to bump their minor/patch versions without little issue? The message could be Update to webpack@x.x.x or later and use resolve.extensionAlias in webpack.config.js instead?

[djcsdy]

I have clients who are still on webpack 4 for one reason or another, and for that matter some of my own projects are still on webpack 4. In some cases it's a lot of work to migrate and not really worth it. Everyone involved knows they're behind the latest webpack release and doesn't really need an extra deprecation warning to push them off this library when it will be maintained for the foreseeable future.

I will maybe print a deprecation notice during the build for webpack 5 users though. It'd be good to get people doing things the right way where possible.