feat!: use a giant multiselect instead of individual toggles for features #695
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As we are adding more features, the number of toggles is getting out of hand. A multiselect could save a few keystrokes for most users.
I also take this opportunity to change the prompts library to
@clack/prompts
.(For context:
create-astro
,sv
,create-preact
,create-solid
,create-qwik
all use@clack/prompts
, whilecreate-vite
&create-next-app
useprompts
)The color library is changed to
picocolors
. IMOkleur
is still the smaller library because of treeshaking. But@clack/prompts
already comes withpicocolors
as a dependency, so by not addingkleur
, we save a few bytes.This is a proof-of-concept PR. I haven't put much consideration into the code style yet. Nor have I updated the i18n messages. I will do that if this change is accepted.
See the result in a screen recording:
