Elliot Chong

For reference: https://github.com/mochajs/mocha/issues/2356

@oleg-rdk thanks for the PR! I'm recently hitting this issue as well, would you like any help getting that PR over the finish line?

I've started work on a fix for #73, #62, and #39 @ https://github.com/ElliotChong/coffee-react-transform/commits/patch-1 It passes all existing tests and it _should_ fix #62 and #39; however, I'm having some trouble...

If the type definitions are identical could we work around that slice of issues by simply discarding the duplication in a pre-processing step before the schema merge? If types are...

Thinking about this more... Is the current intention to just mark the duplicated types in Service B as [stub types](https://www.apollographql.com/docs/apollo-server/federation/federation-spec/#create-stub-types)? We'll still have an issue with `input`s though since they...

The output for node-theseus in verbose mode is: ``` [node-theseus] adding require() instrumentation hook [node-theseus] listening for WebSocket connections on port 8888 [node-theseus] excluding node_module ~/.nvm/v0.10.12/lib/node_modules/mocha/bin/mocha [node-theseus] debugger connected [node-theseus]...

Running `node-theseus` with the `--theseus-include-modules` seems to fix Brackets throwing up that error; however, a new issue has emerged since my mocha tests don't seem to be instrumented / reporting...

Thanks so much for the detailed reply and workarounds!

Sorry, will leave this open until the fixes are in place.

Source maps may keep the implementation more flexible, such as built-in support for TypeScript or any other new transpiler that comes along.