'How to test a monorepo locally?

I got a big project that is a monorepo consisting of multiple scripts and libraries, its structure is the following:

package.json // "private":true
 \packages
    \comp1
       \package.json // an actual component
    \comp2
       \package.json // an actual component
    \comp3
       \package.json // an actual component

I've made a monorepo.tgz using yarn pack.

Then I made a test app whose package.json look like this:

 "scripts": {
    // this is a script in one of the monorepo's components
    "start": "ui-build --bundle --watch -p 3000"
  }
  "dependencies": {
    "comp1": "../monorepo/monorepo.tgz",
    "comp2": "../monorepo/monorepo.tgz",
    "comp3": "../monorepo/monorepo.tgz",
  ...

but its not working, when I run start its complaining that ui-build: command not found. How can I test this monorepo locally to simulate a published npm package as closely as possible?

Solution 1:^[1]

To import a file directly without using npm link or yarn link you have to prepend the path with file:. And I believe you would have to pack each file, but you can link directly to the path without packing it as well. Make sure to build it if you are linking directly to the local package folder.

For your example:

"comp1": "file:../monorepo/comp1.tgz",
"comp2": "file:../monorepo/comp2.tgz",
"comp3": "file:../monorepo/comp3.tgz",

"comp1": "file:../path/to/monorepo/packages/comp1",
"comp2": "file:../path/to/monorepo/packages/comp2",
"comp3": "file:../path/to/monorepo/packages/comp3",

Solution 2:^[2]

After some research I've found that https://verdaccio.org/ is the best tool to test a library without deploying to an npm repository

Sources

This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.

Source: Stack Overflow

Solution	Source
Solution 1	morganmspencer
Solution 2	sydd

'How to test a monorepo locally?

Solution 1:[1]

Solution 2:[2]

Sources

Related Questions

Solution 1:^[1]

Solution 2:^[2]