Ich benutze Heroku, aber es scheint, dass es meinen Code nicht jedes Mal aktualisiere, wenn ich es zum Master schiebe.Heroku aktualisiert nicht
$ git add .
$ git commit -am "make it better"
$ git push heroku master
Aber nachdem ich dies tun nichts passiert .... Die Ausgabe nachdem ich schieben Sie es auf den Master:
Counting objects: 6, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (6/6), done.
Writing objects: 100% (6/6), 494 bytes | 0 bytes/s, done.
Total 6 (delta 5), reused 0 (delta 0)
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_ENV=production
remote: NODE_MODULES_CACHE=true
remote:
remote: -----> Installing binaries
remote: engines.node (package.json): unspecified
remote: engines.npm (package.json): unspecified (use default)
remote:
remote: Resolving node version (latest stable) via semver.io...
remote: Downloading and installing node 6.9.1...
remote: Using default npm version: 3.10.8
remote:
remote: -----> Restoring cache
remote: Loading 2 from cacheDirectories (default):
remote: - node_modules
remote: - bower_components (not cached - skipping)
remote:
remote: -----> Building dependencies
remote: Installing node modules (package.json)
remote:
remote: > [email protected] postinstall /tmp/build_dcfbba691d5c6f4b81e12dbe7f938c55
remote: > npm run build:prod
remote:
remote:
remote: > [email protected] build:prod /tmp/build_dcfbba691d5c6f4b81e12dbe7f938c55
remote: > node bin/bundler.js --prod
remote:
remote: Unhandled rejection Error on fetch for app/main.js at file:///tmp/build_dcfbba691d5c6f4b81e12dbe7f938c55/app/main.js
remote: Error: ENOENT: no such file or directory, open '/tmp/build_dcfbba691d5c6f4b81e12dbe7f938c55/app/main.js'
remote: at Error (native)
remote:
remote: -----> Caching build
remote: Clearing previous node cache
remote: Saving 2 cacheDirectories (default):
remote: - node_modules
remote: - bower_components (nothing to cache)
remote:
remote: -----> Build succeeded!
remote: ├── @angular/[email protected]
remote: ├── @angular/[email protected]
remote: ├── @angular/[email protected]
remote: ├── @angular/[email protected].1.2
remote: ├── @angular/[email protected]
remote: ├── @angular/[email protected]
remote: ├── @angular/[email protected]
remote: ├── @angular/[email protected]
remote: ├── @angular/[email protected]
remote: ├── @types/[email protected]
remote: ├── @types/[email protected]
remote: ├── [email protected]
remote: ├── [email protected]
remote: ├── [email protected]
remote: ├── [email protected]
remote: ├── [email protected]
remote: ├── [email protected]
remote: ├── [email protected]
remote: ├── [email protected]
remote: ├── [email protected]
remote: ├── UNMET PEER DEPENDENCY [email protected]
remote: ├── [email protected]
remote: ├── [email protected]
remote: ├── [email protected]
remote: └── UNMET PEER DEPENDENCY [email protected]
remote:
remote: ! Unmet dependencies don't fail npm install but may cause runtime issues
remote: https://github.com/npm/npm/issues/7494
remote:
remote: -----> Discovering process types
remote: Procfile declares types -> web
remote:
remote: -----> Compressing...
remote: Done: 35.5M
remote: -----> Launching...
remote: Released v5
remote: https://something.herokuapp.com/ deployed to Heroku
remote:
remote: Verifying deploy... done.
To https://git.heroku.com/something.git
fd25f32..505de47 master -> master
Das Merkwürdige ist, dass es irgendwie geschafft, ich es einsetzen, aber nicht weiß wie ich es wirklich gemacht habe. Auch wenn ich mir anschaute, wann ich das letzte vor einiger Zeit eingesetzt habe. Vielen Dank im Voraus!
Es gibt keine Ausgabe nach dem Versuch zu drücken? –
Ich habe meinen Beitrag für ein bisschen mehr Informationen bearbeitet! – John
Hmm sind irgendwelche dieser unerfüllten Abhängigkeiten erforderlich? –