search

PatrickJS / NG6-starter

:ng: An AngularJS Starter repo for AngularJS + ES6 + Webpack
https://angularclass.github.io/NG6-starter
Apache License 2.0
1.91k stars 1.35k forks source link

Updating all the packages is throwing a blank page with no console errors #176

Open josoroma-zz opened 8 years ago

josoroma-zz commented 8 years ago

Hi Hackers!

I just try to update all the packages using:

npm install --save \
angular \
angular-ui-router \
normalize.css
npm install --save-dev \
angular-mocks \
babel-core \
babel-loader \
babel-polyfill \
babel-plugin-transform-runtime \
babel-preset-es2015 \
babel-preset-stage-0 \
babel-register \
babel-runtime \
browser-sync \
chai \
connect-history-api-fallback \
css-loader \
del \
fs-walk \
gulp \
gulp-rename \
gulp-template \
gulp-util \
html-webpack-plugin \
karma \
karma-chai \
karma-chrome-launcher \
karma-mocha \
karma-mocha-reporter \
karma-sourcemap-loader \
karma-webpack \
lodash \
mocha \
ng-annotate-loader \
node-libs-browser \
raw-loader \
run-sequence \
style-loader \
stylus \
stylus-loader \
supports-color \
webpack \
webpack-dev-middleware \
webpack-hot-middleware \
yargs

then I try to run the starter using gulp but I am hitting a blank page with no console errors.

Any of you had this problem before?

Thanks in advance.

  "dependencies": {
    "angular": "^1.5.8",
    "angular-ui-router": "^0.3.1",
    "normalize.css": "^5.0.0"
  },
  "devDependencies": {
    "angular-mocks": "^1.5.8",
    "babel-core": "^6.17.0",
    "babel-loader": "^6.2.5",
    "babel-plugin-transform-runtime": "^6.15.0",
    "babel-polyfill": "^6.16.0",
    "babel-preset-es2015": "^6.16.0",
    "babel-preset-stage-0": "^6.16.0",
    "babel-register": "^6.16.3",
    "babel-runtime": "^6.11.6",
    "browser-sync": "^2.17.0",
    "chai": "^3.5.0",
    "connect-history-api-fallback": "^1.3.0",
    "css-loader": "^0.25.0",
    "del": "^2.2.2",
    "fs-walk": "0.0.1",
    "gulp": "^3.9.1",
    "gulp-rename": "^1.2.2",
    "gulp-template": "^4.0.0",
    "gulp-util": "^3.0.7",
    "html-webpack-plugin": "^2.22.0",
    "karma": "^1.3.0",
    "karma-chai": "^0.1.0",
    "karma-chrome-launcher": "^2.0.0",
    "karma-mocha": "^1.2.0",
    "karma-mocha-reporter": "^2.2.0",
    "karma-sourcemap-loader": "^0.3.7",
    "karma-webpack": "^1.8.0",
    "lodash": "^4.16.3",
    "mocha": "^3.1.0",
    "ng-annotate-loader": "^0.2.0",
    "node-libs-browser": "^1.0.0",
    "raw-loader": "^0.5.1",
    "run-sequence": "^1.2.2",
    "style-loader": "^0.13.1",
    "stylus": "^0.54.5",
    "stylus-loader": "^2.3.1",
    "supports-color": "^3.1.2",
    "webpack": "^1.13.2",
    "webpack-dev-middleware": "^1.8.3",
    "webpack-hot-middleware": "^2.12.2",
    "yargs": "^6.0.0"
  }
IvanBisultanov commented 8 years ago

Hi @josoroma I use this tool https://github.com/tjunnone/npm-check-updates And don't have any problem

p.s. I didn't update this 

karma                  ^0.13.9  →  ^1.3.0
 karma-chrome-launcher   ^0.2.0  →  ^2.0.0
 karma-mocha             ^0.2.0  →  ^1.2.0
 karma-mocha-reporter    ^1.0.2  →  ^2.2.0
 mocha                   ^2.3.0  →  ^3.1.0
 yargs                   ^4.8.1  →  ^6.0.0