Option to specify path for Photon & Nexus output files

As of right now, when looking for a place to put the generated code, Photon & Nexus apparently either find or create a node_modules folder, and then place the code in the @generated sub-directory of it. This works fine on a simple test project, but I’m running into an issue where I have a mono-repo setup with multiple projects in it:

1. If I structure the project such that the generated code is placed in the node_modules folder at the root of the project, then I’ll suddenly have potential conflicts between different Photon/Nexus projects all overwriting the same locations.
2. If I structure the project such that Photon/Nexus essentially create a new node_modules folder for each project, I’m now apparently unable to actually import the client, as the import Photon from "@generated/photon" found in the tutorial only seems to work for the root node_modules folder, and I get various “cannot find module” errors if I try to import the various clients directly, like via foo/node_modules/@generated/photon.

What’s the best way to go about handling multiple Photon/Nexus projects in a single repo?

[timsuchanek]

@artemzakharov ./ is needed, as this is a Node.js convention. Paths without a ./ or / are resolved as a node module.

As of now we don’t have the option to provide the path to the schema file, but feel free to create an issue!

[pantharshit00]

If the output is outside of your node_modules folder, you will need to specify a relative path unless you have defined a babel or webpack plugin or configured your tsconfig to resolve that.

Try this:

import Photon from './prisma/generated/photon';