Build failure on linux

#1

Hello

I get this error durung the build

git commit: 5db5ca1607

$ nodejs --version
v9.3.0

I had this after cleaning the node_modules directory:

$ npm install

> serialport@6.2.2 install /data/od/open-stage-control/node_modules/serialport
> prebuild-install || node-gyp rebuild


> node-sass@4.11.0 install /data/od/open-stage-control/node_modules/node-sass
> node scripts/install.js

Cached binary found at /home/eric/.npm/node-sass/4.11.0/linux-x64-59_binding.node

> electron@1.8.8 postinstall /data/od/open-stage-control/node_modules/electron
> node install.js


> node-sass@4.11.0 postinstall /data/od/open-stage-control/node_modules/node-sass
> node scripts/build.js

Binary found at /data/od/open-stage-control/node_modules/node-sass/vendor/linux-x64-59/binding.node
Testing binary
Binary is fine

> nodemon@1.18.10 postinstall /data/od/open-stage-control/node_modules/nodemon
> node bin/postinstall || exit 0


> open-stage-control@0.44.0 postinstall /data/od/open-stage-control
> echo '\033[36m=> Dependencies installed successfully. Run "npm run build" to build the assets.\033[0m
'

=> Dependencies installed successfully. Run "npm run build" to build the assets.

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.7 (node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.7: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

added 1115 packages in 23.016s
eric@pc-eric:/data/od/open-stage-control$ npm run build

> open-stage-control@0.44.0 build /data/od/open-stage-control
> npm run build-css && npm run build-js && node scripts/copy-assets.js && echo '\033[36m=> JS and CSS assets built successfully. Run "npm run package" to build an executable or "npm start" to run the app.\033[0m
'


> open-stage-control@0.44.0 build-css /data/od/open-stage-control
> node scripts/build-css.js


> open-stage-control@0.44.0 build-js /data/od/open-stage-control
> npm run build-launcher-js && npm run build-client-js -- --prod && npm run build-server-js


> open-stage-control@0.44.0 build-launcher-js /data/od/open-stage-control
> node scripts/build-launcher.js


> open-stage-control@0.44.0 build-client-js /data/od/open-stage-control
> node scripts/build-client.js "--prod"

=> Building minified client bundle, this may take a while...

WARNING: We noticed you're using the `useBuiltIns` option without declaring a core-js version. Currently, we assume version 2.x when no version is passed. Since this default version will likely change in future versions of Babel, we recommend explicitly setting the core-js version you are using via the `corejs` option.

You should also be sure that the version you pass to the `corejs` option matches the version specified in your `package.json`'s `dependencies` section. If it doesn't, you need to run one of the following commands:

  npm install --save core-js@2    npm install --save core-js@3
  yarn add core-js@2              yarn add core-js@3

events.js:136
      throw er; // Unhandled 'error' event
      ^

TypeError: [BABEL] /data/od/open-stage-control/src/client/index.js: (0 , _semver(...).coerce) is not a function (While processing: "/data/od/open-stage-control/node_modules/@babel/preset-env/lib/index.js") while parsing file: /data/od/open-stage-control/src/client/index.js
    at normalizeCoreJSOption (/data/od/open-stage-control/node_modules/@babel/preset-env/lib/normalize-options.js:173:53)
    at normalizeOptions (/data/od/open-stage-control/node_modules/@babel/preset-env/lib/normalize-options.js:192:18)
    at _default (/data/od/open-stage-control/node_modules/@babel/preset-env/lib/index.js:109:37)
    at /data/od/open-stage-control/node_modules/@babel/helper-plugin-utils/lib/index.js:19:12
    at loadDescriptor (/data/od/open-stage-control/node_modules/@babel/core/lib/config/full.js:165:14)
    at cachedFunction (/data/od/open-stage-control/node_modules/@babel/core/lib/config/caching.js:33:19)
    at loadPresetDescriptor (/data/od/open-stage-control/node_modules/@babel/core/lib/config/full.js:235:63)
    at config.presets.reduce (/data/od/open-stage-control/node_modules/@babel/core/lib/config/full.js:77:21)
    at Array.reduce (<anonymous>)
    at recurseDescriptors (/data/od/open-stage-control/node_modules/@babel/core/lib/config/full.js:74:38)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! open-stage-control@0.44.0 build-client-js: `node scripts/build-client.js "--prod"`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the open-stage-control@0.44.0 build-client-js script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/eric/.npm/_logs/2019-04-02T20_25_26_796Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! open-stage-control@0.44.0 build-js: `npm run build-launcher-js && npm run build-client-js -- --prod && npm run build-server-js`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the open-stage-control@0.44.0 build-js script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/eric/.npm/_logs/2019-04-02T20_25_26_814Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! open-stage-control@0.44.0 build: `npm run build-css && npm run build-js && node scripts/copy-assets.js && echo '\033[36m=> JS and CSS assets built successfully. Run "npm run package" to build an executable or "npm start" to run the app.\033[0m
npm ERR! '`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the open-stage-control@0.44.0 build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/eric/.npm/_logs/2019-04-02T20_25_26_828Z-debug.log
#2

I tried to go back a little.

at commit f97a2cf0baeb6de43a3405a7042a3cc00745cfe2, I was able to build.

@jean-emmanuel, do you want me to do a bisect?

#3

I’m unable to reproduce this using node v9.3.0. It might be a cache issue with npm, can you remove node_module/ before running npm install ?

#4

can you remove node_module/ before running npm install ?

Yes, I have done it.
node v9.3.0
npm v5.6.0

can you allow the upload of .zip , .json or .log files?

#5

As suggested here:

npm i semver fixed the problem

#6

Ok cool, commit 02de885bcc557286a22700447bd9aaf664915cfe should prevent it then since core-js brings semver too.