facing issue while running the code

[Dhivakar]

postcss-cssnext npm is deprecated and postcss-variables-loader has dependency on postcss-cssnext . so kinldy check this

[Stefano]

I can look into this @Dhivakar19
@IvanGoncharov have you seen this already? I should check in my other repo, but I remember I sorted it while moving to webpack5

[Dhivakar]

@LunaticMuch kindly take the latest from git and npm install and npm start u will face the n-number of issue ..

[Stefano]

@LunaticMuch kindly take the latest from git and npm install and npm start u will face the n-number of issue ..

I actually face no issue. Two points:

1. I see you're on windows, there might something specific on your environment
2. You should use npm ci as packages-lock.json is included and this will include all specific versions.
3. You might want to share the version of node and npm you are using and the complete stack of your npm ci and npm run start command.

➜  graphql-voyager git:(main) npm run start   

> graphql-voyager@1.0.0-rc.31 start
> webpack-dev-server --config webpack-demo.config.js --hot --inline --mode=development

(node:22006) [DEP0111] DeprecationWarning: Access to process.binding('http_parser') is deprecated.
(Use `node --trace-deprecation ...` to show where the warning was created)
ℹ ｢wds｣: Project is running at http://localhost:9090/
ℹ ｢wds｣: webpack output is served from /
ℹ ｢wds｣: Content not from webpack is served from /Users/stefano/_GITHUB/graphql-voyager/demo
ℹ ｢wdm｣: Compiled successfully.

[Dhivakar]

i tried as you said .. but still have the same issue..

[Stefano]

Also, is your clone updated? Additional updates were approved in the last 24 hours.

[Dhivakar]

https://github.com/Dhivakar19/gqlpoc

kindly take the code from this file not able to resolve it ..

[Stefano]

Not sure what you're trying to do. Your code is not based on the latest commit in main and also includes broken dependencies.
I can probably help with debugging a voyager trouble, but this is not voyager.
You should make a fresh clone, use node 18 as set in the node-version file and then retry.
We can file a big if the official version published in this repo does not work, but we can't file a bug because your customized version does not work. Hope you can understand.

Regarding dependencies, it's true something is old, but they are still supported in the current configuration. Update to webpack5 requires the update of several other packages. I did it on my local and I will eventually submit for review in the next days. Although, so far, this does not appear to be root cause.

[Dhivakar]

i cloned the latest one and i did the same process still getting the same error

[Stefano]

I see. Will see whether upgrading webpack and postcss can solve.
Currently it does not reproduce anywhere else; it is probably related to windows only and to browserify

[Dhivakar]

kindly guide me to overcome from this issue ..

[Dhivakar]

after upgraded the node to 18.3.0. facing issue in latest code .

[Dhivakar]

The Steps i followed is mentioned in attachment .Kindly go through and help us to resolve

voyagerSteps.txt

[Dhivakar]

we tried on mac too with node version of 18.3.0. got the same error