search

OpenSourceWorkflow / generator-kickstart

[deprecated]: yeoman generator for website development
MIT License
10 stars 1 forks source link

update grunt depedencies #182

Open markusfalk opened 8 years ago

markusfalk commented 8 years ago

update all deps in grunt file and check if they still work

stephanfriedrich commented 8 years ago

i think its also nice to split, deploy and dev dependencies. Linke: (example below not tested)

  "dependencies": {
    "grunt": "^0.4",
    "grunt-contrib-clean": "^0.6",
    "grunt-contrib-compass": "^1",
    "grunt-contrib-imagemin": "^0.8",
    "grunt-contrib-requirejs": "^0.4",
    "grunt-contrib-uglify": "^0.9",
    "grunt-modernizr": "^0.6",
    "grunt-replace": "^0.8",
    "grunt-sync": "0.2"
  },
  "devDependencies": {
    "grunt-accessibility": "^3",
    "grunt-contrib-connect": "^0.10",
    "grunt-contrib-copy": "^0.8",
    "grunt-contrib-csslint": "^0.4",
    "grunt-contrib-jshint": "^0.11",
    "grunt-contrib-qunit": "^0.7",
    "grunt-contrib-watch": "^0.6",
    "grunt-jsdoc": "^0.6",
    "grunt-newer": "^1",
    "grunt-scss-lint": "^0.3",
    "jshint-stylish": "^1"
  }
markusfalk commented 8 years ago

all of them are devDependencies. none of them is deployed.

stephanfriedrich commented 8 years ago

what i mean, As a backend developer, i wont install unnecessary modules ( for the Tasks test, doc). with npm install --production only dependencies will be installed.

markusfalk commented 8 years ago

I know what you were trying to accomplish but still from a node package point of view all of those are devDependencies and will not be deployed.

If you need a subset of devDependencies for the deployment itself you might need to write your own command for installation within your deployment environment. 

$ npm i grunt, grunt-contrib-clean, grunt-contrib-compass, grunt-contrib-imagemin, grunt-contrib-requirejs, grunt-contrib-uglify, grunt-modernizr, grunt-replace, grunt-sync