-
Hello,
I have made a test to rebuild the app, I want to create some new blocks and to see how it would go.
The steps I have made are these:
- checked if node is installed, yes is installed
- checked if npm is installed, yes is installed
- cd to the root directory of my app
- npm run build => got this
##############################################################################################
# npm run build
> [email protected] build /var/www/html/dev.webstartbusiness.com
> NODE_ENV=production ./node_modules/webpack/bin/webpack.js --optimize-minimize
sh: ./node_modules/webpack/bin/webpack.js: No such file or directory
npm ERR! Linux 3.10.0-693.21.1.el7.x86_64
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "run" "build"
npm ERR! node v6.14.0
npm ERR! npm v3.10.10
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! [email protected] build:
NODE_ENV=production ./node_modules/webpack/bin/webpack.js --optimize-minimizenpm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the [email protected] build script 'NODE_ENV=production ./node_modules/webpack/bin/webpack.js --optimize-minimize'.
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 SiteBuilder-Pro package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! NODE_ENV=production ./node_modules/webpack/bin/webpack.js --optimize-minimize
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs SiteBuilder-Pro
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls SiteBuilder-Pro
npm ERR! There is likely additional logging output above.
npm WARN Local package.json exists, but node_modules missing, did you mean to install?
npm ERR! Please include the following file with any support request:
npm ERR! /var/www/html/dev.webstartbusiness.com/npm-debug.log
[root@centos-s-1vcpu-1gb-nyc1-01 dev.webstartbusiness.com]# npm install
npm WARN deprecated [email protected]: Use preset options to disable module transformation https://github.com/gajus/babel-preset-es2015-webpack#deprecated
npm WARN deprecated [email protected]: 🙌 Thanks for using Babel: we recommend using babel-preset-env now: please read babeljs.io/env to update!
npm WARN deprecated [email protected]: gulp-util is deprecated - replace it, following the guidelines at https://medium.com/gulpjs/gulp-util-ca3b1f9f9ac5
npm WARN prefer global [email protected] should be installed with -g
> [email protected] install /var/www/html/dev.webstartbusiness.com/node_modules/node-sass
> node scripts/install.js
############################################################################################
After this I thought I might run first npm install command first to install dependencies so I ran it and got this:
###########################################################################################
npm install
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.1.2 (node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN [email protected] requires a peer of bootstrap@>=3.0.0 but none was installed.
############################################################################################
I ran again npm run build
############################################################################################
npm run build
> [email protected] build /var/www/html/dev.webstartbusiness.com
> NODE_ENV=production ./node_modules/webpack/bin/webpack.js --optimize-minimize
[16:43:53] [write-file-webpack-plugin] options { exitOnErrors: true,
force: false,
log: true,
test: null,
useHashIndex: true }
clean-webpack-plugin: /var/www/html/dev.webstartbusiness.com/build has been removed.
(node:6081) DeprecationWarning: loaderUtils.parseQuery() received a non-string value which can be problematic, see https://github.com/webpack/loader-utils/issues/56
parseQuery() will be replaced with getOptions() in the next major version of loader-utils.
(node:6081) DeprecationWarning: loaderUtils.parseQuery() received a non-string value which can be problematic, see https://github.com/webpack/loader-utils/issues/56
parseQuery() will be replaced with getOptions() in the next major version of loader-utils.
Killed
#############################################################################################
I have attached print screen how it looks the app's interface after this.
I have follow this article: https://support.bloxby.com/knowledge-base/block-development-webpack/
and this: https://www.notion.so/Developing-SB-Pro-0c7a0d8049f6406ebd038ab9dd622b3e
I might be something I have probably missed out but the documentation in the article was not clear enough.
Can you please en light me up what I have missed out?
Thank you
Attachments:
You must be logged in to view attached files.
The topic ‘npm run build messes up the app’ is closed to new replies.
