You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jan 23, 2021. It is now read-only.
Extract the OS temp dir to its own option, separate from container
The use cases for changing the OS temp dir are different from the use cases for
specifying a task-specific container. Let's decouple them for better user
interface.
Need to change temp dir use cases:
- No access to the OS temp dir due to permissions
(reported in windows and on-server issues)
- OS temp dir is reported incorrectly
(Windows, https://github.com/sindresorhus/gulp-ruby-sass/issues/2301)
Need to specify container use cases:
- multiple grs tasks running at once
Default: the OS temp directory as reported by [os-tempDir](https://github.com/sindresorhus/os-tmpdir)
112
+
113
+
This plugin compiles Sass files to a temporary directory before pushing them through the stream. Use `tempDir` to choose an alternate directory if you aren't able to use the default OS temporary directory.
114
+
108
115
#### container
109
116
110
117
Type: `String`
111
118
Default: `gulp-ruby-sass`
112
119
113
-
Name of the temporary directory used to process files. If you're running multiple instances of gulp-ruby-sass at once, specify a separate container for each task to avoid files mixing together.
120
+
If you only have a single gulp-ruby-sass task you can ignore this option. If you're running multiple gulp-ruby-sass tasks at once you must specify a separate `container` for each task to avoid file collisions. The value is appended to the `tempDir` option.
0 commit comments