improve: expose projectRoot setting in createTestContext

[luhagel]

Using createTestContext in a monorepo setting leads to the Layout.create function detecting the top level package.json and error out because that one doesn't have it's own name. However, by exposing the projectRoot option already accepted by Layout.create, we can circumvent this by resolving the path ahead of time, i.e.:

Object.assign(ctx, await originalCreateTestContext({ projectRoot: path.join(__dirname, '../..') }))

TODO

• docs
  • jsdoc
  • website api
  • website guides
  • website tutorial
• tests

[netlify]

Deploy request for graphql-nexus pending review.

Review with commit 3698db4

https://app.netlify.com/sites/graphql-nexus/deploys

[jasonkuhrt]

Thanks @luhagel!

One thing. Can you add some jsdoc for this option, mainly about why this setting might be used (like the other).

[luhagel]

Will do

[jasonkuhrt]

Thanks @luhagel!

Clarifying question. The search for package.json starts from cwd by default. If you were inside your package root I don't think there should be any issue, right? However if you're trying to run tests for a package from the monorepo root, then indeed that will not work.

Just want to make sure I'm understanding the problem.

[luhagel]

@jasonkuhrt Exactly, the projectRoot and cwd work as expected if the command is started from the nexus package root.
In our example, we have a monorepo with a few packages of which the api package is one.

Our Jest suite runs from the monorepo root and executes all the suites across all the packages via jest projects.

Since the yarn test command gets kicked off from the monrepo root, cwd resolves to the top level package.json instead of the one in packages/api, which leads to errors to parsing since workspace roots miss some fields and the plugins are defined i the package root so reflection breaks.