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
Bring in new fs sandboxing system #357
Comments
Is the webpack memory-fs module at all useful for this? |
Looks good - there is no stream support though. I can send a PR when I have a minute |
If anyone is interested you can monitor progress here https://github.com/wearefractal/vinyl-fs-tree |
@contra any changes happening for this? I saw vinyl-fs-tree hasn't been touched much. |
@ilanbiala It got put on the backburner, might get moved to 4.1 since its just a tool to make plugins easier to write |
Ok, sounds good. |
I've been trying to figure out how watching in gulp works, and my understanding so far is that every time a file that matches the glob changes, you Wouldn't it be better if |
@spelufo streams/tasks that never end is an anti-pattern |
To describe the problem, look at browserify. It likes to read all of it's own dependencies in. We prefer to do the IO so we can pass virtual files to these modules. Currently this isn't possible without writing to a tmp folder and then giving the tmp folder to browserify so it can load the modifications that a plugin up the pipeline made. Instead we can trick browserify into thinking the set of virtual files (purely in memory) are the real fs by wrapping it in a contextify sandbox where fs = a set of virtual files. This will be a module that plugin authors use under the hood to help deal with these modules.
The text was updated successfully, but these errors were encountered: