Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

facing issue while running the code #231

Open
Dhivakar19 opened this issue Jun 2, 2022 · 13 comments
Open

facing issue while running the code #231

Dhivakar19 opened this issue Jun 2, 2022 · 13 comments

Comments

@Dhivakar19
Copy link

Dhivakar19 commented Jun 2, 2022

issue

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

@LunaticMuch
Copy link
Collaborator

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

@Dhivakar19
Copy link
Author

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

@LunaticMuch
Copy link
Collaborator

@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   

> [email protected] 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.

@Dhivakar19
Copy link
Author

Dhivakar19 commented Jun 3, 2022

node-v
npm start

npm version

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

@LunaticMuch
Copy link
Collaborator

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

@Dhivakar19
Copy link
Author

https://github.com/Dhivakar19/gqlpoc

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

@LunaticMuch
Copy link
Collaborator

LunaticMuch commented Jun 3, 2022

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.

@Dhivakar19
Copy link
Author

main
mainissue

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

@LunaticMuch
Copy link
Collaborator

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

@Dhivakar19
Copy link
Author

kindly guide me to overcome from this issue ..

@Dhivakar19
Copy link
Author

node1 0
node1 1

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

@Dhivakar19
Copy link
Author

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

voyagerSteps.txt

@Dhivakar19
Copy link
Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants