New Ignite walkthrough

I’ve been rethinking the whole “Ignite CLI runs without asking any questions” thing we have going on. There are some benefits to it, but there’s also some benefit of asking the questions in a walkthrough where it can feel exciting / inspire more confidence.

$ npx ignite-cli new

🔥 About to Ignite your new app! 🔥

 ↣ What do you want to call it? PizzaApp
 ↣ What bundle identifier? com.infinitered.pizzaapp
 ↣ Want to use Expo? Y/n
 ↣ Want us to install dependencies for you? (adds 50-100 seconds) Y/n

In the future, if you'd like to skip the questions, you can run Ignite with these options:

  npx ignite-cli new PizzaApp --bundle=com.infinitered.pizzaapp --expo --install-deps

<Ignite continues>

Note that we give them the command for skipping the questions next time, if they want.

Primarily, this surfaces the Expo and bundle identifier options, which are somewhat hidden otherwise.

I think this makes sense to include in Maverick.

[joshuayoes]

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 time we make a change).

However, adding a lock file would also make boilerplates more stable because we’d have the dependencies pinned.

I’m going to remove the lock file from the boilerplate, and then we can add the extra complexity of managing 3 lock files if we start getting issues related to dependencies.

[jamonholmgren]

I think @joshuayoes that I’d just say “For CI, use -y to bypass any non-provided options and use defaults.” The more I think about it, the less I like the behavior of skipping options if any are provided.

With the list you did, I like it, but I’d remove the “where do you want to start your project” and only prompt the overwrite if the folder exists (it’s not necessary to even show it if the folder doesn’t).

The rest looks really good. The package manager should default to whatever we would use normally.