[Feature] Nuxt Compatibility via Alternative Request Handling

[TimoCuijpers]

Feature Suggestion: Nuxt Compatibility via Alternative Request Handling

Hi,

I'm planning to create a Nuxt-compatible version of this package (js-junction) because currently it isn't possible to use it directly in Nuxt projects. The current implementation relies on Axios for HTTP requests, which isn't fully compatible with Nuxt's recommended request handling mechanisms.

Reasoning:

• Current Incompatibility: js-junction relies on Axios, which doesn't align well with Nuxt's standard request handling approach (useFetch, useAsyncData). As a result, developers currently can't leverage js-junction effectively within Nuxt environments.
• Optimized Integration: Using Nuxt composables instead of Axios ensures seamless integration with Nuxt’s built-in SSR features, performance optimizations, and automatic data handling.
• Integration with nuxt-sanctum: By developing compatibility with nuxt-sanctum, we can ensure smooth and secure authentication workflows tailored specifically for Nuxt.

Proposed Solution:

• Develop a separate Nuxt-specific implementation of js-junction.
• Replace Axios with Nuxt composables like useFetch.
• Ensure compatibility with nuxt-sanctum for secure, streamlined authentication.

I welcome feedback or suggestions regarding this direction!

[robinvda]

We're not looking to get tied to a framework like Nuxt. You could create some kind of "connector" between js-junction and Nuxt. I'm not familiar with Nuxt, but i assume you can use axios and useFetch at the same time.

[TimoCuijpers]

Nuxt 3 no longer directly supports Axios due to its new data-fetching approach using built-in composables (useFetch, useAsyncData).

Therefore, creating a dedicated Nuxt 3 connector is necessary to bridge this compatibility gap. My goal is precisely to ensure js-junction works smoothly within Nuxt 3’s ecosystem without affecting the core of your package.

I’ll proceed with developing this connector and will keep you updated!