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.

Sign up for GitHub

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

Jump to bottom

Cache analysis #2

Open
Rich-Harris opened this issue Feb 9, 2015 · 1 comment
Open

Cache analysis #2

Rich-Harris opened this issue Feb 9, 2015 · 1 comment
Labels
enhancement

Comments

@Rich-Harris
Copy link
Owner

When running sorcery on (for example) a browserify bundle, the likelihood is that various external modules will be included. Since these aren't going to change often (if at all), it would make sense to cache analysis in memory and re-use it in the case of incremental rebuilds, potentially avoiding having to re-analyse large subtrees of the bundle.

As a starting point, storing the analysis in memory (must likely against a crc32 checksum of the file contents) would go a long way. Ideally the analysis would be saved to disk (e.g. in a .sorcery.json file) so that it would work with the CLI as well as with gobble-sorcery.
@Rich-Harris Rich-Harris mentioned this issue Feb 20, 2015
Closed
@KnisterPeter
Copy link

I would like to discuss solutions to this.
I have a strong need to cache the results for incremental builds here paeckchen/paeckchen#174

Would you mind a PR for this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@KnisterPeter @Rich-Harris