We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Починить сборку:
Starting to optimize CSS... Processing style.css... Processed style.css, before: 115853, after: 115812, ratio: 99.96% Hash: e941fc2d23a0e6c63c5d Version: webpack 2.6.1 Time: 32312ms Asset Size Chunks Chunk Names glyphicons-halflings-regular.woff 23.4 kB [emitted] derevo3.jpg 394 kB [emitted] [big] glyphicons-halflings-regular.eot 20.1 kB [emitted] modalBG.png 1.46 MB [emitted] [big] glyphicons-halflings-regular.svg 109 kB [emitted] glyphicons-halflings-regular.ttf 45.4 kB [emitted] spinner.png 10.3 kB [emitted] glyphicons-halflings-regular.woff2 18 kB [emitted] build.js 404 kB 0 [emitted] [big] main style.css 116 kB 0 [emitted] main build.js.map 3.4 MB 0 [emitted] main style.css.map 86 bytes 0 [emitted] main WARNING in ./client/api/socket.js /app/client/api/socket.js 14:5 warning Unexpected console statement no-console 19:5 warning Unexpected console statement no-console 33:5 warning Unexpected console statement no-console 44:5 warning Unexpected console statement no-console 64:5 warning Unexpected console statement no-console 74:5 warning Unexpected console statement no-console 79:5 warning Unexpected console statement no-console ✖ 7 problems (0 errors, 7 warnings) @ ./client/main.js 4:0-34 WARNING in ./client/store/modules/playersStore.js /app/client/store/modules/playersStore.js 7:13 warning Unexpected console statement no-console 12:13 warning Unexpected console statement no-console 20:13 warning Unexpected console statement no-console 49:13 warning Unexpected console statement no-console ✖ 4 problems (0 errors, 4 warnings) @ ./client/store/index.js 5:0-53 @ ./client/main.js WARNING in ./client/store/modules/konvaStore.js /app/client/store/modules/konvaStore.js 33:17 warning Unexpected console statement no-console 79:13 warning Unexpected console statement no-console 84:13 warning Unexpected console statement no-console 95:13 warning Unexpected console statement no-console 110:13 warning Unexpected console statement no-console ✖ 5 problems (0 errors, 5 warnings) @ ./client/store/index.js 6:0-49 @ ./client/main.js ERROR in ./client/main.js /app/client/main.js 6:8 error 'bootstrap' is defined but never used no-unused-vars 42:46 error 'e' is defined but never used no-unused-vars ✖ 2 problems (2 errors, 0 warnings) ERROR in ./client/main.js Module not found: Error: Can't resolve 'imports' in '/app' @ ./client/main.js 6:0-34 npm ERR! Linux 3.13.0-112-generic npm ERR! argv "/app/.heroku/node/bin/node" "/app/.heroku/node/bin/npm" "run" "build" npm ERR! node v6.10.3 npm ERR! npm v3.10.10 npm ERR! code ELIFECYCLE npm ERR! [email protected] build: `cross-env NODE_ENV=production webpack —progress —hide-modules` npm ERR! Exit status 2 npm ERR! npm ERR! Failed at the [email protected] build script 'cross-env NODE_ENV=production webpack —progress —hide-modules'. npm ERR! Make sure you have the latest version of node.js and npm installed. npm ERR! If you do, this is most likely a problem with the warlock-server package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! cross-env NODE_ENV=production webpack —progress —hide-modules npm ERR! You can get information on how to open an issue for this project with: npm ERR! npm bugs warlock-server npm ERR! Or if that isn't available, you can get their info via: npm ERR! npm owner ls warlock-server npm ERR! There is likely additional logging output above. npm ERR! Please include the following file with any support request: npm ERR! /app/npm-debug.log
The text was updated successfully, but these errors were encountered:
dyadyaJora
No branches or pull requests
Починить сборку:
The text was updated successfully, but these errors were encountered: