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

fix: disable requireCache #6

Merged
merged 2 commits into from
Mar 7, 2022
Merged

fix: disable requireCache #6

merged 2 commits into from
Mar 7, 2022

Conversation

danielroe
Copy link
Member

resolves #5, resolves nuxt/nuxt#13462

Not sure if this is the correct fix or if we want jiti to have an option to force not using the native cache...

@danielroe danielroe added the bug Something isn't working label Mar 5, 2022
@danielroe danielroe requested a review from pi0 March 5, 2022 21:23
@danielroe danielroe self-assigned this Mar 5, 2022
@pi0
Copy link
Member

pi0 commented Mar 7, 2022

There is an option requireCache, which we could additionally disable as well.

@pi0 pi0 changed the title fix: don't cache resolved config file fix: disable requireCache Mar 7, 2022
@pi0 pi0 merged commit 1a6f7d3 into main Mar 7, 2022
@pi0 pi0 deleted the fix/cached-config branch March 7, 2022 11:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

nuxt.config is not reloaded when it changes config isn't properly reloaded from disk
2 participants