Absolute import path aliases

[jasonkuhrt]

What

• https://stackoverflow.com/questions/38601592/typescript-import-path-alias

Why

• It makes it a lot easier to maintain certain kinds of imports (local lib most common use-case) across an app codebase.

How

• 854

• https://github.com/rollup/plugins/tree/master/packages/alias (example, only specifically relevant if we bundle with rollup, though)
• https://github.com/graphql-nexus/nexus/issues/199 (some insight, we looked at doing it on this codebase)

Instances

• https://github.com/graphql-nexus/nexus/discussions/928 / #927
• https://github.com/graphql-nexus/nexus/issues/855

[mtzfactory]

Hi, I'm using nexus in a project that use yarn workspaces and lerna to build the app...

It works perfectly in dev mode... but fails when I try to build it...

The project use the nexus prisma plugin, with a sqlite database...

❯ yarn workspace @xXXxXXx/server build
yarn workspace v1.22.4
yarn run v1.22.4
$ nexus build
1170 ● nexus:build get used plugins
2099 ● nexus:plugin:nexusPluginPrisma Running Prisma generators ...
 727 ● nexus:build starting reflection
5223 ✕ nexus reflection failed
       | error  Error:
       |                Runner failed with exit code "1".
       |
       |            at ChildProcess.<anonymous> (/Users/xxx/xxx/xxx/packages/server/node_modules/nexus/dist/lib/reflection/reflect.js:71:28)
       |            at ChildProcess.emit (events.js:315:20)
       |            at ChildProcess.EventEmitter.emit (domain.js:485:12)
       |            at Process.ChildProcess._handle.onexit (internal/child_process.js:275:12)

I think this issue might be related...

[jasonkuhrt]

Hey @mtzfactory, I doubt it. Can you share your tsconfig? Access to a repo repro is welcome too.

[mtzfactory]

Hi @jasonkuhrt, I've uploaded to gist the config files...

https://gist.github.com/mtzfactory/65f321b03ef09769c7366e6550323675

If it doesn't help, I'll try to reproduce it in a new repo...

[jasonkuhrt]

Thanks @mtzfactory, took a look, not sure what is going on. Not related to this issue though. Please open a new one if issue persists. Note that monorepos are not yet officially supported #530. So YMMV there.