Are pure JavaScript projects that default to JS code style instead of TypeScript completely unwelcome by Cloudflare’s official stance?

[gowy222]

Existing documentation URL(s)

https://developers.cloudflare.com/pages/framework-guides/deploy-a-remix-site/

clear && pnpm create cloudflare@latest my-remix-app --framework=remix --platform=pages --git=false --deploy=false --ts=false

result will still be TS

and the bug thing:

clear && pnpm create cloudflare@latest my-remix-app --framework=remix --platform=pages --git=false --deploy=false --ts=false --lang=js

╭ Create an application with Cloudflare Step 1 of 3
│
╰  ERROR  Error: The `--ts` argument cannot be specified in conjunction with the `--lang` argument
root@693cbdfeff43:/workspace# 

This is really odd, isn’t it? Why have a --ts option that can’t be used alongside --lang (which even supports Python)? It’s very confusing. Logically, --ts=false --lang=js shouldn’t conflict—unless it’s a flaw in the architectural design.

Are pure JavaScript projects that default to JS code style instead of TypeScript completely unwelcome by Cloudflare’s official stance?

What changes are you suggesting?

The premise of supporting TS should be to support its father pure JS

For a simple page, TypeScript eats up too much performance and drains excessive effort across the entire project.
For developers who already code with strict discipline, its type system is nothing but a waste of time—rigorous thinking matters far more than typing.
The only real upside is making future team handoffs easier, but types won’t stop lazy developers from introducing logic bugs.

Additional information

No response

[kodster28]

Howdy @gowy222, apologies for the redirect here, but it'd be better to raise this issue over in https://github.com/cloudflare/workers-sdk.

We're a docs repo (and a docs team), so a bit too far from this bug report to take action with it. Want you to get your issue in a more visible, actionable place.