feat!: msw/graphql, graphql as an optional peer dependency#2691
feat!: msw/graphql, graphql as an optional peer dependency#2691kettanaito wants to merge 4 commits intofeat/3.0from
msw/graphql, graphql as an optional peer dependency#2691Conversation
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
@Andarist, hi 👋 Mentioning you just in case so this wouldn't conflict with the work you're doing. TL;DR |
Motivation
mswleaks thegraphqlnamespace through the root entrypoints, which makesgraphqlimport problematic for developers who aren't even using GraphQL. This negatively impacts the bundle footprint as well.This is a change in a set of changes aimed to improve DX and bundle size of
mswacross the board.graphqlnamespace and any related values/types are no longer exported frommsw. Please use a designatedmsw/graphqlexport path to work with GraphQL requests.msw/core/graphqlexport path has been changed tomsw/graphqlfor brevity.Todos
feat/3.0. This is not meant to be released separately.defineNetwork) #2650 to benefit fromsetupWorker/setupServeracceptingAnyHandlerand notRequestHandler, which is incompatible withGraphQLHandler