-
-
Notifications
You must be signed in to change notification settings - Fork 120
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
pnpm i fails #68
Comments
Hey there! I need a bit more info to get a clearer picture of what's going on. Could you tell me which pnpm version you're using? Also, it would be super helpful if you could walk me through what you did step by step, or even better, if you could recreate the issue for me. And don't forget to mention whether you're on Windows, Linux, or something else. I'm thinking there might be a problem with your API key permissions (as it stands, there is a problem with permission on the Directus end). Have you double-checked that the user in Directus has all the right privileges? And make sure you hit 'save' after setting up your API key, it's an easy thing to miss. |
I am experiencing the same challenge |
Same here. There's a lot of things broken in this repo. Also my API token is saved and correct.
|
The error you're seeing is not an pnpm issue. After running The error you're seeing is coming from the Directus module included in template. The module tries to fetch redirects from the Directus instance. And it doesn't appear to be able to reach the Directus instance. |
I have the same issue. I used Postman to check if the RestAPI of my Directus instance and the admin's Bearer token were working correctly. I found everything normal, but |
Same as well |
Did you add your DIRECTUS_URL to the .env file? If so, and you are sure the .ENV file is correct - I'd look at the CORS settings for your Directus config. |
@bryantgillespie where can i find those settings more precisely? |
Here's the specific link to the CORS config. |
Thanks @bryantgillespie |
As long as Due to this leaving it closed as resolved for now, happy to re-open if this is still an issue after the above 2 things have been verified to not be the cause. |
thanks @ComfortablyCoding. This fix seems to help. however now getting other errors: [Vue warn]: Property "title" was accessed during render but is not defined on instance. Tried removing globals: { title }, from TheHeader.vue and return appConfig.globals.logo_on_dark_bg; Not sure whether anyone has tried and succeeded running this template in it's current state. |
Glad to hear it helped! The merged PR was primarily to mitigate a crash/error on install, the underlying issue is generally due to a misconfiguration. Happy to look into this further if this is not the case for you.
I will look into this case when I have the chance. I would assume some global is required but missing due to the failed request. I am thinking the ideal path here is to either add default values for globals or revert back to the error state on failure. At the moment leaning toward adding back the error. Generally the globals and redirect requests fail due to the following:
If in your case it is not one of these 3 happy to debug further in the directus discord, my handle is the same as here. EDIT: Optional access was added as a temporary fix in #99
I don't encounter this issue on my side unless one of the issues mentioned above are present. As this is a community maintained repo PRs are always welcome for any issues/improvements. |
Directus is hosted on DigitalOcean through Cloudron...everything works fine on that end
The text was updated successfully, but these errors were encountered: