\n\n const googleMapsApiKey = process.env.NUXT_GOOGLE_MAPS_API_KEY;\n\n\nbut this doesnt work? When i use my api key directly in the file it works. But putting it in the .env i wont load the map? I thought placing your api key is not secure? Already asked chatgpt but no solution. \n\n\n\n### 🔍 What have you tried?\n\nI looked at the docs. Nothing about it. I tried chatgpt and different solutions nothing works. \n\n### ℹ️ Additional context\n\n_No response_",[1984],{"name":1985,"color":1986},"documentation","0075ca",313,"nuxt","scripts","open","Using the googlemaps api key?","2024-11-11T03:54:14Z","https://github.com/nuxt/scripts/issues/313",0.72997856,{"description":1996,"labels":1997,"number":2001,"owner":1988,"repository":1989,"state":1990,"title":2002,"updated_at":2003,"url":2004,"score":2005},"### 🆒 Your use case\n\nFor server-side tagging a custom src needs to be set for Google Tag Manager.\n\nCurrently this src is hard coded in: https://github.com/nuxt/scripts/blob/f96f7b51549f302160559041bbf056589e899b04/src/runtime/registry/google-tag-manager.ts#L47\n\nWhenever we want to change the src manually the ID is no longer appended, make it so we have to define the ID twice.\n\n```\ngoogleTagManager: {\n\tid: 'GTM-123456',\n\tscriptInput: {\n\t\tsrc: 'https://gtm.example.com/gtm.js?id=GTM-123456',\n\t},\n},\n```\n\n### 🆕 The solution you'd like\n\n\nA simple solution to the problem could be to add an option for the src.\n\n`src: withQuery(options?.src || 'https://www.googletagmanager.com/gtm.js', { id: options?.id, l: options?.l }),`\n\nWhich makes it so we can easily change it like so:\n\n```\ngoogleTagManager: {\n\tid: 'GTM-123456',\n\tsrc: 'https://gtm.example.com/gtm.js'\n},\n```\n\n### 🔍 Alternatives you've considered\n\n_No response_\n\n### ℹ️ Additional info\n\n_No response_",[1998],{"name":1999,"color":2000},"enhancement","a2eeef",404,"Allow changing the Google Tag Manager script src","2025-03-19T16:20:34Z","https://github.com/nuxt/scripts/issues/404",0.7496567,{"description":2007,"labels":2008,"number":2017,"owner":1988,"repository":1988,"state":1990,"title":2018,"updated_at":2019,"url":2020,"score":2021},"### Describe the feature\n\nThis request is for the implementation of a `renderPage()` method capable of calling the internal prerender process of Nuxt to render, not just normal pages, but those with dynamic slugs. \r\nI believe this feature would prove significant for blogs, and various static sites to control the re-rendering of specific pages upon update to their respective data. \r\n\r\n```ts\r\nexport default defineEventHandler(async (event)=>{\r\n await renderPage('/posts/24', { query1: 'mostLiked' });\r\n});\r\n```\r\n\r\nThe previous way of adding prerenderable slugs below results in the the need to rebuild to get fresh new routes/slugs:\r\n\r\n```ts\r\nimport { ofetch } from 'ofetch';\r\n\r\nconst getPlanetsRoutes = async () => {\r\n const response = await ofetch(\"https://api.nuxtjs.dev/planets\");\r\n return response.map((planet) => `/planets/${planet.slug}`);\r\n}\r\n\r\nexport default defineNuxtConfig({\r\n hooks: {\r\n async 'nitro:config'(nitroConfig) {\r\n const planetsRoutes = await getPlanetsRoutes();\r\n nitroConfig.prerender.routes.push(...planetsRoutes);\r\n }\r\n }\r\n});\r\n```\r\n\r\nThis feature request prevents the need for unnecessary rebuild and allows re-rendering to occur server-side. This will improve flexibility and ease as anyone could cache a page based on data/[slug title] gotten from a database. \r\nDevelopers will be able to delete pages that are no longer needed (maybe after deletion of data from a store) using `removePage(route)`.\r\n\r\n*The feature would be added only for users with the prerender feature enabled on at least one route, so as to avoid rendering conflicts with a full SSR app rendering mechanism*\n\n### Additional information\n\n- [X] Would you be willing to help implement this feature?\n- [ ] Could this feature be implemented as a module?\n\n### Final checks\n\n- [X] Read the [contribution guide](https://nuxt.com/docs/community/contribution).\n- [x] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[2009,2011,2014],{"name":1999,"color":2010},"8DEF37",{"name":2012,"color":2013},"discussion","538de2",{"name":2015,"color":2016},"nitro","bfd4f2",27058,"A page re-rendering and page deletion composable","2024-06-30T11:04:12Z","https://github.com/nuxt/nuxt/issues/27058",0.7515989,{"description":2023,"labels":2024,"number":2028,"owner":1988,"repository":2029,"state":2030,"title":2031,"updated_at":2032,"url":2033,"score":2034},"Hey 👋 \r\n\r\nI would love to see `@testing-library/vue` support be added. E.g. a `renderSuspended` utility or something like this, which would use `render` from testing library instead of `mount` from VTU.\r\n\r\nI've tinkered with creating this and it seems to be a case of mostly adding an extra root element to the existing code of `mountSuspended` to make this work.",[2025],{"name":2026,"color":2027},"vitest-environment","b60205",545,"test-utils","closed","Support rendering with Testing Library","2023-12-02T00:17:10Z","https://github.com/nuxt/test-utils/issues/545",0.4567044,{"description":2036,"labels":2037,"number":2040,"owner":1988,"repository":2041,"state":2030,"title":2042,"updated_at":2043,"url":2044,"score":2045},"",[2038],{"name":1999,"color":2039},"1ad6ff",387,"nuxt.com","`/resources` page should redirect to `/resources/blog`","2022-04-22T11:12:32Z","https://github.com/nuxt/nuxt.com/issues/387",0.6532857,{"description":2047,"labels":2048,"number":2040,"owner":1988,"repository":2029,"state":2030,"title":2049,"updated_at":2050,"url":2051,"score":2045},"in [module testing docs](https://test-utils.nuxtjs.org/api-reference/module-testing) page It only shows the following options:\r\n- `addPlugin`\r\n- `addLayout` \r\n- `addErrorLayout`\r\n- `addServerMiddleware` \r\n- `requireModule`\r\n\r\nBut the `addModule` option is not documented although it can be used!",[],"Module testing page is missing the \"addModule\" option","2023-12-02T00:13:09Z","https://github.com/nuxt/test-utils/issues/387",{"description":2036,"labels":2053,"number":2054,"owner":1988,"repository":2041,"state":2030,"title":2055,"updated_at":2056,"url":2057,"score":2058},[],986,"[Blog] Article layout","2022-12-07T06:16:35Z","https://github.com/nuxt/nuxt.com/issues/986",0.70706224,{"description":2060,"labels":2061,"number":2054,"owner":1988,"repository":2029,"state":2030,"title":2065,"updated_at":2066,"url":2067,"score":2058},"### Environment\n\n------------------------------\n- Operating System: Linux\n- Node Version: v20.10.0\n- Nuxt Version: 3.13.2\n- CLI Version: 3.14.0\n- Nitro Version: -\n- Package Manager: pnpm@8.12.1\n- Builder: -\n- User Config: -\n- Runtime Modules: -\n- Build Modules: -\n------------------------------\n\n### Reproduction\n\nI've written tests for this here: https://github.com/nuxt/test-utils/compare/main...oskarols:test-utils:fix-unusable-props\n\nMy `@nuxt/test-utils` branch: https://github.com/oskarols/test-utils/tree/fix-unusable-props\n\n### Describe the bug\n\nHi! 👋 \n\nWe're trying to upgrade from `3.10.0` and ran into some issues. \n\nUsing `renderSuspended` or `mountSuspended` together with certain prop names will throw an error and fail the test. This is the case for props named `error` and `url` for instance. \n\nThis is the error received:\n```\nTypeError: 'set' on proxy: trap returned falsish for property 'url' 3:04:05 PM\n ❯ Proxy.clonedComponent.render ../../src/runtime-utils/mount.ts:131:48 3:04:05 PM\n129| } 3:04:05 PM\n130| for (const key in props || {}) {\n131| renderContext[key] = _ctx[key]\n | ^\n132| }\n133| for (const key in passedProps || {}) {\n❯ renderComponentRoot ../../node_modules/.pnpm/@vue+runtime-core@3.5.12/node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:6408:16\n❯ ReactiveEffect.componentUpdateFn [as fn] ../../node_modules/.pnpm/@vue+runtime-core@3.5.12/node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:5225:46\n❯ ReactiveEffect.run ../../node_modules/.pnpm/@vue+reactivity@3.5.12/node_modules/@vue/reactivity/dist/reactivity.cjs.js:226:19\n❯ setupRenderEffect ../../node_modules/.pnpm/@vue+runtime-core@3.5.12/node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:5360:5\n❯ ../../node_modules/.pnpm/@vue+runtime-core@3.5.12/node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:7107:9\n```\n\nI've done some triaging and `renderSuspended` regresses between `v13.13.1` and `v13.14.0`. Likely culprit: #852 \n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2062],{"name":2063,"color":2064},"pending triage","5D08F5","Some prop names break component testing","2024-12-03T21:18:45Z","https://github.com/nuxt/test-utils/issues/986",{"description":2036,"labels":2069,"number":1987,"owner":1988,"repository":2041,"state":2030,"title":2071,"updated_at":2072,"url":2073,"score":1994},[2070],{"name":1999,"color":2039},"Refactor blog index with markdown only","2023-02-15T12:30:44Z","https://github.com/nuxt/nuxt.com/issues/313",{"description":2036,"labels":2075,"number":2077,"owner":1988,"repository":2041,"state":2030,"title":2078,"updated_at":2079,"url":2080,"score":2081},[2076],{"name":1999,"color":2039},359,"Fetch components from project url `/api/component-meta`","2022-04-19T13:51:35Z","https://github.com/nuxt/nuxt.com/issues/359",0.74268705,["Reactive",2083],{},["Set"],["ShallowReactive",2086],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"IadydFzgsXyKr_GFBwWQuKx1kBmUcxyyMaleIu-NS64":-1},"/nuxt/nuxt.com/545"]