feat!: stop passing isTypeScript to remix.init script

[MichaelDeBoey]

Follow-up of @markdalgleish's #6887

[changeset-bot]

🦋 Changeset detected

Latest commit: 7eeb408

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 16 packages

Name	Type
create-remix	Major
@remix-run/dev	Major
remix	Major
@remix-run/architect	Major
@remix-run/cloudflare	Major
@remix-run/cloudflare-pages	Major
@remix-run/cloudflare-workers	Major
@remix-run/css-bundle	Major
@remix-run/deno	Major
@remix-run/eslint-config	Major
@remix-run/express	Major
@remix-run/node	Major
@remix-run/react	Major
@remix-run/serve	Major
@remix-run/server-runtime	Major
@remix-run/testing	Major

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[markdalgleish]

This was deliberately left in as a backwards compatibility layer for existing templates. If we do this, we might want to fast-follow the v2 release with some PRs to community templates that rely on this flag.

[MichaelDeBoey]

@markdalgleish I'm happy to create PRs for our stacks + the official Netlify & Vercel templates (if needed)

I can also do the top 10 listed repos with remix-stack tag if wanted

[brophdawg11]

IIRC we would prefer to remove remix init entirely eventually? Is there a large benefit to removing this flag? It sounds like it just creates a bunch more work for us (per #7099 (comment)) so curious if the the juice is worth the squeeze?

[MichaelDeBoey]

Imo it makes it more clear to template/stack creators that we're not supporting JS transpilation anymore so that they have to provide a JS version themselves if they want to support that

[markdalgleish]

IIRC we would prefer to remove remix init entirely eventually? Is there a large benefit to removing this flag? It sounds like it just creates a bunch more work for us (per #7099 (comment)) so curious if the the juice is worth the squeeze?

I looked into removing it as part of the new create-remix work but found that it will take us more work to remove it than to keep it at the moment due to the way our stacks heavily rely on it. I ultimately felt that removing remix init would be a bunch of work (and churn for community templates) without much payoff. I'm still in favour of removing it if there's a good opportunity in the future though.

[MichaelDeBoey]

I would say: the longer we keep it, more templates/stacks can start to rely on it, so more templates/stacks will need an update to remove it from their codebase

[brophdawg11]

I'm on board with whatever you guys think - you've got more context than I do here - just want to avoid creating any unnecessary work :). I don't think updating the top 10 community stacks is totally necessary if we've got this clearly called out as a breaking change in v2, but if the LOE is small than it could be a nice addition.

[MichaelDeBoey]

Then I would just merge this one
@markdalgleish WDYT?

[markdalgleish]

Yep, let's merge it.

[github-actions]

🤖 Hello there,

We just published version v0.0.0-nightly-b1149bb-20230810 which includes this pull request. If you'd like to take it for a test run please try it out and let us know what you think!

Thanks!