transformer: non-JSX file doesn't need to update options from comments

[Dunqing]

          > Weird, shouldn't have any performance impact in this benchmark, as it applies when the source type is JSX. Could you investigate why this is happening?

SourceType::from_path interprets .js extension as JSX, so antd.js benchmark is treated as JSX.

Originally posted by @overlookmotel in #10983 (comment)

[Dunqing]

I am not sure if this is incorrect in the benchmark or SourceType::from_path. Sometimes, indeed, some .js files include JSX syntax, but the benchmark antd.js definitely does not include it.

[Boshen]

SourceType::from_path treats .js as .jsx to maximize success rate for the linter.

I think we should only do this change in the linter.

[overlookmotel]

Isn't it quite common in React projects to have all your component files with extension .js even though they contain JSX?

I agree that we should not treat .js as JSX by default (ditto .mjs and .cjs). But just flagging that it's probably quite a large breaking change. I'm not sure how it'll affect Rolldown.

[Dunqing]

Isn't it quite common in React projects to have all your component files with extension .js even though they contain JSX?

As far as I know, it should be quite uncommon.

I agree that we should not treat .js as JSX by default (ditto .mjs and .cjs). But just flagging that it's probably quite a large breaking change. I'm not sure how it'll affect Rolldown.

I think this is configurable, so we don't need to worry about it. /cc @IWANABETHATGUY

[IWANABETHATGUY]

We only use this api in tests and tasks(code generator),

So it will not affect rolldown.