\n \u003CUModal v-model=\"isOpen\" :fullscreen=\"fullscreen\">\n \u003Cdiv class=\"p-4\">\n \u003CUButton label=\"Toggle fullscreen\" @click=\"toggleFullscreen\" />\n \u003C/div>\n \u003C/UModal>\n \u003C/div>\n\u003C/template>\n```\n\n### Description\n\nStarting from [2.18.6](https://github.com/nuxt/ui/releases/tag/v2.18.6) @nuxt/ui version, Modal component become transparent when toggle `fullscreen` property. It seems something wrong with transitions css classes in UI props.\n\n**Expected behavior:**\n1. open Modal with `fullscreen=false`\n2. set `fullscreen=true`, Modal fills all viewport\n3. set `fullscreen=false`, Modal become small again\n\n**On 2.18.5 works as expected.** \n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[1984,1987],{"name":1985,"color":1986},"bug","d73a4a",{"name":1988,"color":1989},"triage","ffffff",3292,"nuxt","ui","open","Modal component fullscreen property toggle cause invalid css transition","2025-02-11T20:14:53Z","https://github.com/nuxt/ui/issues/3292",0.67615366,{"description":1999,"labels":2000,"number":2001,"owner":1991,"repository":2002,"state":1993,"title":2003,"updated_at":2004,"url":2005,"score":2006},"https://stackblitz.com/edit/nuxt-icon-playground-frxmrw4y\n\nIcons not displayed",[],368,"icon","Not shows with new Nuxt 3.16.0","2025-03-13T12:52:04Z","https://github.com/nuxt/icon/issues/368",0.7244925,{"description":2008,"labels":2009,"number":2016,"owner":1991,"repository":1992,"state":1993,"title":2017,"updated_at":2018,"url":2019,"score":2020},"### Description\n\nHello,\nAny events fired when month or year is changed? Are there any events emitted?\nCouldnt find anything in the docs\n\nthanks.",[2010,2013],{"name":2011,"color":2012},"question","d876e3",{"name":2014,"color":2015},"v3","49DCB8",3593,"Calendar : Month / Year Emits","2025-03-21T18:11:05Z","https://github.com/nuxt/ui/issues/3593",0.73730147,{"description":2022,"labels":2023,"number":2027,"owner":1991,"repository":2028,"state":1993,"title":2029,"updated_at":2030,"url":2031,"score":2032},"From my testings, only weights `400` (normal) and `700` (bold) are available out of the box by using the `@nuxtjs/tailwindcss` module like this:\r\n\r\n```html\r\n\u003Cspan class=\"font-roboto\">...\u003C/span> \u003C!-- Works -->\r\n\r\n\u003Cspan class=\"font-roboto font-bold\">...\u003C/span> \u003C!-- Works -->\r\n\r\n\u003Cspan class=\"font-roboto font-medium\">...\u003C/span> \u003C!-- Doesn't work -->\r\n```\r\n\r\n> `font-roboto` is defined in tailwind.config.\r\n\r\nAm I missing something, or do I do have to specify the other weights in the module options?",[2024],{"name":2025,"color":2026},"enhancement","a2eeef",209,"fonts","detect font weights automatically","2024-11-24T15:36:51Z","https://github.com/nuxt/fonts/issues/209",0.7383877,{"description":2034,"labels":2035,"number":2046,"owner":1991,"repository":1991,"state":1993,"title":2047,"updated_at":2048,"url":2049,"score":2050},"### Environment\n\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v18.20.3\r\n- Nuxt Version: 3.12.4\r\n- CLI Version: 3.12.0\r\n- Nitro Version: 2.9.7\r\n- Package Manager: npm@10.2.3\r\n- Builder: -\r\n- User Config: compatibilityDate, devtools, runtimeConfig\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-bzhg2m\n\n### Describe the bug\n\nModify `.env` file will trigger dev server restart:\r\n```\r\nℹ .env changed, restarting server... \r\n```\r\n\r\nBut what is returned by `useRuntimeConfig` does not change.\r\n\r\nYou can modify the `.env` file in the reproduction. What rendered in HTML remains the same.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2036,2039,2040,2043],{"name":2037,"color":2038},"good first issue","fbca04",{"name":1985,"color":1986},{"name":2041,"color":2042},"nitro","bfd4f2",{"name":2044,"color":2045},"🔨 p3-minor","FBCA04",28543,"Change .env file does not update runtimeConfig","2024-08-29T09:51:36Z","https://github.com/nuxt/nuxt/issues/28543",0.74489224,{"description":2052,"labels":2053,"number":2057,"owner":1991,"repository":1992,"state":2058,"title":2059,"updated_at":2060,"url":2061,"score":2062},"### Environment\n\n------------------------------\n- Operating System: Linux\n- Node Version: v20.9.0\n- Nuxt Version: 3.15.4\n- CLI Version: 3.22.3\n- Nitro Version: 2.10.4\n- Package Manager: pnpm@8.10.2\n- Builder: -\n- User Config: devtools, vite, modules, css, compatibilityDate\n- Runtime Modules: @nuxt/ui@3.0.0-beta.2\n- Build Modules: -\n------------------------------\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.15.4\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/pmvsfw\n\n### Description\n\n```\ndeclare function _useOverlay(): {\n overlays: import(\"vue\").ShallowReactive\u003COverlay[]>;\n open: \u003CT extends Component>(id: symbol, props?: ComponentProps\u003CT>) => Promise\u003Cany>;\n close: (id: symbol, value?: any) => void;\n create: \u003CT extends Component>(component: T, _options?: OverlayOptions\u003CComponentProps\u003CT>>) => OverlayInstance\u003CT>;\n patch: \u003CT extends Component>(id: symbol, props: Partial\u003CComponentProps\u003CT>>) => void;\n unMount: (id: symbol) => void;\n};\n```\ne.g:\n```\nconst overlay = useOverlay()\noverlay.create(UModal, { props: {untyped} })\n```\n\nI didn't get the correct props type when using useOverlay, and there are no property hints when passing overlay.open or the open function after create\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2054,2055,2056],{"name":1985,"color":1986},{"name":2014,"color":2015},{"name":1988,"color":1989},3436,"closed","useOverlay props type lost","2025-03-28T21:05:02Z","https://github.com/nuxt/ui/issues/3436",0.681056,{"description":2064,"labels":2065,"number":2071,"owner":1991,"repository":1991,"state":2058,"title":2072,"updated_at":2073,"url":2074,"score":2075},"Hey!\r\n\r\n## Description\r\n\r\nI'm currently trying to set several config parameters depending on whether nuxt.js is launched in dev or production mode. To accomplish this, I haven't changed any environment variables before starting nuxt.\r\nUnfortunately, the following won't work (using the axios module) by default:\r\n\r\n```\r\n /*\r\n * Axios\r\n */\r\n axios: {\r\n baseURL: process.env.NODE_ENV !== 'production' ? 'http://api.xyz.test' : 'https://api.xyz.com'\r\n },\r\n```\r\n\r\nIf I use `console.log(process.env.NODE_ENV)` in the `nuxt.config.js` file, it's undefined (if not set before)\r\n\r\n## Current possible solution\r\n\r\nI only came up with one solution for it:\r\n\r\n### Set env variables before starting\r\n\r\nWe could update the package.json scripts to include NODE_ENV or set it manually through the console.\r\nThe former blocks \"overriding\" ENV through the command line, the latter is quite tedious.\r\n```\r\n\"scripts\": {\r\n \"dev\": \"NODE_ENV=development nuxt\",\r\n \"build\": \"NODE_ENV=production nuxt build\",\r\n \"start\": \"NODE_ENV=production nuxt start\",\r\n \"generate\": \"NODE_ENV=production nuxt generate\", \r\n },\r\n```\r\n\r\n### Use dotenv module\r\n\r\nAlso a way to deal with it, and highly customizable. Still, there should be an easier way to define the \"default\" configuration which would be enough in many use-cases.\r\n\r\n## Other solutions?\r\n\r\nAre there better ways to accomplish similar behavior easier?\r\n\r\nBy default, NODE_ENV is set depending on the nuxt mode (`nuxt dev` = development, production otherwise), but I guess this happens after interpreting the config.\r\n\r\nCould we use `extend()` for it? :thinking: \r\n\r\n## Related\r\nhttps://github.com/nuxt/nuxt.js/blob/dev/lib/builder/webpack/server.config.js#L50\r\nhttps://github.com/nuxt/nuxt.js/issues/1386\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This bug report is available on \u003Ca href=\"https://nuxtjs.cmty.io\">Nuxt.js\u003C/a> community (\u003Ca href=\"https://nuxtjs.cmty.io/nuxt/nuxt.js/issues/c2598\">#c2598\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2066,2068],{"name":2011,"color":2067},"cc317c",{"name":2069,"color":2070},"2.x","d4c5f9",2998,"Use environment variables inside nuxt.config.js","2023-01-18T16:09:50Z","https://github.com/nuxt/nuxt/issues/2998",0.71894324,{"description":2077,"labels":2078,"number":2081,"owner":1991,"repository":1991,"state":2058,"title":2082,"updated_at":2083,"url":2084,"score":2085},"Hello !\r\n\r\nFrom the doc, there is a way to set environment variables using the `config.env` key. However, I see one problem here :\r\n\r\nEnvironment variables should not be committed to version control (Git / SVN...). They can be different between environment (local development, continuous integration, production...), and placing them inside the whole project configuration makes it difficult / impossible to maintain. I would have to remember before each commit to remove the environment variables. 😅\r\n\r\nWhat I'm suggesting is following practices already in place : `.env` files.\r\n\r\nEnvironment variables should be defined in here, not in the configuration file anymore. That way, this file could be omitted from version control, and everything would be separated between environments. Of course, the developer would have to think to create the `.env` file on every machine he uses, but that's a small trade-off in my opinion.\r\n\r\nWhat do you think ? Did you already though about it and decided not to implement it ?\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This question is available on \u003Ca href=\"https://nuxtjs.cmty.io\">Nuxt.js\u003C/a> community (\u003Ca href=\"https://nuxtjs.cmty.io/nuxt/nuxt.js/issues/c513\">#c513\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2079,2080],{"name":2011,"color":2067},{"name":2069,"color":2070},586,"Allow .env files to set environment variables","2023-01-18T15:39:32Z","https://github.com/nuxt/nuxt/issues/586",0.719183,{"description":2087,"labels":2088,"number":2096,"owner":1991,"repository":1991,"state":2058,"title":2097,"updated_at":2098,"url":2099,"score":2100},"### Environment\r\n\r\n- Operating System: `Darwin`\r\n- Node Version: `v20.1.0`\r\n- Nuxt Version: `3.6.5`\r\n- Nitro Version: `2.5.2`\r\n- Package Manager: `pnpm@8.6.6`\r\n- Builder: `vite`\r\n- User Config: `devtools`, `runtimeConfig`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n\r\n\r\n### Reproduction\r\n\r\n1. Clone https://github.com/xuzuodong/nuxt-source-test \r\n2. run `pnpm i`\r\n3. run `pnpm dev`, open `localhost:3000`, and then console will print runtime config object, including environment variable `testEnv`, which is accessible:\r\n```js\r\n{\r\n app: { baseURL: '/', buildAssetsDir: '/_nuxt/', cdnURL: '' },\r\n nitro: { envPrefix: 'NUXT_', routeRules: { '/__nuxt_error': [Object] } },\r\n public: {},\r\n testEnv: '12345678asdf'\r\n}\r\n```\r\n4. quit the dev process and run `pnpm build`, then `pnpm start`\r\n5. open `localhost:3000`, and then console will print runtime config, and value of environment variable `testEnv` is missing:\r\n```js\r\n{\r\n app: { baseURL: '/', buildAssetsDir: '/_nuxt/', cdnURL: '' },\r\n nitro: {\r\n envPrefix: 'NUXT_',\r\n routeRules: { '/__nuxt_error': [Object], '/_nuxt/**': [Object] }\r\n },\r\n public: {},\r\n testEnv: ''\r\n}\r\n```\r\n\r\n### Describe the bug\r\n\r\nAccording to [the doc](https://nuxt.com/docs/guide/going-further/runtime-config#environment-variables), runtime config values are automatically replaced by matching environment variables at runtime. This works in development mode, but different behavior happens when I build and run the output with `.env` file sourced. \r\n\r\nAccording to [the env doc](https://nuxt.com/docs/guide/directory-structure/env), after server is built, environment variables should be set before server running, one recommended way is to source env file using `source .env && node .output/server/index.mjs`. \r\n\r\nHowever, such script cannot successfully inject environment variables declared in `.env`. \r\n\r\nIs there something I missed?\r\n\r\n### Additional context\r\n\r\nA temporary workaround I'm using now is manually assign environment variables to runtimeConfig in `nuxt.config.ts`: \r\n\r\n```\r\n runtimeConfig: {\r\n testEnv: process.env.NUXT_TEST_ENV\r\n }\r\n```\r\n\r\n### Logs\r\n\r\n_No response_",[2089,2092,2093],{"name":2090,"color":2091},"documentation","5319e7",{"name":2037,"color":2038},{"name":2094,"color":2095},"3.x","29bc7f",22331,"Cannot access environment variables in `useRuntimeConfig` using `source .env && node server.mjs`","2023-07-30T09:16:47Z","https://github.com/nuxt/nuxt/issues/22331",0.72128886,{"description":2102,"labels":2103,"number":2108,"owner":1991,"repository":1991,"state":2058,"title":2109,"updated_at":2110,"url":2111,"score":2112},"### Environment\n\n- Operating System: `Darwin`\r\n- Node Version: `v20.10.0`\r\n- Nuxt Version: `3.10.3`\r\n- CLI Version: `3.10.1`\r\n- Nitro Version: `2.8.1`\r\n- Package Manager: `pnpm@8.14.1`\r\n- Builder: `-`\r\n- User Config: `devtools`, `runtimeConfig`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-starter-6r61tu\r\n\r\n- in normal dev-mode everything works fine, the value from the .env file is printed\r\n- if you build the app with `cloudflare-pages` preset and then run it via `npx wrangler pages dev dist/ --port=3000`, you'll see that the cli says that the variables from `.dev.vars` are picked up, but they aren't used as the app prints the default value from runtime config\n\n### Describe the bug\n\nWhen building the app with `cloudflare-pages` preset, the env-variables for runtime config are not used in the app correctly.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n✨ Compiled Worker successfully\r\n ⛅️ wrangler 3.29.0\r\n-------------------\r\nUsing vars defined in .dev.vars\r\nYour worker has access to the following bindings:\r\n- Vars:\r\n - NUXT_PUBLIC_TEST_VALUE: \"(hidden)\"\r\n```\n```\n",[2104,2105,2106,2107],{"name":2094,"color":2095},{"name":1985,"color":1986},{"name":2041,"color":2042},{"name":2044,"color":2045},25925,"Runtime config environment variables do not override default values with cloudflare-pages preset","2024-03-04T11:37:26Z","https://github.com/nuxt/nuxt/issues/25925",0.73477334,["Reactive",2114],{},["Set"],["ShallowReactive",2117],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"TQBy_5soHjYozHQF97vz-54S7A9mAbm8k7j7tswxHFg":-1},"/nuxt/ui/3291"]