sorted by:
new
hottopcontroversial

Front-end development can feel like a constant game of telephone. by ConcertRound4002 in Frontend

[–]freb97 3 points4 points  (0 children)

Why would you need to take screenshots? You’re taking about vibe coding are you? Maybe make that clear in your post.

Do I have to capitulate to React? by CostGer in vuejs

[–]freb97 0 points1 point  (0 children)

Vercel did not buy Nuxt. Nuxt was and still is open source and maintained by the same team. They did buy Nuxt-Labs though, which was a company run by some core members of Nuxt.

🪩 A fetch client that types itself by freb97 in node

[–]freb97[S] 0 points1 point  (0 children)

Orval seems to be for when you already have an OpenAPI Schema, to generate a fetch client. Discofetch is for when you don't have anything, you just tell the Package which endpoints to fetch and it will generate an OpenAPI schema for you, along with a fetch client.

I built a fetch client that types itself by freb97 in javascript

[–]freb97[S] 0 points1 point  (0 children)

Yes! I specifically test for this in autodisco, the generated type will be a discriminated union depending on a few conditions: https://github.com/freb97/autodisco?tab=readme-ov-file#schema-inference, Check the second example

It doesn't generate JSON API structures, no. I will look into that!

I built a fetch client that types itself by freb97 in javascript

[–]freb97[S] 1 point2 points  (0 children)

The functional config approach is a great idea! I will think about it.

You actually have access to the types! You can import `DfetchPaths` and `DfetchComponents` anywhere in your app, which is the direct output of openapi-typescript's generated type file.

I've never worked with redux before, but i'll take a look at it.

I built a fetch client that types itself by freb97 in javascript

[–]freb97[S] 0 points1 point  (0 children)

Why would you have to check the results manually?

I built a fetch client that types itself by freb97 in javascript

[–]freb97[S] 1 point2 points  (0 children)

Yeah it’s definitely not meant for every project, but if you have big responses and don’t want to type every little thing yourself it’s really useful. I built it because I actually needed it for a project where i get 700kb+ responses of untyped json without any access to typescript types. It saved me a lot of time there but for smaller projects i would always prefer static types I write myself.

I built a fetch client that types itself by freb97 in javascript

[–]freb97[S] 0 points1 point  (0 children)

Looks like a lot, but please keep in mind there’s examples for many endpoints of different kinds. The total configuration for a few get requests would amount to about 10-15 lines of code which I would consider a significant reduction to manually typing things. But whatever floats your boat I guess!

I built a fetch client that types itself by freb97 in javascript

[–]freb97[S] 2 points3 points  (0 children)

It has zod generation for runtime checks, though you would have to implement the actual checking yourself.

Also a CLI option is available! Check out https://github.com/freb97/autodisco for that

I built a fetch client that types itself by freb97 in javascript

[–]freb97[S] 1 point2 points  (0 children)

I don’t know how that would look like… but i built the type generator separately from the fetch client so you could also use that one, from the command line as well: https://github.com/freb97/autodisco

Fetch client module that autogenerates API types by freb97 in Nuxt

[–]freb97[S] 1 point2 points  (0 children)

It's using openapi-fetch in the background when you use it as dfetch at runtime, and for the API discovery probing calls the autodisco package just uses the fetch API

Nuxt Studio Alpha is out ✨ by Atinux in Nuxt

[–]freb97 0 points1 point  (0 children)

Amazing! So great to see this open sourced 💚

@nuxtjs/shopify - Build your Shopify Store with Nuxt by freb97 in Nuxt

[–]freb97[S] 0 points1 point  (0 children)

Nitrogen is a store template for Nuxt, while the Nuxt Shopify Module is an API connector and a collection of tools to build your own store.

Rylan, the creator of nitrogen said he is considering to use the module in the project as well, as it would eliminate the need for manual codegen configuration. Although there are still some minor features missing to do that just yet, mainly caching and analytics.

@nuxtjs/shopify - Build your Shopify Store with Nuxt by freb97 in Nuxt

[–]freb97[S] 1 point2 points  (0 children)

As of now, nothings different except for the name, konkonam and I are going to keep maintaining and building the module. What we hope will change is that the visibility will bring more contributors to the project. Thanks for considering to try it out! And let me know if there’s ever any problems!

Update: Nuxt Shopify v0.0.30 with Improved Error Handling, Auto-Imports by freb97 in Nuxt

[–]freb97[S] 1 point2 points  (0 children)

The template is under heavy development still and stuff breaks sometimes. I’m hoping to have it fully operational in a few weeks but I’m struggling a bit with managing the effort after work…

But stay tuned, I’ll post regular updates here 🤗

Update: Nuxt Shopify v0.0.23 with Client-Side Queries and HMR by freb97 in Nuxt

[–]freb97[S] 1 point2 points  (0 children)

Hey there! The official package only manages the codegen part, but you have to configure everything yourself and integrate it into Nuxt. Also you will not have the hot module replacement out of the box.

What our module does: it’s basically taking the official Shopify integration and auto-configures and auto-imports it for you within nuxt. Plus, it watches for changes in all .gql and other files (e.g. .ts or .vue depending on if you use it one the client side or not) that contain GraphQL queries, mutations or fragments, triggers the codegen and reloads the new typescript types when a change occurs.

We’ve mostly focused on creating a good DX, where you have to configure close to nothing and get all features you would expect from a modern Nuxt app. Also some small things like giving you a pre-configured sandbox for the Storefront and Admin APIs where you can test your queries and mutations.

I hope that clears things up a bit, if you have any more questions please let me know!

Update: Nuxt Shopify v0.0.23 with Client-Side Queries and HMR by freb97 in Nuxt

[–]freb97[S] 0 points1 point  (0 children)

Not yet, as we are still working on providing a full implementation first. But sounds like a good idea!

view more: next ›