-
-
Notifications
You must be signed in to change notification settings - Fork 193
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
Add docs section in CONTRIBUTING.md #657
Conversation
I based the changes I made on the comment you made here But it seems when I do I tried running @davidjerleke Are there additional steps I should follow to successfully run the docs locally? |
@zaaakher thank you for your contribution. This is a great start. You’re right. After I’ve updated the steps in the comment you linked to. Best, |
@davidjerleke Thanks for the update, I tried running (I'm running node v18.17.0) Error 1Error 2Error 3 |
@zaaakher thanks for the additional details.
It's highly recommended to use I definitely think that one of the steps in this guide should be the Best, |
@davidjerleke Thank you for your time, My apologies I thought it'd work even if my node version is higher than the one stated in Nevertheless I switched to node I'm on windows 10 btw. I'm gonna add a note to |
@zaaakher thanks for the screen recording. That's very strange 😕. Because this project uses GitHub actions and they don't fail when setting it up. They run every time I push something to the repository or merge a PR. It seems like the GitHub actions use a different node version though: Which version of yarn are you using? Best, |
I matched all versions to the github action environment and deleted all and I'm still getting the same error when I run Btw everytime I run And the change seems to be adding a space between each line for some reason |
@zaaakher can you try running yarn start from the root and see if you get a better error message on your terminal? Because the error messages don’t tell much right now. |
I couldn't get the docs to run locally no matter how hard I tried. and I spent too much time on it today 😅 I wish it ran smoothly so I can work better on #658 however I made that PR as a starting point and I'll try to improve on it more inshallah |
@zaaakher thank you for your time. I appreciate it. To be honest the error you get doesn't seem to be related to any Embla package because they don't call Another thing you could try:
Thanks for your efforts. |
Thanks for testing @zaaakher. As I mentioned I have a Unix system which is different from Windows so I will try on a Windows machine when I get the chance and let you know how it goes. |
I just tested it on a Macbook Pro and everything worked extremely well without a single error 😄. So now i'm 100% sure it's a gatspy/window issue originating from |
@davidjerleke I followed the instructions in this new docs section of If you'd like, I can create an issue addressing the gatspy/windows-10 build errors so that it can be dealt with separately without having to dig through the thread in this PR. Thanks, |
@zaaakher I think that’s a great idea! I will be away for 3-4 days and won’t have access to my computer but when I’m back I will rebase and review this PR. There might be a thing or two I want to add before merging. Or maybe not. Regardless, thank you for your efforts! It’s refreshing to see someone not just coming here pointing out missing things, but actually makes an effort to improve things for a change 👍🏻! |
@davidjerleke You're welcome brother 👍, I'm glad I could help and I appreciate the work you do and the wonderful library you made ✨ |
Added a section in the CONTRIBUTING.md file to guide people on how to run the docs locally
1fd81dd
to
b4986db
Compare
Thanks @zaaakher! This is now merged. |
Added a
documentation
section in the CONTRIBUTING.md file to guide people on how to run the docs locally to hopefully streamline the process of updating the docs when needed.