Welcome to the Treehouse Community
The Treehouse Community is a meeting place for developers, designers, and programmers of all backgrounds and skill levels to get support. Collaborate here on code errors or bugs that you need feedback on, or asking for an extra set of eyes on your latest project. Join thousands of Treehouse students and alumni in the community today. (Note: Only Treehouse students can comment or ask questions, but non-students are welcome to browse our conversations.)
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and a supportive community. Start your free trial today.
@4:15, he mentions its better for gulp to src a single sass file instead of multiple ones, like src("path/to/sassDir")
Is this also the case for say other assets, fonts, images, js, etc. since we cant import them from a main asset file - ex. app.scss?
From the series Turn Sass into CSS, automatically - with Huston Hedinger.
Sean T. Unwin28,672 Points
This is not typically the case for other assets as there will be multiple images, js files, and possibly fonts. You should load those for as many as required. This is commonly seen with the globbing pattern --
'**/*.js' -- so that we can grab all the files of the same type from a specific directory or series of directories.
The base Sass file should include all the other Sass partials, therefore when compiling from Sass to CSS the transpiler is processing only one file, as far as it is concerned, since everything is essentially concatenated into the base Sass file.