Turborepo is not creating the node_modules inside the apps/*

[AyushNautiyalDeveloper]

Summary

My project look like this:

root (node_modules)
└── apps

• └── generator(node_modules)

I am trying to run the npm i in my root I am expecting that the node_modules gets installed in my generator app. but it is only installing node_modules in my root.

Additional information

No response

Example

No response

[anthonyshew]

This is the correct behavior. npm hoists dependencies to the root and resolves those dependencies using its resolution algorithm.

[AyushNautiyalDeveloper]

@anthonyshew I mean I have used turborepo for other projects also generally I have seen it installs node_modules for every app it have. Is it configured some how. If yes can you clearify.

[mehulkar]

@ayushnau I'm happy can re-open this if you can provide a reproduction. I agree with Anthony that this doesn't look like it has anything to do with Turbo. You may be able to find more help in the turbo discord as a support channel.

[mehulkar]

also no due to some issue in dependencies the project is not able to run tests. which is the main issue i am having .

Please provide some kind of evidence that this is related to turbo or a reproduction.

[AyushNautiyalDeveloper]

will do that @mehulkar

[AyushNautiyalDeveloper]

@mehulkar I have uploaded my project here please check this. https://github.com/ayushnau/generator

run npm i and see for yourself the node_modules not getting installed in generator repo.
due to which test are getting failed.

[mehulkar]

@ayushnau thanks for the reproduction. I cloned it down and am at the same conclusion: that your issue is not related to Turborepo. Some notes again:

• npm can install your dependencies wherever it likes. turbo cannot control this, and in my experience it's not necessarily a bug that there after npm i apps/generator/node_modules does not exist. I am 99% sure this is intentional.

• I attempted to replace your reproduction with pnpm@8.15.0 instead, which does create apps/generator/node_modules and your tests still fail the same way. I also tried with Node 18 and Node 20, since the error seemed related to some core built ins

  Stack trace

  PASS  test/renderer.test.js
  FAIL  test/utils.test.js
    ● Test suite failed to run
  
      ENOENT: no such file or directory, open 'node:path'
  
      > 1 | const npmConfig = jest.genMockFromModule('@npmcli/config');
          |                                                           ^
        2 |
        3 | module.exports = npmConfig;
        4 |
  
        at Runtime.readFile (../../node_modules/jest-runtime/build/index.js:1842:21)
        at Object.<anonymous> (../../node_modules/.pnpm/@npmcli+config@8.3.1/node_modules/@npmcli/config/lib/index.js:7:36)
        at Object.<anonymous> (test/__mocks__/@npmcli/config.js:1:59)
        at Object.<anonymous> (lib/generator.js:10:16)
        at Object.<anonymous> (test/utils.test.js:3:19)
  
  FAIL  test/generator.test.js
    ● Test suite failed to run
  
      ENOENT: no such file or directory, open 'node:path'
  
      > 1 | const npmConfig = jest.genMockFromModule('@npmcli/config');
          |                                                           ^
        2 |
        3 | module.exports = npmConfig;
        4 |
  
        at Runtime.readFile (../../node_modules/jest-runtime/build/index.js:1842:21)
        at Object.<anonymous> (../../node_modules/.pnpm/@npmcli+config@8.3.1/node_modules/@npmcli/config/lib/index.js:7:36)
        at Object.<anonymous> (test/__mocks__/@npmcli/config.js:1:59)
        at Object.<anonymous> (lib/generator.js:10:16)
        at Object.<anonymous> (test/generator.test.js:4:19)
  

Even if this is some kind of bug with something outside your code, I am reasonably confident at this point that Turborepo's existence in your repo is not causing this. You can try removing Turborepo entirely from your repo, or run your tests directly with jest to confirm this for yourself.