Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- -> Build
- remote: Running build (yarn)
- remote: yarn run v1.22.10
- remote: $ webpack --mode production
- remote: assets by status 0 bytes [cached] 1 asset
- remote:
- remote: ERROR in main
- remote: Module not found: Error: Can't resolve './src' in '/tmp/build_c9c1f5ec'
- remote: resolve './src' in '/tmp/build_c9c1f5ec'
- remote: using description file: /tmp/build_c9c1f5ec/package.json (relative path: .)
- remote: Field 'browser' doesn't contain a valid alias configuration
- remote: using description file: /tmp/build_c9c1f5ec/package.json (relative path: ./src)
- remote: no extension
- remote: Field 'browser' doesn't contain a valid alias configuration
- remote: /tmp/build_c9c1f5ec/src doesn't exist
- remote: .js
- remote: Field 'browser' doesn't contain a valid alias configuration
- remote: /tmp/build_c9c1f5ec/src.js doesn't exist
- remote: .json
- remote: Field 'browser' doesn't contain a valid alias configuration
- remote: /tmp/build_c9c1f5ec/src.json doesn't exist
- remote: .wasm
- remote: Field 'browser' doesn't contain a valid alias configuration
- remote: /tmp/build_c9c1f5ec/src.wasm doesn't exist
- remote: as directory
- remote: /tmp/build_c9c1f5ec/src doesn't exist
- remote:
- remote: webpack 5.24.2 compiled with 1 error in 215 ms
- remote: error Command failed with exit code 1.
- remote: info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
- 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: - Node version not specified in package.json
- 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...
Advertisement
Add Comment
Please, Sign In to add comment