` they dont get applied. Instead a warning is shown in the console:\r\n\r\n> Google Maps JavaScript API: A Map's styles property cannot be set when a mapId is present. When a mapId is present, Map styles are controlled via the cloud console.\r\n\r\nI did not set any mapId.",[3066],{"name":3067,"color":3068},"bug","d73a4a","scripts","Google Maps: Cant add styles to options","2024-09-03T16:45:09Z","https://github.com/nuxt/scripts/issues/202",{"labels":3074,"number":3080,"owner":3021,"repository":3021,"state":3058,"title":3081,"updated_at":3082,"url":3083,"score":3084},[3075,3077],{"name":3054,"color":3076},"8DEF37",{"name":3078,"color":3079},"2.x","d4c5f9",10156,"Clarify use of Vuex typing of module","2023-02-15T00:40:52Z","https://github.com/nuxt/nuxt/issues/10156",0.74499685,{"description":3086,"labels":3087,"number":3088,"owner":3021,"repository":3089,"state":3058,"title":3090,"updated_at":3091,"url":3092,"score":3093},"Tailwind v4 moves configuration into CSS instead of `tailwind.config.js`. https://tailwindcss.com/blog/tailwindcss-v4-alpha\r\n\r\nFor example in v4 to specify a custom font, you'd just do this and then you can use `.font-display` within your HTML. (example from their blog post)\r\n```css\r\n/* main.css */\r\n@import \"tailwindcss\";\r\n\r\n@theme {\r\n --font-family-display: \"Satoshi\", \"sans-serif\";\r\n}\r\n```\r\n### Workaround\r\n\r\nCurrently the workaround to use Tailwind CSS v4 with Nuxt Fonts is simply to specify using `font-family` in the CSS so it's loaded in.\r\n```css\r\n@import \"tailwindcss\";\r\n\r\n@theme {\r\n --font-family-marker: \"Permanent Marker\", cursive;\r\n}\r\n\r\n.nuxt-fonts-permanent-marker {\r\n font-family: \"Permanent Marker\", cursive;\r\n}\r\n```",[],132,"fonts","Support Tailwind CSS v4","2024-04-22T09:11:12Z","https://github.com/nuxt/fonts/issues/132",0.74693424,{"description":3095,"labels":3096,"number":3099,"owner":3021,"repository":3021,"state":3058,"title":3100,"updated_at":3101,"url":3102,"score":3103},"Hello guys. I've opened this one trying to help making upgrade progress faster. Feel free closing if you are internally working on this. Following list is according to [2.3.0 release notes ](https://github.com/vuejs/vue/tree/v2.3.0) and [new dedicated Vue SSR guide](https://ssr.vuejs.org).\r\n\r\n- [x] Allow [runInNewContext](https://ssr.vuejs.org/en/api.html#runinnewcontext) option. which can bring huge performance improvement in production.\r\n- [x] `vue-ssr-webpack-plugin` is deprecated. ([webpack plugins](https://ssr.vuejs.org/en/api.html#webpack-plugins))\r\n- [x] [Generating clientManifest](https://ssr.vuejs.org/en/build-config.html#generating-clientmanifest)\r\n- [x] ~~Vue 2.3.x broke middleware in dev #636~~ (seems working)\r\n- [x] Duplicate assets in client manifest entry point\r\n- [x] CI Fails with infinity wait with new vue-loader (12.x)\r\n- [x] [server side directives](https://ssr.vuejs.org/en/api.html#directives)\r\n- [x] New [CSS Management](https://ssr.vuejs.org/en/css.html)\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This feature request is available on \u003Ca href=\"https://nuxtjs.cmty.io\">Nuxt.js\u003C/a> community (\u003Ca href=\"https://nuxtjs.cmty.io/nuxt/nuxt.js/issues/c548\">#c548\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[3097,3098],{"name":3054,"color":3076},{"name":3078,"color":3079},632,"⚡️ Upgrade to Vue 2.3.x ","2023-01-18T15:39:38Z","https://github.com/nuxt/nuxt/issues/632",0.7475012,{"description":3105,"labels":3106,"number":3114,"owner":3021,"repository":3021,"state":3058,"title":3115,"updated_at":3116,"url":3117,"score":3118},"### Environment\r\n\r\n- Operating System: Darwin\r\n- Node Version: v20.11.0\r\n- Nuxt Version: 3.10.2\r\n- CLI Version: 3.10.1\r\n- Nitro Version: 2.8.1\r\n- Package Manager: npm@10.2.4\r\n- Builder: -\r\n- User Config: `devServer`, `nitro`, `routeRules`, `components`, `build`, `modules`, `primevue`, `experimental`, `typescript`, `devtools`\r\n- Runtime Modules: `@vueuse/nuxt@10.8.0`, `nuxt-svgo@4.0.0`, `nuxt-primevue@0.3.0`, `@nuxt/image@1.3.0`, `@pinia/nuxt@0.5.1`\r\n- Build Modules: -\r\n\r\n### Reproduction\r\n\r\n✅ `3.9.3`: https://stackblitz.com/edit/nuxt-3-9-3-typecheck \r\n❌ `3.10.3`: https://stackblitz.com/edit/nuxt-3-10-typecheck \r\n\r\n### Describe the bug\r\n\r\nAfter upgrading Nuxt from `v3.9.3` to `v3.10.2` some typings are not detected anymore. It looks like it's related to third-party packages with `exports` config in the `package.json`. I discovered that `moduleResolution` has been changed in the automatically generated `tsconfig.json` file.\r\n\r\n### Additional context\r\n\r\nSetting `moduleResolution` as `Node` should fix the problem. In the Nuxt `3.10` it was changed to `Bundler`, which looks like a breaking change in some cases.\r\n\r\nIn our case, we have a multifile/multitype package that stopped working during type-checking (the build is okay). I tried to set `moduleResolution` to `Node` back in Nuxt 3.10 and it seems like the type-checking issue has been fixed.\r\n\r\n```json5\r\n{\r\n // https://nuxt.com/docs/guide/concepts/typescript\r\n \"extends\": \"./.nuxt/tsconfig.json\",\r\n\r\n \"compilerOptions\": {\r\n \"moduleResolution\": \"Node\"\r\n }\r\n}\r\n```\r\n\r\n#25230 can be related, but I'm unsure because the Nuxt version there is `3.9`.\r\n\r\n### Logs\r\n\r\n_No response_",[3107,3110,3113],{"name":3108,"color":3109},"types","2875C3",{"name":3111,"color":3112},"3.x","29bc7f",{"name":3032,"color":3044},25929,"Typechecking issue after Nuxt upgrading 3.9 -> 3.10","2024-03-08T11:49:58Z","https://github.com/nuxt/nuxt/issues/25929",0.7541257,{"labels":3120,"number":3123,"owner":3021,"repository":3021,"state":3058,"title":3124,"updated_at":3125,"url":3126,"score":3127},[3121,3122],{"name":3032,"color":3044},{"name":3078,"color":3079},8452,"v12.14.10 is breaking existing projects","2023-01-22T15:38:24Z","https://github.com/nuxt/nuxt/issues/8452",0.7546421,["Reactive",3129],{},["Set"],["ShallowReactive",3132],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$faC5T-VyDnvqETcWSGlvlaKRmWbhKmfHwuaR-AMT7ghs":-1},"/nuxt/nuxt.com/1006"]