fix: remove snackify command and references (#2763 by @frankcalise)

Author: frankcalise

docs/cli/Ignite-CLI.md

@@ -146,13 +146,6 @@ Removes all demo code (files, marked code blocks and lines) from the generated b
 
 Renames your current project to the desired new name. It'll also help switch the bundle identifier.
 
-### Snackify
-
-- `npx ignite-cli snackify`
-- Alias: `npx ignite-cli s`
-
-Turns an Ignite app into a project compatible with uploading directly to [Expo's Snack platform](https://snack.expo.dev/). This will create a separate branch to do so without worrying about modifying your current project structure.
-
 ### Update
 
 - `npx ignite-cli update`

docs/expo/Expo-and-Ignite.md

@@ -47,13 +47,3 @@ As a general rule of thumb, it's not a bad idea to start with Expo CLI. You'll a
 Where you generally will need to start considering diverging from standard Expo is when you need custom native functionality. Note that you can do a lot of custom native code with Expo's new [Config Plugins](https://docs.expo.dev/guides/config-plugins/) feature, too, so even native code is no longer much of a barrier.
 
 If you still would rather not use Expo Go / CLI, then Ignite is already ready for you -- no "ejecting" necessary. Expo refers to this as the "bare workflow." Just run `yarn ios` / `yarn android` and it'll build using the React Native CLI.
-
-## Expo Snacks
-
-You can't run an Ignite app directly in [Expo Snack](https://snack.expo.dev/), but we have a new command in Ignite that will set up your project so it can load in a Snack!
-
-This is one of the coolest ways to demo an app to someone else without having to send them a build. They can try your app out right in their browser!
-
-Note there are some limitations to Expo Snacks, and making those work (other than out of the box for Ignite) is beyond the scope of this documentation. You can learn more in [the Snack docs](https://docs.expo.dev/workflow/snack/).
-
-TODO: add documentation for `npx ignite-cli snackify` here.

src/commands/help.ts

@@ -61,10 +61,6 @@ module.exports = {
       ["npx ignite-cli remove-demo-markup", "npx ignite-cli remove-demo-markup --dry-run"],
     )
     p()
-    command("snackify        ", "Creates a new branch which can be imported as an Expo snack", [
-      "npx ignite-cli snackify",
-    ])
-    p()
     direction(
       `See the documentation: ${link("https://github.com/infinitered/ignite/tree/master/docs")}`,
     )