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

feat: configurable working directory #563

Closed
samyosm opened this issue Oct 7, 2023 · 2 comments
Closed

feat: configurable working directory #563

samyosm opened this issue Oct 7, 2023 · 2 comments

Comments

@samyosm
Copy link

samyosm commented Oct 7, 2023

We aren't able to configure the .contentlayer output location.

Uses

  • Cleanly support multiple sites/apps
  • Ability to be used with monorepos

Context

Appropriate lines of code:
https://github.com/samyosm/contentlayer/blob/2f491c540e1d3667577f57fa368b150bff427aaf/packages/%40contentlayer/core/src/_ArtifactsDir.ts#L12-L13

Related

#464

Copy link

stale bot commented Dec 7, 2023

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.

@stale stale bot added the meta: stale label Dec 7, 2023
@stale stale bot closed this as completed Dec 17, 2023
@harrysolovay
Copy link

harrysolovay commented Mar 19, 2024

Current examples show generated assets imported via contentlayer/generated, which is aliased via paths in the tsconfig.json. Many folks will already alias their root directory (for instance, shadcn ui projects are generated with the alias @/[subdir]). One could forgo the second alias and instead import from @/.contentlayer/generated, however it's a bit clunky. Ideally one could configure the output directory to enable a more minimal import specifier (@/content perhaps). Any chance we could reopen this issue?

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

No branches or pull requests

2 participants