vite-plugin-gherkin 0.0.0 → 0.0.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +5 -0
  2. package/package.json +13 -4
package/README.md CHANGED
@@ -4,6 +4,11 @@
4
4
 
5
5
  Check out [Cucumber](https://cucumber.io/) for more info regarding the Gherkin syntax.
6
6
 
7
+ > [!WARNING]
8
+ > This package is currently under development and is not intended for production use.
9
+ >
10
+ > That said, it is well-tested, we do not anticipate the API changing too drastically (at most, we _might_ change the methods for creating step definitions, but this seems unlikely), and we would love any feedback if you want to try it out!
11
+
7
12
  ## Getting Started
8
13
 
9
14
  In your [Vitest configuration file](https://vitest.dev/config/), import and register a `vitePluginGherkin` instance. This will allow you to include Gherkin feature files in your test configuration. Also, don't forget to include your step definitions in your test setup:
package/package.json CHANGED
@@ -1,7 +1,10 @@
1
1
  {
2
2
  "name": "vite-plugin-gherkin",
3
- "version": "0.0.0",
4
- "description": "",
3
+ "version": "0.0.2",
4
+ "repository": {
5
+ "url": "https://github.com/computost/vite-plugin-gherkin"
6
+ },
7
+ "description": "A Vitest plugin for running Gherkin specs.",
5
8
  "files": [
6
9
  "./dist/**/*"
7
10
  ],
@@ -17,8 +20,14 @@
17
20
  "default": "./dist/internal.js"
18
21
  }
19
22
  },
20
- "keywords": [],
21
- "author": "",
23
+ "keywords": [
24
+ "vitest",
25
+ "cucumber",
26
+ "gherkin",
27
+ "bdd",
28
+ "testing"
29
+ ],
30
+ "author": "Joshua Hogsett",
22
31
  "license": "ISC",
23
32
  "type": "module",
24
33
  "devDependencies": {