How to register Inertia 1.x as a plugin during tests (Jest or Vitest)? #1683
Replies: 1 comment 4 replies
-
|
Have you found a solution to this? Amazing how it's been 5 months and nothing from the developers. |
Beta Was this translation helpful? Give feedback.
-
Honestly, comments like these make contributing to an OSS package less and less fun and feeling like an actual burden, as if everything you want is up to others to fix. Maybe the maintainers don't use Vitepress/Jest (which is kinda obvious, as testing within Inertia itself is done with cypress, at least for the Vue 2 adapter; https://github.com/inertiajs/inertia/tree/master/packages/vue2/tests), so it would make sense that it hasn't been investigated, since there's not a lot of gain for the maintainers while needing to maintain it. |
Beta Was this translation helpful? Give feedback.
-
|
@malssid I just stopped trying to use @RobertBoes I get where he is coming from, Inertia is a 1st-party package on the Laravel ecosystem, but it doesn't get enough attention as it's mostly "feature-complete" but still lacks a lot of the high quality work that goes into the Laravel brand. However, I do perceive this not only as a core developers issue, but rather as a community issue. The adoption of Inertia seems to be growing, but the amount of community content is still very small. We're still lacking content creators that talk about the high quality Laravel content around automation testing, components best practice designed for Inertia, Typescript, IDE tips, etc. I take some of that blame myself because it's been 5 months and now I am in position of writing a little bit more about Inertia, but I've been so swamped at work because of my decision to use Inertia that I'm still buried in a slow development cycle that I need to catch up before I can take some time to produce content. |
Beta Was this translation helpful? Give feedback.
-
|
Hey @RobertBoes, I didn't mean to come off rude. I agree with what @deleugpn said about the missing pieces being a community issue rather than a core developers issue. We've been using Inertia over here for about 5 months and I'll run into issues where the Inertia documentation doesn't explain how to do something, so I'm stuck with stack overflow, chatgpt, laracasts, etc. For example, mocking Inertia components wasn't clear (I've figured it out) and there doesn't seem to be a way to register Inertia as a plugin globally. |
Beta Was this translation helpful? Give feedback.
-
|
Has anyone had any progress this? As far as I can tell, the design of Inertia makes testing using Vitest (the official Vue testing library) impossible.
To be honest, I disagree. This isn't a minor issue that's making it hard. Digging around the source of both Inertia and |
Beta Was this translation helpful? Give feedback.
-
I'm getting the following error:
This started happening because I put
<Head>on my Vue component:This is my test:
Most content that I found online refers to Inertia 0.x, where it was possible to do:
But as we can see on the upgrade guide, this is now gone: https://inertiajs.com/upgrade-guide#renamed-imports
So, to my original question: how can I register inertia as a plugin the same way I register
piniaorfont-awesomein Vitest/Jest in Inertia 1.x?Beta Was this translation helpful? Give feedback.
All reactions