Mick Lawitzke
Mick Lawitzke
I am still having the same issue, I am on latest @nuxtjs/seo, unhead `1.9.16`. Both me and @jfern01 reported this issue in july, I dont think it has been fixed....
Currently Nuxt Image only supports transforming images **outside** of Cloudflare Images, see: https://developers.cloudflare.com/images/transform-images/ I agree that the naming is very confusing! There is an open feature request to support Cloudflare...
I think it is the same naming without `$` from i18n instance. I use Nuxt so I do: ``` const { n } = useI18n(); n(100, 'currency'); ``` I assume...
Yes it is. But regarding your issue: You will not import it from vue-18n because it is from nuxt-i18n. But it is already auto imported. My guess is you didnt...
Use `@nuxtjs/i18n` instead, it is pretty awesome!
As a workaround I use `@egjs/grid` directly, instead of `@egjs/vue-grid`: ```vue import { FrameGrid } from '@egjs/grid'; const containerRef = ref(); onMounted(() => { const grid = new FrameGrid(containerRef.value, {...
I have no problem making a differntiation between dev and prod. I want to set cors origin to a specific URL instead of accepting all origins. For example in Express...
I was just wondering if this actually needs to be done within H3?
Just to note a **workaround** for now: Cors cant be configured by `nitro.config.ts` (what this issue is about), but it can be configured by use of a middleware, e.g. here...
Are you running a Vite project? Because I think there is no more `.nitro` folder. With the path option it works for my TypeScript / IDE but Vite doesnt catch...