Rename "composeMocks" to better describe what it does

Is your feature request related to a problem? Please describe.

I find it confusing that composeMocks() function composes request handlers, and not mocks.

Describe the solution you’d like I think renaming composeMocks() function to composeHandlers() would provide a more domain-driven name, and won’t confuse the users.

- const { start } = composeMocks(...)
+ const { start } = composeHandlers(...)

Benefits of the change

• Aligned with the internal vocabulary
• Function does exactly what it’s called after

Drawbacks of the change

• Longer to write
• Not straight intuitive if you don’t know the library’s glossary

Alternatives to consider I was also thinking about simply naming it compose(), but I’m afraid this will clash with the similar functional composition utility that is often called compose(). Also, composeMocks() is not the traditional compose function per-say, as it’s logic is specific to MSW.

[andreawyss]

// Browser usage
import { setupServiceWorker } from 'msw'

const { start, stop } = setupServiceWorker(options)
start()

// Node usage
import { setupMockServer } from 'msw'

setupMockServer(options)

[kettanaito]

As MSW will eventually support mocking in non-browser environments, I think that such initializer functions like composeMocks() should clearly describe what are they initializing.

I suggest the following API:

useWorker()

function useWorker(...handlers: RequestHandler[]): WorkerAPI

Uses a Service Worker with the given request handlers.

useServer()

function useServer(...handlers: RequestHandler[]): unknown

Stubs an XHR communication with the given request handlers, thus, mimicking a server.

I’m not found of a word “server” where there are no actual servers, so please feel free to share what name makes more sense to you.