Mutually dependent local dependencies

[wokalski]

We have a module foo which depends on bar.
In project X you have dependency on ../foo and ../bar which are locally in the root folder. In that case bsb cannot resolve bar from ../foo.

[bobzhang]

Do u have a 'tree' layout?

[wokalski]

bsconfig.json // "dependencies": ["../foo", "../bar"]
foo
|--  bsconfig.json // "dependencies": ["bar"]
bar
|-- bsconfig.json

[bobzhang]

what is your intended workflow? will foo, bar be published as a package? Will your project x be published as a package? If not, any downside using a mono-repo?

[wokalski]

I am using a monorepo. However, foo and bar are submodules containing forks of some packages. Now as a workaround I have them listed as sources but it doesn't work correctly with relative paths to assets in them because the output is not in lib corresponding to their folders but relative to the project root.

[knowbody]

This is exactly the same issue I'm having. I think it is a very common workflow where in the root you have your library and the example directory. Then in the example directory, you want to use the modules from the library.

[bobzhang]

@wokalski it seems that you are doing the symlinks by hand which otherwise should be done by yarn workspaces

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.