gruntjs

问题 Is it possible to use two generators on one project with yeoman? For example: I want to use the angular-generator but also want to use another generator, whether it be custom or one of the bootstrap generators. I know you can add dependencies through bower, but that doesn't add anything to my workflow(e.g. compiling less), does it? 回答1: Yes, it is not only possible, but common. Example: When you use JS-MV* generator in the project ( generator-angular for instance) you will probably use

问题 When I create an AngularJS project with yo angular it creates a node_modules/ directory but puts that directory in .gitignore. When I clone the project elsewhere and run grunt server I get Fatal error: Unable to find local grunt. If you're seeing this message, either a Gruntfile wasn't found or grunt hasn't been installed locally to your project. For more information about installing and configuring grunt, please see the Getting Started guide: The getting started guide doesn't say anything

问题 When you create an ember app with Yeoman, it create a handlebars templates folder for you (.hbs). The yeoman config is set that way : watch: { ember_templates: { files: '<%= yeoman.app %>/templates/**/*.hbs', tasks: ['ember_templates', 'livereload'] }, When a template is in the folder root, it works When a template is in a subfolder template/mySubfolder the template is not rendered (no html is returned) When a template is missing, ember throw an error So when the template is in a subfolder,

问题 Is there a way to get dynamic path into the Yeoman build tag, e.g. for <!-- build:js scripts/modernizr.js --> The use-case would be to push in a different path in the layout for differently nested pages, either / to webroot or ../../ to an upper level, e.g. something like <!-- build:js <%= config.path.script %>/modernizr.js --> Related topic has already been discussed in a question of Yeoman/Grunt usemin subfolders, but what about a more graceful/flexible solution? Ideas? 回答1: If you compile

问题 I'm attempting to create a Jade task that will have a build and dev task that have very similar options, except a dev boolean, and a different destination. The simplest way I've been able to achieve this is: jade: { dev: { options: { data: { dev: true, // dev true config: ..., pkg: ..., helpers: ... } }, files: [{ dest: '<%= config.workingDir %>', ... }] }, build: { options: { data: { // no dev config: ..., pkg: ..., helpers: ... } }, files: [{ dest: '<%= config.buildDir %>', ... }] } } There

问题 Here's what I want to do: Create a node package that features the following: gulpfile.js All gulp plugins, tasks, configs. Install this node package (referred to as "my-gulp" from here on) within an Angular app (referred to as "myApp" from here on) via package.json dependencies. gulpfile.js is copied into app root. All Gulp tasks can be run from app. We currently have something similar setup with Grunt (although without the Gruntfile.js copy stuff). It works pretty well to have a common setup

问题 info: Starting app... Grunt :: module.js:340 throw err; ^ Error: Cannot find module '/var/lib/openshift/54a3a0ec4382ecf1130000f1/app-root/runtime/repo/node_modules/sails/node_modules/grunt-cli/bin/grunt' at Function.Module._resolveFilename (module.js:338:15) at Function.Module._load (module.js:280:25) at Function.Module.runMain (module.js:497:10) at startup (node.js:119:16) at node.js:902:3 回答1: OpenShift needs grunt separately added to package.json, it does not contain it out of box. Try to

问题 We are trying to stand up a sandbox/evaluation instance of Zeppelin on a 4-node CentOS 6 cluster with Vagrant and having some issues with dependencies in the build process. Here is the high level script we’re running. (Have tried running this as privileged account and as a user, with the same results.) Recreate Steps Install Hadoop 2.7.0 from Binary Install Spark 1.4.0 from Binary Install Maven 3.3.3 from Binary Run the following: curl --silent --location https://rpm.nodesource.com/setup |

问题 I have a branding application where I would like to have this output: /branding/ /default/ default.css /brand1/ brand1.css /brand2/ brand2.css This one should be output from a branding folder with same structure but with .less files So I would like to do something like this: less: { production: { options: { }, files: { 'dist/branding/**/*.css': 'branding/**/*.less' } } } I just seen examples on this where they all go to same folder, but I want to keep this dynamic because in my case there is

问题 I have a serious problem (!!!) about organizing my develop environment; I have two apps: app1 and app2. This apps are written using OpenUI5 (but this detail is not important) app1 and app2 are similar and share some code (for example the code to login). I use git (with git-flow) with two remote repo and I have all equal code duplicate. Now I want optimize my develop-flow sharing equal code (login code). This is my first idea: have only one repo contains all my code in a structure of this type