Skip to content

Failed to run webapp online #31

Description

@TyrusRC

After successfully running on local machine, I have pushed my project to heroku to run online but it does not work correctly.
image
What should i do now?

Activity

  1. bourdakos1 commented on Dec 29, 2020

    @bourdakos1
    Member

    Did you check the logs?

  2. TyrusRC commented on Dec 30, 2020

    @TyrusRC
    Author

    This log?

    -----> Node.js app detected

    -----> Creating runtime environment

       NPM_CONFIG_LOGLEVEL=error
       USE_YARN_CACHE=true
       NODE_ENV=production
       NODE_MODULES_CACHE=true
       NODE_VERBOSE=false
    

    -----> Installing binaries
    engines.node (package.json): unspecified
    engines.npm (package.json): unspecified (use default)
    engines.yarn (package.json): unspecified (use default)

       Resolving node version 12.x...
       Downloading and installing node 12.20.0...
       Using default npm version: 6.14.8
       Resolving yarn version 1.22.x...
       Downloading and installing yarn (1.22.10)
       Installed yarn 1.22.10
    

    -----> Installing dependencies
    Installing node modules (yarn.lock)
    yarn install v1.22.10
    [1/4] Resolving packages...
    [2/4] Fetching packages...
    warning mini-css-extract-plugin@0.5.0: Invalid bin field for "mini-css-extract-plugin".
    warning url-loader@1.1.2: Invalid bin field for "url-loader".
    info fsevents@2.0.6: The platform "linux" is incompatible with this module.
    info "fsevents@2.0.6" is an optional dependency and failed compatibility check. Excluding it from installation.
    info fsevents@1.2.9: The platform "linux" is incompatible with this module.
    info "fsevents@1.2.9" is an optional dependency and failed compatibility check. Excluding it from installation.
    [3/4] Linking dependencies...
    warning "@cloud-annotations/models > @tensorflow/tfjs > @tensorflow/tfjs-data@1.4.0" has unmet peer dependency "seedrandom@~2.4.3".
    warning "react-scripts > @typescript-eslint/eslint-plugin@1.6.0" has unmet peer dependency "typescript@".
    warning "react-scripts > @typescript-eslint/parser@1.6.0" has unmet peer dependency "typescript@
    ".
    warning "react-scripts > @typescript-eslint/eslint-plugin > @typescript-eslint/typescript-estree@1.6.0" has unmet peer dependency "typescript@*".
    warning "react-scripts > @typescript-eslint/eslint-plugin > tsutils@3.17.1" has unmet peer dependency "typescript@>=2.8.0 || >= 3.2.0-dev || >= 3.3.0-dev || >= 3.4.0-dev || >= 3.5.0-dev || >= 3.6.0-dev || >= 3.6.0-beta || >= 3.7.0-dev || >= 3.7.0-beta".
    [4/4] Building fresh packages...
    Done in 61.50s.

    -----> Build
    Running build (yarn)
    yarn run v1.22.10
    $ react-scripts build
    Creating an optimized production build...
    Browserslist: caniuse-lite is outdated. Please run next command yarn upgrade
    Compiled with warnings.

       ./src/index.js
         Line 9:   'handlePrediction' is assigned a value but never used  no-unused-vars
         Line 15:  'render' is assigned a value but never used            no-unused-vars
       
       Search for the keywords to learn more about each warning.
       To ignore, add // eslint-disable-next-line to the line before.
       
       File sizes after gzip:
       
         252.5 KB  build/static/js/2.367fc7da.chunk.js
         1.92 KB   build/static/js/main.6b115d7b.chunk.js
         762 B     build/static/js/runtime~main.a8a9905a.js
         123 B     build/static/css/main.563c1e07.chunk.css
       
       The project was built assuming it is hosted at the server root.
       You can control this with the homepage field in your package.json.
       For example, add this to build it for GitHub Pages:
       
         "homepage" : "http://myname.github.io/myapp",
       
       The build folder is ready to be deployed.
       You may serve it with a static server:
       
         yarn global add serve
         serve -s build
       
       Find out more about deployment here:
       
         https://bit.ly/CRA-deploy
       
       Done in 48.31s.
    

    -----> Pruning devDependencies
    yarn install v1.22.10
    [1/4] Resolving packages...
    [2/4] Fetching packages...
    info fsevents@2.0.6: The platform "linux" is incompatible with this module.
    info "fsevents@2.0.6" is an optional dependency and failed compatibility check. Excluding it from installation.
    info fsevents@1.2.9: The platform "linux" is incompatible with this module.
    info "fsevents@1.2.9" is an optional dependency and failed compatibility check. Excluding it from installation.
    [3/4] Linking dependencies...
    warning "@cloud-annotations/models > @tensorflow/tfjs > @tensorflow/tfjs-data@1.4.0" has unmet peer dependency "seedrandom@~2.4.3".
    warning "react-scripts > @typescript-eslint/eslint-plugin@1.6.0" has unmet peer dependency "typescript@".
    warning "react-scripts > @typescript-eslint/parser@1.6.0" has unmet peer dependency "typescript@
    ".
    warning "react-scripts > @typescript-eslint/eslint-plugin > @typescript-eslint/typescript-estree@1.6.0" has unmet peer dependency "typescript@*".
    warning "react-scripts > @typescript-eslint/eslint-plugin > tsutils@3.17.1" has unmet peer dependency "typescript@>=2.8.0 || >= 3.2.0-dev || >= 3.3.0-dev || >= 3.4.0-dev || >= 3.5.0-dev || >= 3.6.0-dev || >= 3.6.0-beta || >= 3.7.0-dev || >= 3.7.0-beta".
    [4/4] Building fresh packages...
    warning Ignored scripts due to flag.
    Done in 12.85s.

    -----> Caching build
    - yarn cache

    -----> Build succeeded!
    ! Unmet dependencies don't fail yarn install but may cause runtime issues
    npm/npm#7494
    -----> Discovering process types
    Procfile declares types -> (none)
    Default types for buildpack -> web
    -----> Compressing...
    Done: 66.2M
    -----> Launching...
    Released v3
    https://signlookbucket.herokuapp.com/ deployed to Heroku

  3. bourdakos1 commented on Dec 30, 2020

    @bourdakos1
    Member

    Are these the logs from “heroku logs —tail”?

  4. TyrusRC commented on Dec 31, 2020

    @TyrusRC
    Author

    Sure, I just upload folder without running npm install, is it ok ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions