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

persistent-cache + exportModuleMetadata are not compatible #53

Closed
2 tasks
stefanpenner opened this issue Aug 24, 2015 · 5 comments
Closed
2 tasks

persistent-cache + exportModuleMetadata are not compatible #53

stefanpenner opened this issue Aug 24, 2015 · 5 comments

Comments

@stefanpenner
Copy link
Member

  • make it work
  • re-enable persist when exportModuleMetadata is enabled

cc @chadhietala (also note, exportModuleMetadata relies on private API _cache ...)

@chadhietala
Copy link
Member

Why does this not work?

@rwjblue
Copy link
Member

rwjblue commented Jun 8, 2016

@chadhietala - It doesn't work because it relies on this.moduleMetadata which is only populated in processString, and when a given file is found in the cache it wouldn't have processString called on it (so its metadata would not have been added to the local cache).

The good news is that this is now pretty easy, using postProcess that was added to allow us to export more than just the resulting file.

See:

@krisselden
Copy link

would it not be better to save the metadata the async cache?

@rwjblue
Copy link
Member

rwjblue commented Aug 25, 2016

@krisselden - Yes, that is what my suggestion is. 😺

@stefanpenner
Copy link
Member Author

I think this is no longer a thing

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