<commit_before># Ignite Commands

This document reviews the commands that the Ignite 2.0 CLI provides. This guide
assumes that you've installed Ignite; if you haven't, then check out our Getting
Started Guide [here]().

Enter `ignite` into your command line to see the commands offered by Ignite 2.0.


### Add

`add (a)`

Adds an Ignite plugin.

Ignite plugins are just node plugins. They must have an index.js file with an
`add` function. Calling `ignite add <plugin name>` calls this function. Its job is to add the
desired plugin to your project. It may modify files in your project.

You can find published Ignite plugins on npm, but you can also add unpublished
plugins from source. To do so, simply pass the path to the plugin instead of its
name.


### Doctor

`doctor`

Checks your dev environment for dependencies.
  
This command checks your dev environment for dependencies. It will list the version of
system, JavaScript, React Native, Ignite, Android, and iOS dependencies
available on your machine, and where applicable, their location. This may be
useful when debugging or when seeking help for an issue in forums.
  
  
### Generate
 
`generate (g)`

Generates some files.

This command will use generators to create files for you. It looks at
node_modules for folders starting with `ignite`, then looks in those for
generators. Generators have a folder called `templates`, which (naturally)
contain the templates that determine the contents of the files the generator
generates.
  
### New
  
`new (n)`

Generate a new React Native project with Ignite.

`ignite n` uses `react-native init`, then adds files specific to Ignite.
  
When you execute this command, Ignite 2.0 will give you a series of options for
your new project regarding what libraries you would like to use.

`ignite new` has various -- commands. ex: `ignite n MyApp --template
infinitered` creates the project with a certain set of opinions regarding
proejct structure.

  
### Plugin

`plugin (p)`

Manages ignite plugins

This command allows you to add or list currently available plugins (coming
soon).

When creating a plugin, you can choose to include an example component and example
command or generator.
  
### Remove

`remove (r)`

Removes an Ignite plugin.
  
The opposite of `ignite add`, this removes a plugin from your project. Be warned
that this may change other files in your project, e.g. to undo changes made by
`add`. There is a potential for danger here, so you may want to consider using<commit_msg>Add more to commands doc<commit_after># Ignite Commands

This document reviews the commands that the Ignite 2.0 CLI provides. This guide
assumes that you've installed Ignite; if you haven't, then check out our Getting
Started Guide [here]().

Enter `ignite` into your command line to see the commands offered by Ignite 2.0.


### Add

`add (a)`

Adds an Ignite plugin.

Ignite plugins are just node plugins. They must have an index.js file with an
`add` function. Calling `ignite add <plugin name>` calls this function. Its job is to add the
desired plugin to your project. It may modify files in your project.

You can find published Ignite plugins on npm, but you can also add unpublished
plugins from source. To do so, simply pass the path to the plugin instead of its
name.


### Doctor

`doctor`

Checks your dev environment for dependencies.
  
This command checks your dev environment for dependencies. It will list the version of
system, JavaScript, React Native, Ignite, Android, and iOS dependencies
available on your machine, and where applicable, their location. This may be
useful when debugging or when seeking help for an issue in forums.

Especially handy is `ignite doctor --bug`, which opens webpage with pre-filled
out issue on Ignite's github. ***[NOTE: this doesn't seem to work yet]***
  
  
### Generate
 
`generate (g)`

Generates some files.

This command will use generators to create files for you. It looks at
node_modules for folders starting with `ignite`, then looks in those for
generators. Generators have a folder called `templates`, which (naturally)
contain the templates that determine the contents of the files the generator
generates.

Run `ignite generate` by itself and it will list available generators. Run
`ignite generate <generator name>` to use the desired generator.
  
### New
  
`new (n)`

Generate a new React Native project with Ignite.

`ignite n` uses `react-native init`, then adds files specific to Ignite.
  
When you execute this command, Ignite 2.0 will give you a series of options for
your new project regarding what libraries you would like to use.

`ignite new` has various -- commands. ex: `ignite n MyApp --template
infinitered` creates the project with a certain set of opinions regarding
proejct structure.

  
### Plugin

`plugin (p)`

Manages ignite plugins

This command allows you to create a plugin or list currently available plugins (coming
soon).

When creating a plugin, you can choose to include an example component and example
command or generator.
  
### Remove

`remove (r)`

Removes an Ignite plugin.
  
The opposite of `ignite add`, this removes a plugin from your project. Be warned
that this may change other files in your project, e.g. to undo changes made by
`add`. There is a potential for danger here, so you may want to consider using
{'fraction_non_alphanumeric': 0.05666041275797373, 'fraction_numerical': 0.00225140712945591, 'mean_word_length': 4.130895091434072, 'pattern_counts': {'":': 0, '<': 6, '<?xml version=': 0, '>': 6, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4421972', 'n_tokens_mistral': 1435, 'n_tokens_neox': 1379, 'n_words': 831}