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

.cache/ is created in node_modules/mdx-deck/ on build #724

Open
millette opened this issue May 31, 2020 · 3 comments
Open

.cache/ is created in node_modules/mdx-deck/ on build #724

millette opened this issue May 31, 2020 · 3 comments

Comments

@millette
Copy link
Contributor

Maybe it's not a bug per say, but I just noticed a .cache/ directory was created in node_modules/mdx-deck/ when I mdx-deck build deck.mdx, which I found sort of weird.

Should this be fixed or is it normal behavior? I would have expected .cache/ directory be created in my project root, not down into a node_modules/ directory.

@jorabra
Copy link

jorabra commented Jun 8, 2020

I am seeing this issue as well. The mdx-deck deck.mdx process console logs the following two lines twice every second when running:

info added directory at <path_to_project>/node_modules/mdx-deck/.cache/redux

Not only annoying, but also useless noise.

I also agree with you, @millette, the .cache directory should reside in the project root.

@domvo
Copy link

domvo commented Sep 1, 2020

Is there an update? I still have the problem @jorabra described when running mdx-deck deck.mdx. Every second I get these messages, over and over again:

info added directory at /<path_to_project>/node_modules/mdx-deck/.cache/redux
info added directory at /<path_to_project>/node_modules/mdx-deck/.cache/redux
success building schema - 0.105s
success createPages - 0.002s
success Checking for changed pages - 0.001s
success update schema - 0.012s
success onPreExtractQueries - 0.002s
success extract queries from components - 0.016s
success write out requires - 0.001s

@HoverBaum
Copy link
Contributor

Running into this as well. Seems to be related to: #654

Am experiencing the same thing @jorabra described.

For now I am working around this by downgrading to version 4.0.0.

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

4 participants