Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reduce blueprint variance and *always* have typescript support by default. #258

Open
NullVoxPopuli opened this issue Feb 11, 2024 · 0 comments

Comments

@NullVoxPopuli
Copy link
Collaborator

NullVoxPopuli commented Feb 11, 2024

Like with Vite, Bun, Deno, ESBuild, Parcel, RSpack, etc, I think we should always support typescript as an output, rather than have two varying blueprint outputs / branches.

What's great is that even if someone doesn't like typescript, none of the typescript stuff actually gets in their way, and they can use JS / GJS just fine.

This has the added advantage tho of enabling Glint by default, which there is an RFC for, and would also require a configured tsconfig.json anyway in JS projects.

Now, maybe we keep the --typescript flag and add / remove the lint:types script, and that's it, keeping everything else the same.

Thoughts?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant