Easily manage your mock request handlers
To get started, install the package via npm:
npm install -D @custardcream/msw-devtools msw
Before integrating, make sure you have set up MSW in your project.
npx msw init public
import { setupWorker } from "msw/browser"
import { installMSWDevtools } from "@custardcream/msw-devtools"
const enableMocking = async () => {
// Exclude devtool from production builds
if (import.meta.env.DEV) {
return await installMSWDevtools({
initialOpen: true, // Automatically open devtool on start
setupWorker: setupWorker(), // Initialize MSW worker
options: { // MSW worker options
onUnhandledRequest: "bypass",
}
})
}
}
// You can use any framework you like
enableMocking().then(() =>
ReactDomClient.createRoot(document.getElementById("root")!).render(
<React.StrictMode>
<App />
</React.StrictMode>
)
)
const enableMocking = async () => {
if (import.meta.env.DEV) {
return await installMSWDevtools({
initialOpen: true,
setupWorker: setupWorker(),
options: {
onUnhandledRequest: "bypass"
}
})
}
}
enableMocking().then(() => {
const app = createApp(App)
app.mount("#app")
})
In various cases, you may want to make response data dynamic.
You can achieve this by using the sequential response feature.
This feature allows you to change the response data for each request sequentially.
(experimental) This feature is experimental and may change in the future.
Using @custardcream/msw-devtools-server
, you can create and update the request handler JSON file in real time through the Devtools UI.
Conversely, you can also directly edit the JSON file to reflect changes in your developing app in real time.
npm install -D @custardcream/msw-devtools-server
// Add isUsingServer option to installMSWDevtools
installMSWDevtools({
setupWorker: setupWorker(),
isUsingServer: true // Enable server usage
})
Be sure to start the server before you begin developing your project.
For example, a Vite app can be configured as follows (using concurrently
):
{
"scripts": {
"start": "concurrently \"msw-devtools-server -o ./mock\" \"vite\""
}
}
Devtools prioritizes the JSON file over the Request Handler information stored in local storage. Please note that the values stored in local storage may be overwritten when connecting to the server.
-o, --output <path>
: Output file path(or directory) for the generated JSON file. (default: ./mock-list.json
)-r, --recursive
: Read all JSON files in the directory.You can manage JSON files by dividing them into folders.
msw-devtools-server --output ./mocks --recursive
mocks
ββββfolder1
β β mock-list.json
β β any-name.json
β β
β ββββsubfolder1
β β mock-list.json
β β ...
β
ββββfolder2
β JSON_FILE_NAME.json
You must specify a directory for the
-o, --output
option.Failure to follow the JSON file schema may result in errors.
The JSON file generated by @custardcream/msw-devtools-server
follows the following scheme (in typescript):
/**
* JSON file scheme for managing MSW request handlers
*/
type JsonMock = Array<{
url: string
method: MethodOption
status: StatusOption
response: JsonMockResponse
responseDelay: number
isActivated: boolean
}>
type MethodOption =
| "get"
| "post"
| "put"
| "patch"
| "delete"
| "options"
| "head"
type StatusOption = "200" | "201" | "400" | "401" | "403" | "404" | "500"
type JsonMockResponse =
| {
type: "single"
response: any
}
| {
type: "sequential"
response: any[]
}