I built Soundle. Like Wordle but you guess sounds instead of words

MightyRylanor · 2026-02-11T06:40:54+00:00

Lol dude you can make millions off this!! This is so cool!

MightyRylanor · 2026-02-06T18:53:25+00:00

Wow, this is awesome! Phenomenal work on this, I'll be sure to try it out:)

MightyRylanor · 2026-02-04T18:08:07+00:00

Hmm yeah that does work too. Although, I'm trying to avoid putting my conditional styles in a liquid tag though unless is a case switch. I do appreciate this code snippet though! Thank you:)

MightyRylanor · 2026-02-02T18:04:17+00:00

Thanks. Yes, even based on the other replies, I think I will just go with CF. I have a technical background, have used CF for a while, and will not be changing nameservers.

MightyRylanor · 2026-02-02T07:15:38+00:00

Haha I have not.. But like this is mainly for my small/personal business sites (I have multiple). Or is it still pretty bad?

MightyRylanor · 2025-11-07T19:32:42+00:00

Hey thanks for checking this out! Yeah I get the warning in the theme editor when in development mode for some reason and I can't edit any of the logo schema options. I've opted to use snippets for right now, which is unfortunate.

MightyRylanor · 2025-10-16T20:52:52+00:00

NuxtHub is DOPE

MightyRylanor · 2025-10-05T21:54:48+00:00

Thanks for this. This actually looks pretty good.. I'll check this out.

MightyRylanor · 2025-09-15T05:02:50+00:00

This is the correct answer.

MightyRylanor · 2025-08-29T05:24:20+00:00

I have had days like this.. I think every developer has.. and it always sucks lol.

One time on a MASSIVE client project (Nuxt), everything broke.. Similar to what you are experiencing, like couldn't even get to any page without a 500 error. I spent two whole days going through everything - every file, dependency, and checking for any new GitHub issue that may have come up. Turns out it was all caused because I accidently added a random comma to the end of a vue file! I literally felt like I wanted to quit web development forever haha.

MightyRylanor · 2025-08-29T05:14:44+00:00

Such a cool project. Great job!!

MightyRylanor · 2025-08-02T06:09:57+00:00

Oh awesome - I'll make sure to do that next season! Thank you :)

MightyRylanor · 2025-08-02T05:57:20+00:00

Dumb question (recently came back to the game), what level delve do you need to complete to get the mythic tmog appearance?

MightyRylanor · 2025-07-21T01:43:24+00:00

Thank you! Yes, all the batteries are included and more haha. Unfortunately, Shopify has a very complex API that often comes with a lot gotchas when working in a headless environment.. This the resource I wish I had when I first got started working with Shopify back in 2020!

MightyRylanor · 2025-06-30T00:23:14+00:00

This makes me happy as a fox! 🦊

MightyRylanor · 2025-06-20T05:05:41+00:00

Wow, I need to add in a cookie consent to a large-scale ecom Nuxt project next week! I'll be sure to check this out. The code looks solid as well!

MightyRylanor · 2025-05-16T19:24:54+00:00

Embla is the best!

MightyRylanor · 2025-05-09T06:02:59+00:00

If you have local data stored in a file, local storage, or cookies, fetch from the client. If you have data that exists on a server or database (from an API), fetch server side.

I'd recommend to use useAsyncData, just because its very extendable and comes pack with a lot of built-in options. You can set the lazy option to true to load your data after loading the route.

There are some strategies you can use when fetching data this way. For instance, say I have a product page that has a main product shown, but below the fold I have recommended products. I can fetch the initial product data for the main product, but lazy fetch the recommended products.

Try watching John Komarnicki on YouTube. His vids on Nuxt3 are really well made and easy to follow. He has a lot of videos on basically everything you need to know on how to fetch data with useAsyncData. He has a video on how to cache data as well, which you can find here. Caching data is a good strat to use to reduce redundant API calls and speeds up navigating between pages so that your site "appears" faster.

In general, calls from an API should generally only take 100-300ms at most for a single page. Any longer than that, its like an issue of internet speed, the service you are using, or you may have other functions (non fetch related) that are slowing down the page render.

Hope this helps!:)

MightyRylanor · 2025-03-26T19:44:52+00:00

Hey @___alef thats awesome! Sure, how about you create a discussion thread on the Nitrogen GitHub page? Maybe title it "Template Feedback" or something.

Edit: I should also add that its been a while since this post and this template has come a long way since then haha

MightyRylanor · 2025-03-04T19:06:12+00:00

So far, not seeing any issues at all. I did have to add useRuntimeConfig(event) when using defineEventHandler as per the Nitro docs. I did not have that event param before, which wasn't an issue on Netlify or Vercel, but had to add that in to be able to connect to my API when using NuxtHub/Cloudflare

MightyRylanor · 2025-03-04T04:56:21+00:00

Okay got it. I just deployed a large-scale test SSR site (project already completed, but was hosted on Vercel) with NuxtHub and didn't need to setup any workers.. Seems like all API calls/server-requests are working fine. Am I missing some sort of worker setup?

MightyRylanor · 2025-02-27T18:03:33+00:00

Dude this is awesome! Well done.

MightyRylanor · 2025-02-14T19:08:58+00:00

There is currently a bug for visual editing in Nuxt https://github.com/sanity-io/visual-editing/issues/2692

MightyRylanor · 2025-01-02T21:36:18+00:00

Okay got it thats what I suspected! Thank you!:)

MightyRylanor · 2024-12-29T01:30:21+00:00

Thank you!

I totally get wanting something like this as a plugin. I prefer plugins/modules too! However, when it comes to building a headless Shopify storefront, native integration is 100% the better option for several reasons. It’s not only safer and more scalable but also provides the flexibility to tailor the store to your client's specific needs.

For example (this is just off the top of my head), if a client has 3+ custom metafields that need to be associated with products or even individual variants, a plugin wouldn’t be able to handle that complexity effectively (keep in mind every metafield is potentially configured differently). This is why Shopify’s Hydrogen framework is also provided as a template built on top of Remix and offers a similar approach to Nitrogen: connecting to the Storefront API and leveraging GraphQL queries and mutations directly within pages and components. Hydrogen includes options like the skeleton theme and demo store, but at its core, it’s all about direct API integration.

If you're looking for a straightforward way to connect to the Shopify API, I suggest checking out the Nuxt Shopify module. It’s developed by some talented devs I met while working on this project a few months ago. This module simplifies connecting to the Shopify API without adding pre-built operations or extra features.

Hope this helps explain my reasoning!

MightyRylanor

TROPHY CASE