I discovered JointsWP starter theme which looks promising.
However, I'm having troubles getting started with the sass version which I would like to use.
I did a fresh installation of wordpress, and installed the jointswp theme.
When I do npm install, it installs the dependencies.
But when I do 'gulp', I get a bunch of warnings.
Doing gulp watch and gulp styles seems to work but doing gulp vendor-js gives a "Too many errors. (67% scanned)." reply.
When I install a fresh copy of foundation 6 and use the foundation-cli, I have no problems what so ever.
Does anyone know what might be causing this?
Image of errors
Sorry for the slow response.
Those errors are normal - they're actually warnings. Your code will compile fine.
It looks like JSLint has some "issues" with how some of the Foundation JavaScript is implemented.
Related
We are using Gulp with browserify, and I am having a problem diagnosing an error. Browserify runs, reporting no problems, however, many of the scripts that should have been concatenated into my output js file are missing.
We have found that this can happen if we are missing an npm package (if we need to run npm install), or if there is something wrong with an npm package. The past couple of times it has happened, we have been lucky in that we had only just added 1 package and so we immediately knew where to look.
Now, I have it failing on a dev machine (by fail, I mean that my output .js file is 1/10th the size it should be an missing many js files, but no errors reported). I am not sure which package it is failing on, and I am getting no diagnostics.
I tried hooking .on('error') as described here: https://stackoverflow.com/a/24817446/67038, but there was no additional output.
The output from the Visual Studio Task Runner Explorer looks like this:
[18:17:21] Using gulpfile C:\git\...\Gulpfile.js
[18:17:21] Starting 'browserify:local'...
[18:17:24] Finished 'browserify:local' after 2.63 s
[18:17:24] Starting 'build:local'...
[18:17:24] Finished 'build:local' after 31 ms
Process terminated with code 0.
What can I do to get additional information from Browserify? Is there some sort of logging that I can turn on?
The problem you experienced was caused by the tsify plugin.
Prior to version 1.0.4, there were a number of path-related bugs that could result in empty modules being emitted without any errors being reported to Browserify. These bugs have been fixed and errors are now emitted to Browserify in situations that would have previously resulted in an empty module.
I was using node v0.12, and just wanted to update my npm packages, however, the new version of node uses node-sass and libsass as a compiler.
I am using grunt-sass to compile my files, but ended up with a lot of errors that occur only with Libsass.
Here is an example that seems happen on sassmeister.com when using the Libsass compiler.
The solution is to add a space after the :, fine, but this is not the solution am seeking, any help please?
Here is a gist to experiment the issue and it has a weird fix tho.
http://www.sassmeister.com/gist/b8197cf0593d722f808809e8979f2ab9
I'm trying to run the MEAN stack on windows. I've installed all the pre-requisites (I think) but when I try to start the server via the gulp command I get the error:
Error: Cannot find module 'assetmanager'.
IMAGE:
I have tried running npm install assetmanager which run fine but I still get this error.
This is my first time trying to run node on a machine (I should have used a linux box) so go easy on me as I am learning :-).
Any and all help appreciated.
David
I had exactly the same problem on Linux Mint 17.2.
The failing way: This was my first project that I'd generated and I don't think I had all the dependencies installed before I ran the init command (g++ was missing).
I tried the npm install assetmanager command as you did and then install worked. Running gulp after this, it got further but this time I was missing mongoose. I installed that then it couldn't find .../config/env/all so I sylinked the default.js config. Then running gulp again, errorhandler was missing. I figured it shouldn't be this hard so...
The working way: I deleted that failure of a project and init'd a new one and it worked. Unfortunately I'm not sure if the init didn't work the first time but I missed the error/warning or something else caused it. All I can recommend is try creating another project and see if that works.
When I install mongodb I'm getting a long warning list like this:
Why is this happening? I'm not sure if I can ignore this. Because those warnings look pretty serious. I'm concerned about the fact that it is telling me something about Visual Studio 2013...
I've also uninstalled "Nodejs tools for Visual Studio", and reinstalled Nodejs, but I still get these warnings.
You can ignore that npm warning, it's basically just telling you that the repository field isn't filled out in your denoapp module's package.json. If you don't have a repository for the module, you could probably just set it to an empty string or something similar.
As long as the module installs/builds ok, you can usually ignore the compiler warnings (especially if they are V8-related since there's not much you can do about those).
Having issues getting swiper.js to work. Requires grunt/bower. I'm completely new to js generators and am only able to get through about half the walkthrough before running into issues.
When I type $grunt dist into terminal, I get the following response: -bash: dist: command not found
What step am I missing?
Followed the idangerous steps to the letter: http://www.idangero.us/sliders/swiper/plugins/scrollbar.php
I have most often see "X command not found" for one of the following reasons:
The project's Grunt dependencies aren't installed or aren't installed properly
Your Gruntfile is mis-configured or missing
To fix this, first make sure there is a package.json file in your project. This will tell the npm what dependencies the project has and install them accordingly (assuming the package.json file is also configured correctly).
Next, make sure you have installed grunt correctly.
If you're still having issues, open your Gruntfile and search for:
grunt.registerTask('dist
This will show where the "dist" task is being defined. If you for some reason don't find it, then there's your problem. If you do find it, then check the proceeding commands inside square brackets that look like this:
grunt.registerTask('dist', ['clean', 'dist-css', 'copy:fonts', 'dist-js', 'dist-docs']);
'clean', 'dist-css', etc. are all other tasks defined in the Gruntfile, and there could be an issue with those as well.
If there's an issue with your package.json or Gruntfile, then trying re-installing the project with bower and repeat the above steps to ensure that it's not an issue on your end.
If it's not, then something is probably wrong with the author's source code.