lidaof / eg-react

WashU Epigenome Browser
https://epigenomegateway.wustl.edu
Other
66 stars 29 forks source link

In front-end, npm start exited without any info #278

Closed Tong-Chen closed 1 year ago

Tong-Chen commented 2 years ago

When I try to install this version of eg, I download the zipped version of eg-react source code by clicking Code - Download zip in the eg-react repository.

Changing dir into front-end, and run npm install, with no explicit errors like below:

npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: webpack-dev-middleware@1.12.2
npm WARN Found: webpack@4.42.0
npm WARN node_modules/webpack
npm WARN   dev webpack@"^4.42.0" from the root project
npm WARN   21 more (babel-loader, dotenv-webpack, eslint-loader, ...)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer webpack@"^1.0.0 || ^2.0.0 || ^3.0.0" from webpack-dev-middleware@1.12.2
npm WARN node_modules/webpack-dev-middleware
npm WARN   webpack-dev-middleware@"^1.12.2" from @storybook/core@3.4.12
npm WARN   node_modules/@storybook/core
npm WARN 
npm WARN Conflicting peer dependency: webpack@3.12.0
npm WARN node_modules/webpack
npm WARN   peer webpack@"^1.0.0 || ^2.0.0 || ^3.0.0" from webpack-dev-middleware@1.12.2
npm WARN   node_modules/webpack-dev-middleware
npm WARN     webpack-dev-middleware@"^1.12.2" from @storybook/core@3.4.12
npm WARN     node_modules/@storybook/core
npm WARN deprecated tar@2.2.2: This version of tar is no longer supported, and will not receive security updates. Please upgrade asap.

up to date, audited 3559 packages in 2m

138 packages are looking for funding
  run `npm fund` for details

152 vulnerabilities (12 low, 87 moderate, 45 high, 8 critical)

To address issues that do not require attention, run:
  npm audit fix

To address all issues possible (including breaking changes), run:
  npm audit fix --force

Some issues need review, and may require choosing
a different dependency.

Run `npm audit` for details.

Then, run npm start -d, npm exists with no error info in one minute.

npm info using npm@8.11.0
npm info using node@v16.16.0
npm timing npm:load:whichnode Completed in 0ms
npm timing config:load:defaults Completed in 1ms
npm timing config:load:file:/var/www/html/node-v16.16.0-linux-x64/lib/node_modules/npm/npmrc Completed in 1ms
npm timing config:load:builtin Completed in 1ms
npm timing config:load:cli Completed in 2ms
npm timing config:load:env Completed in 0ms
npm timing config:load:file:/var/www/html/eg_test/eg-react-master/frontend/.npmrc Completed in 1ms
npm timing config:load:project Completed in 4ms
npm timing config:load:file:/home/xuepu/.npmrc Completed in 0ms
npm timing config:load:user Completed in 0ms
npm timing config:load:file:/var/www/html/node-v16.16.0-linux-x64/etc/npmrc Completed in 0ms
npm timing config:load:global Completed in 1ms
npm timing config:load:validate Completed in 0ms
npm timing config:load:credentials Completed in 0ms
npm timing config:load:setEnvs Completed in 1ms
npm timing config:load Completed in 10ms
npm timing npm:load:configload Completed in 10ms
npm timing npm:load:mkdirpcache Completed in 3ms
npm timing npm:load:mkdirplogs Completed in 0ms
npm timing npm:load:setTitle Completed in 1ms
npm timing config:load:flatten Completed in 2ms
npm timing npm:load:display Completed in 5ms
npm timing npm:load:logFile Completed in 3ms
npm timing npm:load:timers Completed in 0ms
npm timing npm:load:configScope Completed in 0ms
npm timing npm:load Completed in 24ms

> epgg@53.8.0 start
> react-app-rewired start

ℹ 「wds」: Project is running at http://172.31.177.72/n 24ms
ℹ 「wds」: webpack output is served from /browser
ℹ 「wds」: Content not from webpack is served from /var/www/html/eg_test/eg-react-master/frontend/public
ℹ 「wds」: 404s will fallback to /browser/

Starting the development server...

Browserslist: caniuse-lite is outdated. Please run:in 24ms
npx browserslist@latest --update-db

Why you should do it regularly:
https://github.com/browserslist/browserslist#browsers-data-updating
npm timing command:run-script Completed in 37307ms
npm timing command:start Completed in 37310ms
npm timing npm Completed in 37338ms
npm info ok 

My npm version is 8.11.0, nodejs version is v16.16.0, and operating system CentOS Linux release 8.4.2105.

I searched this for two days but did not get any clue. I wonder if you could give some hints?

Thanks.

Chen Tong

lidaof commented 2 years ago

Hi @Tong-Chen what happens if you not use -d with npm start?

Tong-Chen commented 2 years ago

Thanks!

Running npm start would generate the following logs and exit. I added -d to check if there is some useful logs.

> epgg@53.8.0 start
> react-app-rewired start

ℹ 「wds」: Project is running at http://172.31.177.72/n 24ms
ℹ 「wds」: webpack output is served from /browser
ℹ 「wds」: Content not from webpack is served from /var/www/html/eg_test/eg-react-master/frontend/public
ℹ 「wds」: 404s will fallback to /browser/

Starting the development server...

Browserslist: caniuse-lite is outdated. Please run:in 24ms
npx browserslist@latest --update-db

Why you should do it regularly:
https://github.com/browserslist/browserslist#browsers-data-updating

Also I tried the command npm build, and got

> epgg@53.8.0 build
> react-app-rewired build

Creating an optimized production build...
Browserslist: caniuse-lite is outdated. Please run:
npx browserslist@latest --update-db

Why you should do it regularly:
https://github.com/browserslist/browserslist#browsers-data-updating
The build failed because the process exited too early. Someone might have called `kill` or `killall`, or the system could be shutting down.

My working computer has 16 G memory. I use top to watch the process and the node process only consumes less than 10% memory.

lidaof commented 2 years ago

Hi @Tong-Chen your computer is fine, I don't think it's a computer issue. I did test nodejs the version you used in Mac, which works fine...I need to find a machine with centos and do some troubleshooting...

can you delete your current eg-react folder, do:

git clone https://github.com/lidaof/eg-react.git
cd eg-react/frontend
npm install
npm start

also check here: https://eg.readthedocs.io/en/latest/installation.html#example-commands-for-installation-on-a-rhel-system

Tong-Chen commented 2 years ago

I cloned eg-react in a new folder, and run npm install in frontend.

The first tiem I get

npm WARN   node_modules/@storybook/core
npm WARN
npm WARN Conflicting peer dependency: webpack@3.12.0
npm WARN node_modules/webpack
npm WARN   peer webpack@"^1.0.0 || ^2.0.0 || ^3.0.0" from webpack-dev-middleware@1.12.2
npm WARN   node_modules/webpack-dev-middleware
npm WARN     webpack-dev-middleware@"^1.12.2" from @storybook/core@3.4.12
npm WARN     node_modules/@storybook/core
npm WARN deprecated left-pad@1.3.0: use String.prototype.padStart()
npm WARN deprecated tar@2.2.2: This version of tar is no longer supported, and will not receive security updates. Please upgrade asap.
npm ERR! process terminated
npm ERR! signal SIGTERM

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/ct/.npm/_logs/2022-07-27T04_15_30_250Z-debug-0.log

Then I run npm install again and got

npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: html-webpack-plugin@2.30.1
npm WARN Found: webpack@4.42.0
npm WARN node_modules/webpack
npm WARN   dev webpack@"^4.42.0" from the root project
npm WARN   21 more (babel-loader, dotenv-webpack, eslint-loader, ...)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer webpack@"1 || ^2 || ^2.1.0-beta || ^2.2.0-rc || ^3" from html-webpack-plugin@2.30.1
npm WARN node_modules/html-webpack-plugin
npm WARN   html-webpack-plugin@"^2.30.1" from @storybook/react@3.4.12
npm WARN   node_modules/@storybook/react
npm WARN
npm WARN Conflicting peer dependency: webpack@3.12.0
npm WARN node_modules/webpack
npm WARN   peer webpack@"1 || ^2 || ^2.1.0-beta || ^2.2.0-rc || ^3" from html-webpack-plugin@2.30.1
npm WARN   node_modules/html-webpack-plugin
npm WARN     html-webpack-plugin@"^2.30.1" from @storybook/react@3.4.12
npm WARN     node_modules/@storybook/react
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: webpack-dev-middleware@1.12.2
npm WARN Found: webpack@4.42.0
npm WARN node_modules/webpack
npm WARN   dev webpack@"^4.42.0" from the root project
npm WARN   21 more (babel-loader, dotenv-webpack, eslint-loader, ...)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer webpack@"^1.0.0 || ^2.0.0 || ^3.0.0" from webpack-dev-middleware@1.12.2
npm WARN node_modules/webpack-dev-middleware
npm WARN   webpack-dev-middleware@"^1.12.2" from @storybook/core@3.4.12
npm WARN   node_modules/@storybook/core
npm WARN
npm WARN Conflicting peer dependency: webpack@3.12.0
npm WARN node_modules/webpack
npm WARN   peer webpack@"^1.0.0 || ^2.0.0 || ^3.0.0" from webpack-dev-middleware@1.12.2
npm WARN   node_modules/webpack-dev-middleware
npm WARN     webpack-dev-middleware@"^1.12.2" from @storybook/core@3.4.12
npm WARN     node_modules/@storybook/core
已终止

It seems like npm start has been killed. I am looking for the reasons.

lidaof commented 2 years ago

Hi, @Tong-Chen any luck in getting it working? I guess maybe we can schedule a time to do a zoom meeting to get this fixed? How do you think?

Tong-Chen commented 2 years ago

Sorry, I still have no idea to get it to work. I would be very thankful if we can schedule a time for a zoom meeting. Currently, there are 12 hours of jet lag from China, Beijing, and Washington DC. I am ok from 8 am to 9 pm (Beijing time). My Wechat id: ct5869. Thanks.

lidaof commented 2 years ago

Hi @Tong-Chen , great! Does Beijing time 11AM Saturday works for you?

Tong-Chen commented 2 years ago

That works for me! Thanks!

Tong-Chen commented 2 years ago

Sorry. I tried Zoom and found I could not use Zoom in China. Could you mind using Tencent Meeting or others?

lidaof commented 2 years ago

Hi @Tong-Chen I will add you wechat and figure it out together.

lidaof commented 2 years ago

Hi @Tong-Chen just like to follow up on this issue. I tested on our RHEL linux virtual server with node v16 and npm v8, which works fine.

$ node -v
v16.16.0
$ npm -v
8.11.0
$ cat /etc/redhat-release 
Red Hat Enterprise Linux Server release 7.9 (Maipo)
lidaof commented 1 year ago

close for now, feel free to open new issue. thank you!