Ponieważ poprzedni seed napsuł mi krwi przy próbie skonfigurowania karmy, to wziąłem się za kolejny, który uprzykrza mi życie w nowy sposób.
https://github.com/AngularClass/angular2-webpack-starter
Próbuję postawić niedotykane ziarno, niestety bez sukcesów.
D:\projects\fortys-edu>git clone https://github.com/AngularClass/angular2-webpack-starter experiment
Cloning into 'experiment'...
remote: Counting objects: 8131, done.
remote: Total 8131 (delta 0), reused 0 (delta 0), pack-reused 8131
Receiving objects: 100% (8131/8131), 3.18 MiB | 2.61 MiB/s, done.
Resolving deltas: 100% (4704/4704), done.
D:\projects\fortys-edu>cd experiment
D:\projects\fortys-edu\experiment>heroku create
Creating app... done, powerful-badlands-10276
https://powerful-badlands-10276.herokuapp.com/ | https://git.heroku.com/powerful-badlands-10276.git
D:\projects\fortys-edu\experiment>heroku buildpacks:add heroku/nodejs
Buildpack added. Next release on powerful-badlands-10276 will use heroku/nodejs.
Run git push heroku master to create a new release using this buildpack.
D:\projects\fortys-edu\experiment>git push heroku master
Counting objects: 7608, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (3058/3058), done.
Writing objects: 100% (7608/7608), 2.51 MiB | 335.00 KiB/s, done.
Total 7608 (delta 4351), reused 7608 (delta 4351)
remote: Compressing source files... done.
remote: Building source:
remote:
remote: -----> Node.js app detected
remote:
remote: -----> Creating runtime environment
remote:
remote: NPM_CONFIG_LOGLEVEL=error
remote: NPM_CONFIG_PRODUCTION=true
remote: NODE_VERBOSE=false
remote: NODE_ENV=production
remote: NODE_MODULES_CACHE=true
remote:
remote: -----> Installing binaries
remote: engines.node (package.json): >= 4.2.1
remote: engines.npm (package.json): >= 3
remote:
remote: Resolving node version >= 4.2.1 via semver.io...
remote: Downloading and installing node 7.8.0...
remote: Resolving npm version >= 3 via semver.io...
remote: Downloading and installing npm 4.4.4 (replacing version 4.2.0)...
remote:
remote: -----> Restoring cache
remote: Skipping cache restore (new runtime signature)
remote:
remote: -----> Building dependencies
remote: Installing node modules (package.json)
remote:
remote: > [email protected] postinstall /tmp/build_4abbe38a654690bf69b0f07ba684b7f7
remote: > npm run webdriver:update
remote:
remote:
remote: > [email protected] webdriver:update /tmp/build_4abbe38a654690bf69b0f07ba684b7f7
remote: > webdriver-manager update
remote:
remote: sh: 1: webdriver-manager: not found
remote: npm ERR! file sh
remote: npm ERR! code ELIFECYCLE
remote: npm ERR! errno ENOENT
remote: npm ERR! syscall spawn
remote: npm ERR! [email protected] webdriver:update: `webdriver-manager update`
remote: npm ERR! spawn ENOENT
remote: npm ERR!
remote: npm ERR! Failed at the [email protected] webdriver:update script 'webdriver-manager update'.
remote: npm ERR! Make sure you have the latest version of node.js and npm installed.
remote: npm ERR! If you do, this is most likely a problem with the angular2-webpack-starter package,
remote: npm ERR! not with npm itself.
remote: npm ERR! Tell the author that this fails on your system:
remote: npm ERR! webdriver-manager update
remote: npm ERR! You can get information on how to open an issue for this project with:
remote: npm ERR! npm bugs angular2-webpack-starter
remote: npm ERR! Or if that isn't available, you can get their info via:
remote: npm ERR! npm owner ls angular2-webpack-starter
remote: npm ERR! There is likely additional logging output above.
remote:
remote: npm ERR! A complete log of this run can be found in:
remote: npm ERR! /app/.npm/_logs/2017-04-06T11_48_27_825Z-debug.log
remote: npm ERR! code ELIFECYCLE
remote: npm ERR! errno 1
remote: npm ERR! [email protected] postinstall: `npm run webdriver:update`
remote: npm ERR! Exit status 1
remote: npm ERR!
remote: npm ERR! Failed at the [email protected] postinstall script 'npm run webdriver:update'.
remote: npm ERR! Make sure you have the latest version of node.js and npm installed.
remote: npm ERR! If you do, this is most likely a problem with the angular2-webpack-starter package,
remote: npm ERR! not with npm itself.
remote: npm ERR! Tell the author that this fails on your system:
remote: npm ERR! npm run webdriver:update
remote: npm ERR! You can get information on how to open an issue for this project with:
remote: npm ERR! npm bugs angular2-webpack-starter
remote: npm ERR! Or if that isn't available, you can get their info via:
remote: npm ERR! npm owner ls angular2-webpack-starter
remote: npm ERR! There is likely additional logging output above.
remote:
remote: npm ERR! A complete log of this run can be found in:
remote: npm ERR! /app/.npm/_logs/2017-04-06T11_48_27_884Z-debug.log
remote:
remote: -----> Build failed
remote:
remote: We're sorry this build is failing! You can troubleshoot common issues here:
remote: https://devcenter.heroku.com/articles/troubleshooting-node-deploys
remote:
remote: Some possible problems:
remote:
remote: - Dangerous semver range (>) in engines.node
remote: https://devcenter.heroku.com/articles/nodejs-support#specifying-a-node-js-version
remote:
remote: Love,
remote: Heroku
remote:
remote: ! Push rejected, failed to compile Node.js app.
remote:
remote: ! Push failed
remote: Verifying deploy...
remote:
remote: ! Push rejected to powerful-badlands-10276.
remote:
To https://git.heroku.com/powerful-badlands-10276.git
! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to 'https://git.heroku.com/powerful-badlands-10276.git'
Przeczytałem, że jedną z opcji jest zaciągnięcie devDependencies - tak też zrobiłem; Przeglądarka mieliła żądanie przez minutę by pokazać mi application error; Zajrzałem więc w heroku logs, by ujrzeć to:
2017-04-06T11:59:45.274347+00:00 app[web.1]: webpack: Compiled successfully.
2017-04-06T11:59:45.274346+00:00 app[web.1]: chunk {0} index.html 543 kB [entry]
2017-04-06T12:00:22.359073+00:00 heroku[web.1]: Error R10 (Boot timeout) -> Web process failed to bind to $PORT within 60 seconds of launch
2017-04-06T12:00:22.359073+00:00 heroku[web.1]: Stopping process with SIGKILL
2017-04-06T12:00:22.501848+00:00 heroku[web.1]: Process exited with status 137
2017-04-06T12:00:22.520449+00:00 heroku[web.1]: State changed from starting to crashed
2017-04-06T12:00:23.333055+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=powerful-badlands-10276.herokuapp.com request_id=e774b2f8-bdff-4d3c-9f1e-a7afd5311016 fwd="31.178.201.8" dyno= connect= service= status=503 bytes= protocol=https
2017-04-06T12:00:24.391260+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=powerful-badlands-10276.herokuapp.com request_id=ff391e99-668e-458c-8794-c49221d08187 fwd="31.178.201.8" dyno= connect= service= status=503 bytes= protocol=https
2017-04-06T12:00:25.323738+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=powerful-badlands-10276.herokuapp.com request_id=c5d4f38a-1e4f-4811-abe5-f478a9d0b872 fwd="31.178.201.8" dyno= connect= service= status=503 bytes= protocol=https
2017-04-06T12:03:00.452452+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=powerful-badlands-10276.herokuapp.com request_id=73726835-52d2-4b49-8172-6cf4b535059f fwd="31.178.201.8" dyno= connect= service= status=503 bytes= protocol=https
Jakieś pomysły?