chore: rename package to react-components

Author: davidjgoss

CHANGELOG.md

@@ -10,6 +10,7 @@ and this project adheres to [Semantic Versioning](http://semver.org/).
 - Render hook names if present ([#137](https://github.com/cucumber/cucumber-react/pull/137))
 ### Changed
 - Scenario outline styling - Examples changed to H3 and aligned with steps
+- Package name is now `@cucumber/react-components` for clarity
 
 
 ## [19.2.0] - 2022-03-25

README.md

@@ -1,6 +1,6 @@
-# Cucumber-React
+# @cucumber/react-components
 
-Cucumber-React is a set of React components for rendering Gherkin documents and Cucumber results.
+> A set of React components for rendering Gherkin documents and Cucumber results.
 
 ## Screenshot
 

package-lock.json

@@ -1,5 +1,5 @@
 {
-  "name": "@cucumber/react",
+  "name": "@cucumber/react-components",
   "version": "19.2.0",
   "description": "React components for Cucumber",
   "main": "dist/src/index.js",

package.json

@@ -4,7 +4,7 @@ Drop message ndjson files in this directory (with `.ndjson` extension).
 They will be picked up by `acceptance.spec.tsx` which will try to render them.
 
 This is useful whenever we come across a message stream that causes a runtime error
-in HTML Reporter or any other tool depending on `@cucumber/react` so we can diagnose
+in HTML Reporter or any other tool depending on `@cucumber/react-components` so we can diagnose
 and fix any issues.
 
 Sometimes we will get message files from users that might be useful for reproducing a bug.