Skip to content

feat(react-vite): prefer @msw/data for stateful mocks #40

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
v-byte-cpu merged 1 commit into from
Jun 8, 2026
Merged

feat(react-vite): prefer @msw/data for stateful mocks #40

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion skills/react-vite-structure/references/platform-services-and-di.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -131,7 +131,11 @@ export const webProductService: ProductService = {

## Additional Platform Implementations

Add `tauri`, `mock`, or `composite` implementations only when the feature needs them. The interface still stays in the feature:
Add `tauri`, `mock`, or `composite` implementations only when the feature needs them.

For first-pass `mock` service implementations that need reusable state, CRUD, filtering, or relations, prefer an `@msw/data`-backed store over ad hoc arrays or maps. Simple injected fake services are still fine for one-off tests, static Storybook states, or behavior that does not need realistic state transitions.

The interface still stays in the feature:

```ts
// features/projects/services/projectService.ts
Expand Down