Nestia can not properly find @nestia/sdk in Yarn Monorepos

[Aderinom]

Bug Report

Summary

Nestia can not find it's packages when beeing used in a yarn monorepo

• SDK Version: 1.0.7 (skipped installing the @next version since I took a look at the current source code)
• Expected behavior:
  npx nestia swagger "src/**/*.controller.ts" --out ./
  should output a swagger.json
• Actual behavior:
  @nestia/sdk has not been installed. Run "npx nestia setup" before.

Nestia tries to find its packages by using a fully qualified path:

await import(process.cwd() + "/node_modules/@nestia/sdk"); index.ts:53

This does not work as expected in yarn monorepos and will probably also cause issues with
repos using pnpm.

Yarn saves all packages from child workspaces in the root node_modules. (hoisting)
As such the fully qualified path supplied will not be able to find the packages.

Example format of yarn monorepo

/app
  /server
     app.ts
     package.json (has @nestia/sdk as a dependency)
     ...
/lib
  ...
/node_modules
   /@nestia/sdk
   /...
/package.json (could in theory also have the @nestia/sdk as a dependency, making it "global" at least in my understanding)

[samchon]

OK, I'll patch it after home.

[samchon]

package.json also exists in ./ path?

[Aderinom]

Updated the example layout.

But yes, there is always a package.json in the root path. At least with yarn and pnpm.
I'll quickly make an example repo.

[samchon]

Okay, I will wait for

[Aderinom]

There you go. Installed nestia manually with ttsc.
Server works as expected. CLI fails to find nestia.

https://github.com/Aderinom/yarn-monorepo-example

When I tried to use the nestia setup yesterday, that also ran into some issues, don't remember what though.

[samchon]

I'll try it, thx.

[samchon]

Oh my god, I found that node_modules directories are generated in both ./ and ./apps/nest.

I have to check both of them.

[Aderinom]

I'm not sure. But I think that require would actually try all node_modules in all parent folders.
Sadly I have to be somewhere right now else I'd try to find some info on how other cli tools solve this / how resolve works for modules. .

[Aderinom]

However, resolution for a non-relative module name is performed differently. Node will look for your modules in special folders named node_modules. A node_modules folder can be on the same level as the current file, or higher up in the directory chain. Node will walk up the directory chain, looking through each node_modules until it finds the module you tried to load.

https://www.typescriptlang.org/docs/handbook/module-resolution.html

https://nodejs.org/api/modules.html#loading-from-node_modules-folders

[samchon]

Update to the latest, then be fixed.