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

chore(core): warn when db cache is disabled #28929

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

AgentEnder
Copy link
Member

Current Behavior

Expected Behavior

Related Issue(s)

Fixes #

Copy link

vercel bot commented Nov 13, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Skipped Deployment
Name Status Preview Updated (UTC)
nx-dev ⬜️ Ignored (Inspect) Visit Preview Nov 22, 2024 10:17pm

) {
// TODO (@AgentEnder): Insert correct link after @isaacplmann has written the documentation.
logger.warn(
`Nx is using the filesystem cache instead of the db cache. There are some limitations and trade-offs to consider when using the filesystem cache. Read more at https://nx.dev/{insert-link-here}.`
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we can call it the legacy cache and mention that it will be removed in Nx 21. Instruct them to start looking into moving to the new db based cache.

process.env.NX_REJECT_UNKNOWN_LOCAL_CACHE === 'false'
) {
logger.warn(
'NX_REJECT_UNKNOWN_LOCAL_CACHE=0 is not supported with the new db cache. If you were using this environment variable to suppress warnings about unrecognized cache artifacts you may be interested in Nx PowerPack. Read more at https://nx.dev/powerpack.'
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this shouldn't point to powerpack directly. It should point to a page about the problem.. which should point them to Nx Cloud or Powerpack to achieve what they want.

@AgentEnder AgentEnder force-pushed the chore/warn-on-legacy-cache branch 3 times, most recently from b7ebaea to 7a950c2 Compare November 18, 2024 23:08
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

Successfully merging this pull request may close these issues.

2 participants