<commit_before># CLI

Cucumber.js includes a executable file to run the features.

If you installed Cucumber.js globally, you may run it with:

```shell
$ cucumber.js
```

If you installed Cucumber locally, you may need to specify the path to the executable:

``` shell
$ ./node_modules/.bin/cucumber.js
```

The executable is also aliased as `cucumber-js` and `cucumberjs`.

**Note to Windows users:** Use `cucumber-js` or `cucumberjs` instead of `cucumber.js`.
The latter is causing the operating system to invoke JScript instead of Node.js,
because of the file extension.

## Running specific features

* Specify a feature file<commit_msg>documentation: fix global install docs<commit_after># CLI

Cucumber.js includes a executable file to run the features. After installing Cucumber in your project, you can run it with:

``` shell
$ ./node_modules/.bin/cucumber.js
```

The executable is also aliased as `cucumber-js` and `cucumberjs`.

**Note to Windows users:** Use `cucumber-js` or `cucumberjs` instead of `cucumber.js`.
The latter is causing the operating system to invoke JScript instead of Node.js,
because of the file extension.

**Note on global installs:** Cucumber does not work when installed globally because cucumber 
needs to be required in your support files and globally installed modules cannot be required. 

## Running specific features

* Specify a feature file
{'fraction_non_alphanumeric': 0.08080808080808081, 'fraction_numerical': 0.0, 'mean_word_length': 4.592741935483871, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, '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': '4061616', 'n_tokens_mistral': 414, 'n_tokens_neox': 390, 'n_words': 186}