Extract response from .har file and create JSON mocks for mock server.
npm install -g har-to-mocks
or by npx
npx har-to-mocks [path to .har] [path mock/api folder] --dry-run
File can contain hundreds of requests so it's important to be able filter data. For filtering you can use flags:
- (
--url) for filtering by match in the url. Search is case sensitive - (
-m,--method=GET) for filter specific method. Default value is 'GET' - (
-t,--type=xhr) for filtering request type. Default value is 'xhr'
Video example: YouTube [email protected].
example:
$ har-to-mocks ./file.har --url=api/service --method=GET
will display:
Filtered requests:
Name Method Path
─────────────────────── ────── ───────────────────────────
userRoles GET /api/service/userRoles
currentUserId GET /api/service/currentUserId
active GET /api/service/clients/active
If output folder is not specified mocks will not be written.
Export structure is prepared for connect-api-mocker. After successful filtering request just add second argument which will be path to connect-api-mocker's folder for mock/api.
WARNING: When second argument is defined cli will write files. To avoid unwanted overwrite use --dry-run flag to skip writing part of process.
example:
$ har-to-mocks ./file.har ./mocks --url=api/service --method=GET --dry-run
will display:
Filtered requests:
Name Method Path
─────────────────────── ────── ───────────────────────────
userRoles GET /api/service/userRoles
currentUserId GET /api/service/currentUserId
active GET /api/service/clients/active
Folder tree which will be applied:
└─ mocks
└─ api
└─ service
├─ userRoles
│ └─ GET.json
├─ currentUserId
│ └─ GET.json
└─ clients
└─ active
└─ GET.json
No files were written. If you want to write files remove the (--dry-run) flag.