Colby Fayock

We'll (Cloudinary) surely defer to the Nuxt preference. The idea behind using the loader that I linked is that by updating the dependency new features would "just work" as things...

thanks everyone just an FYI one potential option is to still use the `url-loader` for both instances in the event that it makes maintaining the logic easier something to consider...

Option 2 has a better DX. Devs shouldn't necessarily have to care or think about the example in option 1. It's also confusing.

the easier method would be to use the same options in the loader but that would certainly be breaking i defer to what you and @pi0 think about that one

hey @vanling there's 2 ways you can chain transformations right now, though it might not be exactly what you want the effects prop supports an array, but only a limited...

i noticed this happening to myself in dev mode only in a library i'm working on: https://github.com/cloudinary-community/next-cloudinary/blob/main/next-cloudinary/src/components/CldImage/CldImage.tsx#L156 its not as much of a concern because it seems to only be...

thanks @romanskorobagatko - good idea! do you have any Raycast flows you've really liked with that regard? considering things like confirming you want to delete, before you delete the asset?...

opened a ticket over on the actual repository for this as well https://github.com/colbyfayock/raycast-cloudinary/issues/10

Will be pulling this in with #477

I noticed the same thing, i was just trying to test it on a random twitch stream to get a script working. my error code at the bottom (Assuming its...