https://signoz.io logo
Title
d

Devesh Sharma

12/18/2021, 1:31 PM
Hello @User @User can anyone of you help me with this issue . https://github.com/SigNoz/signoz/issues/360 initially I was on nodejs version 16.3 but even after switching to node version 14.18.1 I am getting the same error.
p

Pranay

12/18/2021, 1:32 PM
@User is your man 🙂
👍 1
p

Palash Gupta

12/20/2021, 3:36 AM
Hi @User There are couple of questions 1. Which OS you are using 2. what is the node version (try using node -v) 3. Did you try removing the node_modules and then try again running the server 4. what is the Signoz Version you are running 5. Are you running Only frontend or via install.sh
let know this one..
d

Devesh Sharma

12/20/2021, 3:52 PM
Hey @User answers to your question 1. window 10 2. node version 14.18.1 3. yes 4. package.json in frontend folder mentions version 1.0.0 5. yes I am running only frontend got same issue after deleting node module and running yarn install again. attaching a pic for your reference. also one more question do we need to pass some argument while running "yarn dev"
p

Palash Gupta

12/21/2021, 5:03 AM
@User please pull the latest changes.. this issue is already fixed
also just one query why do we need
win-node-env
in windows ?
d

Devesh Kumar

12/21/2021, 8:00 AM
Hey @User it's @User I guess u wanted to tag. We have the same first name.
p

Palash Gupta

12/21/2021, 8:04 AM
My bad 😅
please pull the latest changes
d

Devesh Kumar

12/21/2021, 8:04 AM
Also @User I think that the issue is fixed but the PR is not merged yet https://github.com/SigNoz/signoz/pull/485 but @User changing dev in package.json under scripts section as the below one (by adding a &)
"dev": "NODE_ENV=development & webpack serve --progress",
solved the issue for windows
p

Palash Gupta

12/21/2021, 8:04 AM
i see
We will fix this one in upcoming release cc: @User
d

Devesh Sharma

12/21/2021, 5:18 PM
Hey @User and @User thanks to both of you...after pulling the latest changes everything is running perfectly now...
1
Also @User I was getting the error "Node_env is not recognised" issue so, after little bit of searching I came across win-node-env and installed it globally then the error was resolved...after seeing your reply I uninstalled it and the took a SS for your reference...I don't really know the correct reason for why I was getting this error...