Trying to upgrade here and got NPM error on JS Client

16 views
Skip to first unread message

Mail Sender

unread,
Dec 11, 2019, 3:15:37 PM12/11/19
to YesCart - pure eCommerce, platform with open source
Hi there, I am upgrading to 3.4.1 from 3.4.0-SNAPSHOT (somewhere 2018-01 version) and now I got NPM compilation error on JS Client.

Maybe my NPM, node should be updated?

Versions on my machine:
  • java: 1.8.0_201
  • maven: 3.6.0
  • ant: 1.10.7
  • node: v11.10.0
  • npm: 6.9.0
Attaching logs:
[DEBUG] Executing command line: [C:\WINDOWS\system32\cmd.exe, /c, "C:\Program Files\nodejs\npm.cmd", install]
npm WARN read-shrinkwrap This version of npm is compatible with lockfileVersion@1, but npm-shrinkwrap.json was generated for lockfileVersion@0. I'll try to do my best with it!
npm WARN deprecated fsev...@1.1.3: Way too old

> yes-ca...@3.4.1 postinstall C:\code\mydomain.com\manager\jam-jsclient\src\main\typescript
> gulp check.versions && gulp build.bundle.rxjs && npm prune && gulp webdriver && gulp print.banner

[22:06:17] Requiring external module ts-node/register
gulp[19384]: src\node_contextify.cc:631: Assertion `args[1]->IsString()' failed.
 1: 00007FF6DCF2CC3A v8::internal::GCIdleTimeHandler::GCIdleTimeHandler+4618
 2: 00007FF6DCED98B6 uv_loop_fork+80934
 3: 00007FF6DCED9963 uv_loop_fork+81107
 4: 00007FF6DCEDFE62 uv_loop_fork+106962
 5: 00007FF6DD561BCE v8::internal::OptimizingCompileDispatcher::Unblock+910
 6: 00007FF6DD562E0C v8::internal::OptimizingCompileDispatcher::Unblock+5580
 7: 00007FF6DD56208D v8::internal::OptimizingCompileDispatcher::Unblock+2125
 8: 00007FF6DD561FAB v8::internal::OptimizingCompileDispatcher::Unblock+1899
 9: 00000253304D0461
npm ERR! code ELIFECYCLE
npm ERR! errno 134
npm ERR! yes-ca...@3.4.1 postinstall: `gulp check.versions && gulp build.bundle.rxjs && npm prune && gulp webdriver && gulp print.banner`
npm ERR! Exit status 134
npm ERR!
npm ERR! Failed at the yes-ca...@3.4.1 postinstall 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!     C:\Users\user\AppData\Roaming\npm-cache\_logs\2019-12-11T20_06_17_296Z-debug.log
[ERROR] Command execution failed.
org.apache.commons.exec.ExecuteException: Process exited with an error: 134 (Exit value: 134)
    at org.apache.commons.exec.DefaultExecutor.executeInternal (DefaultExecutor.java:404)
    at org.apache.commons.exec.DefaultExecutor.execute (DefaultExecutor.java:166)
    at org.codehaus.mojo.exec.ExecMojo.executeCommandLine (ExecMojo.java:764)
    at org.codehaus.mojo.exec.ExecMojo.executeCommandLine (ExecMojo.java:711)
    at org.codehaus.mojo.exec.ExecMojo.execute (ExecMojo.java:289)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
    at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
    at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke (Method.java:498)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:289)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:229)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:415)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:356)
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for Yes cart JAM: JS client 3.4.1:
[INFO]
[INFO] Yes cart JAM: JS client ............................ FAILURE [ 16.491 s]
[INFO] Yes cart JAM: server ............................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] BUILD FAILURE

Please give me any hints how can I resolve this.

Yes Cart

unread,
Dec 11, 2019, 3:49:19 PM12/11/19
to YesCart - pure eCommerce, platform with open source
Hi,

You need to downgrade version of Node to 8.x.x

Regards,
YC team

Mail Sender

unread,
Dec 11, 2019, 5:02:57 PM12/11/19
to YesCart - pure eCommerce, platform with open source
Thanks a lot, it worked
Reply all
Reply to author
Forward
0 new messages