Joshua Yoes

I was thinking of running a similar behavior of `npm init`, where you have a few options: - By default, all `npm init` will prompt you to go through all...

```ts export interface Options { /** * Log raw parameters for debugging, run formatting script not quietly * @default false */ debug?: boolean /** * Remove existing directory otherwise throw...

These are the options that I am planning on implementing. All options will be available in `parameters.options` passed via a flag in the command like `--install-deps`, but the debug and...

> I'm thinking over the "If only partial options are passed, assume existing defaults for not included flag options". My initial reaction is that's not super intuitive to me I...

> One note: bundle is used on iOS and Android, despite the note. (This is why comments are a two-edged sword....) That is a good catch! I'll update that comment

Here is a sample of what I imagined for the question prompts ``` $ npx ignite-cli new 🔥 About to Ignite your new app! 🔥 ↣ What do you want...

Currently, our package manager behavior is to prefer the following order: - Vanilla: pnpm -> yarn -> npm - Expo: yarn -> npm Previously, we didn't let people use pnpm...

Here is an updated table of the behavior I'm planning on implementing based on @jamonholmgren's feedback | Command | Question Prompts? | Description | ------------ | --------------------- | ------------- |...

I think for now, I would prefer to remove adding a lock file because that would introduce a lot more maintenance overhead (adding one for yarn, npm, and pnpm every...

Resolved by https://github.com/infinitered/ignite/pull/1999