Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

@plasmic/loader-nextjs ignores custom build directory, is not configurable #45

Open
isolationism opened this issue Jul 12, 2022 · 0 comments
Assignees

Comments

@isolationism
Copy link

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:

const cacheDir = path.resolve(process.cwd(), '.next', '.plasmic');

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants