You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My particular case is the use of nx (a monorepo) which builds the deployable in an entirely different directory from the project root/cwd, i.e ./dist/apps/my-project/.next.
Next.js has a setting to configure the build/output directory:
https://nextjs.org/docs/api-reference/next.config.js/setting-a-custom-build-directory
... which makes this line in the loader a problem:
plasmic/packages/loader-nextjs/src/cache.ts
Line 40 in 5198eac
My particular case is the use of nx (a monorepo) which builds the deployable in an entirely different directory from the project root/cwd, i.e
./dist/apps/my-project/.next
.According to the "Legacy API" docs, once upon a time PlasmicLoader supported configuring these directories, but seem to have disappeared post-refactoring for greater abstraction and re-use.
Any plans to restore support for configuring plasmic's cache directory manually, or matching the build directory used by Next?
The text was updated successfully, but these errors were encountered: