-
Notifications
You must be signed in to change notification settings - Fork 270
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
Browsersync errors #309
Comments
+1 - I got the same issue recently. I ended up grabbing the mode modules folder from another install and using that as a bandaid but definitely not a fix. |
Did you run the |
Can you try running |
Thanks for the responses, gang. Here's an outline of the steps I took and the results. Sorry if any of this is obvious - npm, gulp, etc. are still relatively new to my workflow. 1) Ran "rm -rf node_modules && npm install", got "permission denied" errs. iMac-2% sudo rm -rf node_modules && npm install npm ERR! A complete log of this run can be found in: 3) Attempted to run browsersync - no dice. iMac-2% npm run browsersync
[15:35:20] Local gulp not found in ~/Dropbox (éclat.digital)/Local Sites/The Bone Reader/app/public/wp-content/themes/the-bone-reader-5 npm ERR! A complete log of this run can be found in: 4) Then tried to reinstall all of my usual tools and got this: iMac-2% npm install --save-dev gulp-sass gulp-cssnano gulp-sourcemaps gulp-autoprefixer npm ERR! A complete log of this run can be found in: |
OK, so I ran all of the npm installs individually and browsersync is back up and running. I'm guessing that the "rm -rf node_modules" that Jeremy suggested flushed everything and reinstalling all of the npm stuff brought it back. However, I've now got what seems to be a different problem. [Browsersync] Watching files...
[Browsersync] 2 files changed (login.css.map, login.css) I'd be much obliged if anyone has thoughts on this but I'll hold off posting anything more until Jeremy or other mods decide if this a related issue or if it's a separate matter. |
Hi @dgadwa |
Thanks, Garrett. I've verified that my _global.scss file is in the correct folder. The contents of the file seem to be OK and in line with every other project that I've built with Joints. Knowing that we don't typically make changes to minified files such as assets/styles/scss/style.scss I couldn't help but take a look for the @import "global"; that was also mentioned in the error message. Strangely, I can't find any @global statements at all in there. Any thoughts? |
Very odd, can you package up your assets folder as a zip to post here along with your gulpfile.js and I'll see if anything is amiss. |
Yes, this was a clean install. It was running for a short time before the original browsersync errors so I was able to add a little content and styling, but didn't get very far along with it. Here's a link to the assets and gulpfile: https://drive.google.com/open?id=1WiQq50B4cEsqRZFlIOQJM4L9a2ArHI2P Cheers! |
Hey @dgadwa that link is locked down, can you make it public so I can download the assets. Thanks |
Sorry Garrett. Should be good to go now. https://drive.google.com/file/d/1WiQq50B4cEsqRZFlIOQJM4L9a2ArHI2P/view?usp=sharing |
Thanks @dgadwa got it here. |
YError: Invalid first argument. Expected boolean or string but received function. I am getting this error what to do |
Hey all. I'm encountering an error with Browsersync (via NPM/Gulp) and wondering if someone can shed some light on it. Lines 4 and 7 call attention to "jointswp-sass@5.0.0 browsersync script".
[10:40:23] 'browsersync' errored after 42 s
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! jointswp-sass@5.0.0 browsersync:
gulp browsersync
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the jointswp-sass@5.0.0 browsersync script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
I've tried running “npm i -g gulp-cli” and made sure that dependencies are sorted out and up to date, sadly, to no avail.
dMac-2% node -v
v8.6.0
dMac-2% npm -v
5.6.0
I've successfully built several other projects using Joints but I am at a loss here. Thanks and all the best!
The text was updated successfully, but these errors were encountered: