Incorrect content type when using typescript worker in dev server about webpack-dev-middleware

[alexander-akait]

Can you create reproducible test repo, I think you have a problem with configuration, there is not ts content-type, your worker should have the js extension

[ericvergnaud]

My worker is written in Typescript, so it has the tsextension (it's not a content-type)

new Worker(new URL("./TeknaWorkerThread.ts" , import.meta.url ), { type: "module"});

If I use .jsin the above example I get the following error:
Module not found: Error: Can't resolve './TeknaWorkerThread.js' in ...

Debugging the dev server, I found that the above call translates into an HTTP GET /static/.../TeknaWorkerThread.SOMEHASH.ts

Then the ts is transpiled to js. But middleware infers the content type from the ts extension.
My proposed fix is precisely to treat as js

I'll try to provide a simple reproducible example in the coming days, please don't close.

Check the links in the report, many people have bumped into this issue (and some of them have gone through extreme workarounds).

[ericvergnaud]

Creating a project from scratch with a simple worker does not exhibit the issue.
This could be a side effect of using acejs, needing more exploration.
Closing

[alexander-akait]

Just note - ts is still part of js ecosystem, so after transpiling the worker file should have js extensions, there is not ts content-type, ts is a part of js, like you can't have raw react code or vue code for execable files