Devesh Sharma

    Devesh Sharma

    9 months ago
    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.
    Pranay

    Pranay

    9 months ago
    @User is your man 🙂
    Palash Gupta

    Palash Gupta

    9 months ago
    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..
    Devesh Sharma

    Devesh Sharma

    9 months ago
    Hey @User answers to your question1. 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"
    Palash Gupta

    Palash Gupta

    9 months ago
    @User please pull the latest changes.. this issue is already fixed
    also just one query why do we need
    win-node-env
    in windows ?
    Devesh Kumar

    Devesh Kumar

    9 months ago
    Hey @User it's @User I guess u wanted to tag. We have the same first name.
    Palash Gupta

    Palash Gupta

    9 months ago
    My bad 😅
    please pull the latest changes
    Devesh Kumar

    Devesh Kumar

    9 months ago
    Also @User I think that the issue is fixed but the PR is not merged yethttps://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
    Palash Gupta

    Palash Gupta

    9 months ago
    i see
    We will fix this one in upcoming release cc: @User
    Devesh Sharma

    Devesh Sharma

    9 months ago
    Hey @User and @User thanks to both of you...after pulling the latest changes everything is running perfectly now...
    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...