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 has been archived by the owner on Sep 16, 2019. It is now read-only.
Running into an issue with path configuration or file generation during npm install.
I have already reviewed #691, #676, and other issues mentioning _settings.scss, but no luck.
Environment Details
Fresh install.
Linux (Ubuntu derivative).
node -v = v4.4.0 (via nvm)
npm -v = 2.14.20
bower -v = 1.4.1
How to Reproduce
Following instructions, cloning the repo and running npm install results in tasks passing, with some deprecation warnings, and with this error along the way:
Error msg:
what-input#1.1.4 bower_components/what-input
[20:49:49] Using gulpfile ~/code/foundationpress/gulpfile.js
[20:49:49] Starting 'clean'...
[20:49:49] Starting 'clean:javascript'...
[20:49:49] Starting 'clean:css'...
[20:49:49] Finished 'clean:javascript' after 8.52 ms
[20:49:49] Finished 'clean:css' after 5.23 ms
[20:49:49] Finished 'clean' after 12 ms
[20:49:49] Starting 'build'...
[20:49:49] Starting 'copy'...
[20:49:49] Finished 'copy' after 38 ms
[20:49:49] Starting 'sass'...
[20:49:50] Starting 'javascript'...
[20:49:50] Starting 'lint'...
[20:49:50] gulp-notify: [Sass Error] assets/scss/global/_settings.scss
Error: File to import not found or unreadable: ../../components/foundation-sites/scss/util/util
Parent style sheet: /home/USERNAME/code/foundationpress/assets/scss/global/_settings.scss
on line 43 of assets/scss/global/_settings.scss
>> @import '../../components/foundation-sites/scss/util/util';
^
The same error shows up when running npm run watch or npm run build.
[20:50:41] Starting 'clean'...
[20:50:41] Starting 'clean:javascript'...
[20:50:41] Starting 'clean:css'...
[20:50:41] Finished 'clean:css' after 9.4 ms
[20:50:41] Finished 'clean:javascript' after 17 ms
[20:50:41] Finished 'clean' after 19 ms
[20:50:41] Starting 'build'...
[20:50:41] Starting 'copy'...
[20:50:41] Finished 'copy' after 36 ms
[20:50:41] Starting 'sass'...
[20:50:41] Starting 'javascript'...
[20:50:42] Starting 'lint'...
[20:50:42] gulp-notify: [Sass Error] assets/scss/global/_settings.scss
Error: File to import not found or unreadable: ../../components/foundation-sites/scss/util/util
Parent style sheet: /home/USERNAME/code/foundationpress/assets/scss/global/_settings.scss
on line 43 of assets/scss/global/_settings.scss
>> @import '../../components/foundation-sites/scss/util/util';
^
The text was updated successfully, but these errors were encountered:
@hackingoff I have almost similar local environment and ran into same error a week ago or so. Bower components were getting installed into /bower_components/ , not /components/.
Using fresh install today, build runs beautifully with no errors:
npm run build
> [email protected] build /var/www/html/wp-content/themes/FoundationPress220316
> gulp build
[09:12:07] Using gulpfile /var/www/html/wp-content/themes/FoundationPress220316/gulpfile.js
[09:12:07] Starting 'clean'...
[09:12:07] Starting 'clean:javascript'...
[09:12:07] Starting 'clean:css'...
[09:12:07] Finished 'clean:javascript' after 51 ms
[09:12:07] Finished 'clean:css' after 32 ms
[09:12:07] Finished 'clean' after 62 ms
[09:12:07] Starting 'build'...
[09:12:07] Starting 'copy'...
[09:12:07] Finished 'copy' after 380 ms
[09:12:07] Starting 'sass'...
[09:12:11] Starting 'javascript'...
[09:12:15] Starting 'lint'...
[09:12:29] Finished 'lint' after 14 s
[09:12:29] Finished 'sass' after 22 s
[09:12:34] Finished 'javascript' after 23 s
[09:12:34] Finished 'build' after 27 s
Running into an issue with path configuration or file generation during
npm install
.I have already reviewed #691, #676, and other issues mentioning _settings.scss, but no luck.
Environment Details
How to Reproduce
Following instructions, cloning the repo and running
npm install
results in tasks passing, with some deprecation warnings, and with this error along the way:Error msg:
The same error shows up when running
npm run watch
ornpm run build
.The text was updated successfully, but these errors were encountered: