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

Issue with Generating GraphQL Types on Windows 11 #936

Closed
yuriassuncx opened this issue Oct 16, 2024 · 2 comments
Closed

Issue with Generating GraphQL Types on Windows 11 #936

yuriassuncx opened this issue Oct 16, 2024 · 2 comments
Labels

Comments

@yuriassuncx
Copy link
Contributor

Issue Type

  • Bug Report

Description:

I am encountering issues while trying to generate GraphQL types using Deno on my Windows 11 Pro system. Below are the steps I've followed and the errors I received:

  1. Running Task:

    • Command: deno task start
    • Output includes:
      Generating GraphQL types for specs at shopify\utils\admin
      Error generating GraphQL types: Failed to find any GraphQL type definitions in: **/*.ts;
      - EINVAL: invalid argument, stat
      
    • This indicates that the program could not find any TypeScript files matching the pattern **/*.ts.
  2. File Check:

    • I verified that TypeScript files do exist in the specified directories:
      • C:\Users\Yuri\Desktop\coding\apps\shopify\utils\admin\queries.ts
      • C:\Users\Yuri\Desktop\coding\apps\shopify\utils\storefront\queries.ts
      • C:\Users\Yuri\Desktop\coding\apps\wake\utils\graphql\queries.ts
  3. Deno Version:

    • I am using the latest version of Deno.
  4. Error Message:

    • The errors consistently mention EINVAL: invalid argument, stat.

Expected Behavior:
I expect the GraphQL types to be generated without any issues when the files exist in the specified directories.

Environment:

  • OS: Windows 11 Pro

image

Additional Information:
I have tried running the commands in both CMD and Git Bash, and the problem persists across both environments.

@luanargolodev
Copy link
Contributor

This is some incompatibility with powershell/windows.

Using WSL2 solves the problem.

@yuriassuncx
Copy link
Contributor Author

Fixed issue when using WSL on Windows

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

No branches or pull requests

2 participants