-
-
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
[Bug]: embla-carousel-docs
gatsby build errors in Windows 10
#662
Comments
Im getting a similar issue when running Here the error
and my pc info is
|
@TheMikeyRoss Our OS are basically identical except mine is Windows 10 Pro and not Home The error is likely coming from |
@TheMikeyRoss as @zaaakher mentioned everything is working as expected on Unix based environments. @zaaakher @TheMikeyRoss thanks for the information. You could try changing the gatsby version (like one or two patch versions) and run It will take some time for me to get hold of a Windows machine to debug this. Best, |
Hi @davidjerleke, I was trying to change the gatsby version but I noticed in I've never seen something like this before (especially that it works fine in unix-based env), could you educate me about how that works? |
I hope I'm understanding your question correctly because I'm not 100% sure where the confusion lies:
I don't think there's anything strange with that.
Maybe it won't and something else is causing this problem but since the Best, |
Omg what a brain fart that was from me. For some reason my brain kept processing it as 5.13 is less than 5.5 🤦♂️ I definitely need to take a break 😅 My apologies for taking up your time @davidjerleke I will test out your suggestion when I get around it inshallah 👍 |
Ok so I upgraded gatsby to the following versions:
And each time I ran the commands And just for good measure I went back to gatsby I think this is a good sign, it seems all gatsby versions |
@zaaakher thank you for your efforts! That’s helpful 👍🏻. It seems to be related to graphql that gatsby is using now. You might get a more detailed error message if you run I will also start debugging this as soon as I get hold of a Windows machine. |
@davidjerleke Using gatsby but when I visit the site in |
Take your time, no rush, no pressure. 👍 I'm just trying to get closer to the source of the error so that it's easier for you to solve once you get around it |
embla-carousel-docs
gatsby build errors in Windows 10embla-carousel-docs
gatsby build errors in Windows 10
@zaaakher an interesting find: I was running through dependabot PR:s and there's a Gatsby PR that's failing: When I tried that PR branch locally, I got the exact same error as you shared here, but on Maybe debatable, but I guess we can call this some progress of sort if |
@zaaakher I solved the problem on OSX. Would you mind try building on Windows again? This is the commit that might solve the problem. Steps:
Regardless if you try this or not, thanks! Best, |
Hey @davidjerleke ,
I've been quite busy lately and now looking back to this error I'm just thankful it's from the docs and not the actual consumable package. So the only people who'd face it are developers trying to contribute to the docs while in Windows 😅 UpdateSo I decided to delete the file mentioned in the error message (
And at this point it kept pointing at a different mdx/md file every time the build fails so I'm pretty sure the cause is not the content of these mdx/md files but rather the way it's being built. |
@zaaakher thank you for your additional efforts! And please, if I tag you in an issue, no strings attached. Just answer if you want to help out and if you have time. I think we’re making progress even though we haven’t solved this yet, because at least both you and @TheMikeyRoss are getting the same errors now! The build problem on OSX was related to a simple syntax thing. Both the syntax that threw the error and the syntax that fixed it are actually valid, but for some reason
Anyway, thanks a ton! Best, |
Ideas: ERROR #95313 HTML.COMPILATION |
Hi @davidjerleke, I've had this in my tasks list for a while I was planning to eventually get to it but today I decided to take a jab at it and 2 hours later and I've got nothing to show for 😅 I played around in Which Isn't very helpful I think it just prevents gatsby from building the pages alltogether. So I played around with
And after running For a second I thought maybe this whole windows-only issue we have here could be from the fact that the path slashes is different in each operating system and using This issue is definitely unique to Windows |
@zaaakher thank you very much for being so persistent 😄! I finally got hold of a PC with Windows 10 installed yesterday. I gave it 4 good hours last night and have to say that the error messages make no sense at all. Judging by the behaviour, I think the error messages are not highlighting what's actually going wrong in the code, but they're rather symptoms of something else. I activated the gatsby SSR flag for debugging while testing. This is what I did (to no avail):
Agreed. This is working just as expected on ❓ Moving forwardUnfortunately, this is so typical for Gatsby. I don't know how many hours I've totally spent on debugging error messages that make no sense and didn't point me to the real error, just to try random stuff until finally finding the culprit. It's sad to say the least. I'm considering creating a minimal reproduction repository and creating a bug report for the gatsby plugin Thank you for your efforts @zaaakher! Let me know if you try something else regardless if it solves the problem or not. Best, |
Hi @davidjerleke thanks for the update, I'm honestly relieved you're in the same boat as us now that you've seen the error yourself 😅 I was worried it's too edgy of an edge-case that only I and @TheMikeyRoss encountered. I've never used gatsby before, and for a while i've been seeing some online rumors that gatsby is on the verge of dying with only a single developer maintaining it. And ever since, I've been hesitant to bring that up to you along with a suggestion to migrate to Astro. But I've checked on Gatsby recently and the repository is active and there's still hope for it to stay around for a little longer. As a busy man myself I understand how it feels to work on something that's not profitable and that's why I didn't want to bring up Astro to you or the mere idea of migrating the docs to another framework, which feels quite unnecessary especially that the docs currently looks absolutely great and nothing is wrong with it (except for this issue I guess 🫥). I kinda feel guilty for wasting your time and mine on an issue that doesn't even effect the packages itself. I have a macbook so I can contribute to the docs with no issue at anytime. And at this point I'd suggest to @TheMikeyRoss and potential docs-contributors (on Windows) to create an issue addressing any fixes or additions to the docs so we can take care of it. @davidjerleke to prevent other developers on windows from falling into the same 10+ collective hours of debugging nightmare we've been through here, I'd suggest we add a note to the documentation section in |
Hi @zaaakher,
Don’t. I know that your intention is to help out and I appreciate that. As I said in my previous comment:
I think I’m done with Gatsby to be honest. I’ve spent crazy amounts of time debugging just to realize the error messages have nothing to do with the real problem. This happens every time I upgrade Gatsby and its plugins. I can’t afford to spend more time on this. I’ve actually considered alternatives back in time. For example, I’ve seriously considered migrating to Docusaurus. But it doesn’t support using Styled Components which I use throughout the project so the migration would be insanely time consuming. Additionally, the flexibility Styled Components has is necessary for the automatic CodeSandbox generation process for all the examples. Any changes made in the documentation example styles will instantly be reflected on the generated sandboxes on the examples page. This is great because this means no manual maintenance. And if it’s one thing I’ve learned from maintaining this library myself is that automation is key if I’m to have time over to build new features, examples and improving the docs. Alternatives
Best, |
Hi @davidjerleke, I also haven't used Astro before but I'm planning to learn it since it's becoming the go-to for static sites and a lot of people recommended it to me, Although the Astro path I'm planning to learn is CMS-based rather than MDX-based. I've only recommended Astro because I've seen a lot of open-source projects use Astro for their MDX-based documentation. However, I'd definitely recommend NextJS, It's my favorite framework. Although there's an on-going debate regarding the pages vs. app routers (the biggest con of the pages router is that it will eventually be deprecated 😅). In the documentation of my UI kit I used the same nextjs docs setup used by shadcn/ui here. Although they're using contentlayer which unfortunately seems to be unmaintained at this point in time. There's also Nextra, which is easy to setup and get started with the MDX side of things. But I worry it might start causing you trouble when you go deeper and try to customize things that could potentially conflict with Nextra. Note: Nextra is currently working on v3 here (related PR) So expect breaking changes when they upgrade to v3. The best course of action at this point might be to start a fresh next.js project, unless you have another plan in mind. In all cases, let me know if you need any help. Best of luck brother 👍 |
Bug is related to
Embla Carousel version
v8.0.0-rc15
Describe the bug
yarn build
in a windows 10 machine throws 3 errors in a row originating from gatsby in theembla-carousel-docs
package. The 3 errors are mentioned hereCodeSandbox
N/A
Steps to reproduce
yarn install
in the root directoryyarn build
in the root directoryExpected behavior
The gatsby docs should build without an errors so that you can run
yarn start
afterwards to see the documentation site inlocalhost:8000
Additional context
node version:
v18.19.0
npm version:
v10.2.3
yarn version:
v3.3.1
I only get this error in my Windows 10 (Build 19045.3086).
This issue does not exist in unix-based environments.
The text was updated successfully, but these errors were encountered: