I was looking through a lot of commits, PRs etc and see that there has been some work-ish done on monorepo support.
Now I have a project that is similar to the https://github.com/vercel/next-forge monorepo with apps/* and packages/*
Now I run into a issue where packages are inheriting from each other example
packages/ai uses a package from packages/next-config/env-types
It looks like the bundler only works on app level and not looking into sublevel tsconfig settings?
Because its totally wrong when it tries to resolve the paths.
Discovering workflow directives 1110ms
Created steps bundle 69ms
✘ [ERROR] Could not resolve "../../../../packages/n
ext-config/env-types"
../../packages/ai/keys.ts:2:25:
2 │ ...from "../../../../packages/next-con...
╵ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Error: Build failed with 1 error:
../../packages/ai/keys.ts:2:25: ERROR: Could not res
olve "../../../../packages/next-config/env-types"
at new Promise (<anonymous>) {
errors: [Array],
warnings: []
}
Originally posted by @rodeyseijkens in #388
I was looking through a lot of commits, PRs etc and see that there has been some work-ish done on monorepo support.
Now I have a project that is similar to the https://github.com/vercel/next-forge monorepo with apps/* and packages/*
Now I run into a issue where packages are inheriting from each other example
packages/ai uses a package from packages/next-config/env-types
It looks like the bundler only works on app level and not looking into sublevel tsconfig settings?
Because its totally wrong when it tries to resolve the paths.
Originally posted by @rodeyseijkens in #388