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

Getting a schema generate issue when I command npm run generate #576

Closed
sachinnawale99 opened this issue Oct 13, 2021 · 6 comments
Closed

Comments

@sachinnawale99
Copy link

sachinnawale99 commented Oct 13, 2021

Screenshot 2021-10-12 at 4 31 27 PM
Hello Everyone, I'm having a schema generate issue when I command npm run generate. That's the reason I am not able to see my custom fields. Is that any way to solve this error? Thanks

@theodesp
Copy link
Member

@sachinnawale99 did you copied the sample environment template?

cp .env.local.sample .env.local

If not then the NEXT_PUBLIC_WORDPRESS_URL env variable will be undefined here:

endpoint: `${process.env.NEXT_PUBLIC_WORDPRESS_URL}/graphql`,

@JPOak
Copy link

JPOak commented Oct 18, 2021

I'm getting this error as well when doing a walkthrough of the tutorial found here: https://faustjs.org/docs/tutorial/setup-faustjs

I did indeed follow what it says about setting up the .env.local file and my development site URL (LocalWP) and my secret code. Is there any error in the documentation for this step? It was going smooth until this point.

Thanks

@trust96
Copy link

trust96 commented Oct 27, 2021

i had the same issue. what help was installing dotenv-flow:
npm i dotenv-flow -D
then inside gqty.config.js
require("dotenv-flow").config();

@vaihtovirtahepo
Copy link

You can also rename .env.local to .env and that will fix the problem.

@blakewilson
Copy link
Contributor

@sachinnawale99 👋

We've smoothed over a few issues in the tutorail/getting started. The latest changes should now fix this.

@blakewilson
Copy link
Contributor

This should be resolved now on the Faust.js/docs side. However, if anyone is still experiencing this, please feel free to open a new issue

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

6 participants