apimock-rs 4.6.0 → 4.6.1
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.
- package/README.md +28 -1
- package/package.json +4 -4
package/README.md
CHANGED
|
@@ -79,7 +79,7 @@ npm run dev
|
|
|
79
79
|
| --- | --- |
|
|
80
80
|
| `npx apimock` | Run with all default parameters |
|
|
81
81
|
| `npx apimock -p 4000` | Run with custom port |
|
|
82
|
-
| `npx apimock -d tests` | Run with custom root dir on server response |
|
|
82
|
+
| `npx apimock -d tests/integration` | Run with custom root dir on server response |
|
|
83
83
|
| `npx apimock -c apimock.toml` | Run with config file giving rich features |
|
|
84
84
|
|
|
85
85
|
## Mock APIs easily 🎈 — just JSON and go
|
|
@@ -91,6 +91,33 @@ All you have to do to start up is just use folders and JSON without any config s
|
|
|
91
91
|
- 🌬️ Fast to boot, light on memory.
|
|
92
92
|
- 🪄 File-based and rule-based matching. Scripting supported.
|
|
93
93
|
|
|
94
|
+
### When should you use `apimock-rs` ?
|
|
95
|
+
|
|
96
|
+
Use it when:
|
|
97
|
+
|
|
98
|
+
- The backend is not ready yet.
|
|
99
|
+
- You need stable API responses for UI testing.
|
|
100
|
+
- You want offline development.
|
|
101
|
+
- CI tests require a predictable API.
|
|
102
|
+
- Your mock data is becoming large.
|
|
103
|
+
|
|
104
|
+
#### Handles real project scale
|
|
105
|
+
|
|
106
|
+
As your project grows, your mock API grows, too. Large mock datasets often cause problems:
|
|
107
|
+
|
|
108
|
+
- Slow startup
|
|
109
|
+
- High memory usage
|
|
110
|
+
- Crashes during UI testing
|
|
111
|
+
- Unstable CI runs
|
|
112
|
+
|
|
113
|
+
apimock-rs does not preload responses. Each response file is read only when a request arrives using non-blocking I/O. This keeps:
|
|
114
|
+
|
|
115
|
+
- Startup nearly instant
|
|
116
|
+
- Memory usage minimal
|
|
117
|
+
- Stable behavior under repeated requests
|
|
118
|
+
|
|
119
|
+
You can run automated tests and frontend development against it continuously. (Validated with k6 load testing.)
|
|
120
|
+
|
|
94
121
|
### 📖 Documentation
|
|
95
122
|
|
|
96
123
|
For more details, **🧭 check out [the docs](https://apimokka.github.io/apimock-rs/)**.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "apimock-rs",
|
|
3
|
-
"version": "4.6.
|
|
3
|
+
"version": "4.6.1",
|
|
4
4
|
"description": "A developer-friendly, featherlight and functional HTTP(S) mock server built in Rust.",
|
|
5
5
|
"author": "nabbisen<nabbisen@scqr.net>",
|
|
6
6
|
"license": "Apache-2.0",
|
|
@@ -19,9 +19,9 @@
|
|
|
19
19
|
"postinstall": "node postinstall.js"
|
|
20
20
|
},
|
|
21
21
|
"optionalDependencies": {
|
|
22
|
-
"@apimock-rs/bin-linux-x64-gnu": "4.6.
|
|
23
|
-
"@apimock-rs/bin-darwin-arm64": "4.6.
|
|
24
|
-
"@apimock-rs/bin-win32-x64-msvc": "4.6.
|
|
22
|
+
"@apimock-rs/bin-linux-x64-gnu": "4.6.1",
|
|
23
|
+
"@apimock-rs/bin-darwin-arm64": "4.6.1",
|
|
24
|
+
"@apimock-rs/bin-win32-x64-msvc": "4.6.1"
|
|
25
25
|
},
|
|
26
26
|
"keywords": [
|
|
27
27
|
"api",
|