-
Notifications
You must be signed in to change notification settings - Fork 41
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
Disable cache on non-v8 versions of Node #5
Conversation
Yes, please 😋 As more tools adopt |
Looking |
Rock! On the current stable release I see chakracore erroring out in the I believe this PR will resolve the issue since it just bypasses the entire thing. Update: Too fast 🚤 🎉 |
Just published v8-compile-cache@1.1.1... sorry about the delay - totally missed this PR |
NP! I'll ping back after investigating to see if other engines produce the buffer. As with chakracore I think the buffer was being produced it's just they don't have a v8 version, since it's not v8, so the directory was the bug point. If it turns out they do work I'll prep a PR for a more generic cache folder naming scheme or one that crawls all versions data. |
Oh wait, |
Fixes #5 such that it doesn't preclude future support in different engines
chakracore doesn't support cached data, but a027ea3 leaves the possibility open to use it if it ever works |
Nice! If you want to test in chakra core here is my appveyor.yml for reference. |
Recently I was playing around with ChakraCore's implementation of Node (https://github.com/nodejs/node-chakracore) and noticed that v8-compile-cache fails since
process.version.v8
is not set. I did some experimentation and it seems that running the cache in Chakra causes segmentation faults on version 8.3 and nightlies, so I just made sure that the cache only initializes for v8. I'm not even sure if, philosophically, a package calledv8-compiler-cache
should enable a cache for other implementations of Node, but I will do my best to watch Chakra's development and get another PR to enable the cache if support comes.