\nI'd really appreciate it if the team considers a more flexible and intuitive API.\n\n### Additional information\n\n- [ ] 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).",[2014,2015],{"name":1985,"color":1986},{"name":2016,"color":2017},"pending triage","E99695",29275,"Better API for Auto Imports Customization","2024-10-08T08:40:01Z","https://github.com/nuxt/nuxt/issues/29275",0.7339197,{"description":2024,"labels":2025,"number":2030,"owner":1991,"repository":1991,"state":1992,"title":2031,"updated_at":2032,"url":2033,"score":2034},"### Describe the feature\r\n\r\nI'm reaching out with a suggestion that might enhance the documentation, particularly for those looking to disable code splitting. We recently came across a method to inline dynamic imports through the Rollup configuration, effectively disabling code splitting. This was discovered in a ViteJS discussion ([Reference here](https://github.com/vitejs/vite/discussions/13925#discussioncomment-7709077)):\r\n\r\n```typescript\r\nbuild: {\r\n rollupOptions: {\r\n output: {\r\n inlineDynamicImports: true\r\n }\r\n }\r\n}\r\n```\r\n\r\nComing forth to this solution took us a considerable amount of time. A search in the Nuxt documentation for \"code splitting\" yielded few results. Including this information in the Nuxt documentation could significantly improve the developer experience, making this knowledge more readily accessible.\r\n\r\nThere are practical scenarios, such as ensuring seamless access for mobile users with unstable internet connections, where disabling code splitting can be beneficial. Although code splitting with dynamic imports provides some fantastic optimizations, ensuring that the entire page content is downloaded and ready on the first load can be crucial in these situations. I do understand, that there are [ways to handle these errors](https://nuxt.com/docs/getting-started/error-handling#errors-with-js-chunks), but unfortunately, as the application grows, it just creates too much room for error.\r\n\r\nI must admit my understanding of the implications of setting `inlineDynamicImports` to `true` is not comprehensive. One of our applications, deployed as a static single-page app, benefits from this setting, but I'm uncertain about its effects in other build configurations. I would greatly appreciate if someone could provide further insight on this.\r\n\r\nAdditionally, I would like your opinion on the best section within the Nuxt documentation to include this information, ensuring it's easily found by those who need it.\r\n\r\nLooking forward to your thoughts and guidance on this matter.\r\n\r\n### Additional information\r\n\r\n- [X] Would you be willing to help implement this feature?\r\n- [ ] Could this feature be implemented as a module?\r\n\r\n### Final checks\r\n\r\n- [X] Read the [contribution guide](https://nuxt.com/docs/community/contribution).\r\n- [X] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[2026,2029],{"name":2027,"color":2028},"documentation","5319e7",{"name":1988,"color":1989},24539,"Docs: Suggestion for documenting disabling code splitting","2024-06-30T11:06:44Z","https://github.com/nuxt/nuxt/issues/24539",0.7399,{"description":2036,"labels":2037,"number":2040,"owner":1991,"repository":1991,"state":1992,"title":2041,"updated_at":2042,"url":2043,"score":2044},"Nuxt has full support for payload extraction in production, when run with `nuxi generate` or `nuxi build --prerender` but there's no way to experience this in development (or identify possible bugs).\n\nIt would be good to support payload extraction when explicitly enabled by setting `nitro.static` to `true` (or by enabling `experimental.payloadExtraction` directly).\n\nWe might also consider moving `payloadExtraction` out of experimental namespace and/or renaming it.",[2038,2039],{"name":1985,"color":1986},{"name":2004,"color":2005},30679,"payload extraction support in development mode","2025-01-21T09:09:47Z","https://github.com/nuxt/nuxt/issues/30679",0.7409015,{"labels":2046,"number":2047,"owner":1991,"repository":1991,"state":2048,"title":2049,"updated_at":2050,"url":2051,"score":2052},[],13614,"closed","Migrating to nitropack","2023-01-19T17:02:40Z","https://github.com/nuxt/nuxt/issues/13614",0.7013588,{"labels":2054,"number":2062,"owner":1991,"repository":1991,"state":2048,"title":2049,"updated_at":2063,"url":2064,"score":2065},[2055,2056,2059],{"name":1988,"color":1989},{"name":2057,"color":2058},"3.x","29bc7f",{"name":2060,"color":2061},"nitro","bfd4f2",13360,"2023-01-19T17:03:08Z","https://github.com/nuxt/nuxt/issues/13360",0.7133065,{"description":2067,"labels":2068,"number":2072,"owner":1991,"repository":1991,"state":2048,"title":2073,"updated_at":2074,"url":2075,"score":2076},"### Describe the feature\r\n\r\nHello,\r\n\r\nActually, there is different import meta. One of them is for prerendering. But there is nothing about static when nuxt is generating the website. Pre-render key is not enough specific when site is static since there is a payload generated. \r\n\r\nSee https://github.com/nuxt/content/issues/2533\r\n\r\nhttps://nuxt.com/docs/api/advanced/import-meta#runtime-app-properties\r\n\r\n### Additional information\r\n\r\n- [ ] Would you be willing to help implement this feature?\r\n- [ ] Could this feature be implemented as a module?\r\n\r\n### Final checks\r\n\r\n- [X] Read the [contribution guide](https://nuxt.com/docs/community/contribution).\r\n- [X] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[2069,2070,2071],{"name":1985,"color":1986},{"name":1988,"color":1989},{"name":2057,"color":2058},25566,"Add import meta for static rendering","2024-05-10T09:41:34Z","https://github.com/nuxt/nuxt/issues/25566",0.7154172,{"description":2078,"labels":2079,"number":2082,"owner":1991,"repository":1991,"state":2048,"title":2083,"updated_at":2084,"url":2085,"score":2086},"### Environment\n\n- Operating System: `Darwin`\r\n- Node Version: `v18.16.0`\r\n- Nuxt Version: `3.6.5`\r\n- CLI Version: `3.9.0`\r\n- Nitro Version: `2.6.3`\r\n- Package Manager: `yarn@1.22.19`\r\n- Builder: `-`\r\n- User Config: `srcDir`, `authoringTools`, `typescript`, `app`, `runtimeConfig`, `graphql-client`, `modules`, `image`, `sentry`, `tailwindcss`, `vite`, `build`, `experimental`\r\n- Runtime Modules: `nuxt-lodash@^2.5.0`, `@nuxtjs/tailwindcss@^6.8.0`, `@vueuse/nuxt@10.5.0`, `nuxt-graphql-client@^0.2.29`, `nuxt-icon@^0.4.2`, `@nuxt/image-edge@1.0.0-rc.3-28294248.a578636`\r\n- Build Modules: `-`\r\n\n\n### Reproduction\n\n```js\r\n// my-nuxt-app/modules/my-module/index.ts\r\n\r\nconsole.log({\r\n url: import.meta.url,\r\n nitro: import.meta.nitro,\r\n build: import.meta.build,\r\n client: import.meta.client,\r\n server: import.meta.server,\r\n});\r\n```\r\n\r\nAll accesses of `import.meta` except for `url` cause execution failures when running/building the project.\n\n### Describe the bug\n\nWhen `import.meta.url` is available, then `import.meta` should be safe to access with arbitrary (but compile-time known) keys. For example `import.meta.server`.\r\n\r\nThis will make code that is nuxt-aware (e.g. using the `client` and `server` properties to determine where code is being ran) safe to use within a nuxt module setup function.\r\n\n\n### Additional context\n\nSince `import.meta.url` works, I suspect there is some sort of define-replace step before the module code is being executed. I first was going to open this issue on nitro, but I quickly found that using this kind of code in a nitro route works fine.\r\n\r\nLooking at the stack trace it points to a `@nuxt/kit` function `loadNuxtModuleInstance` which uses `requireModule` (also from kit) to load the nuxt module.\n\n### Logs\n\n```shell-script\n\u003Cpre>\r\nERROR Cannot start nuxt: Cannot use 'import.meta' outside a module 10:49:45 AM\r\n10:49:44 AM\r\nclient: import.meta.client\r\n^^^^\r\n\r\nSyntaxError: Cannot use 'import.meta' outside a module\r\n at new Script (node:vm:100:7)\r\n at createScript (node:vm:259:10)\r\n at Object.runInThisContext (node:vm:307:10)\r\n at evalModule (.../node_modules/jiti/dist/jiti.js:1:255425)\r\n at jiti (.../node_modules/jiti/dist/jiti.js:1:253542)\r\n at requireModule (.../node_modules/nuxt/node_modules/@nuxt/kit/dist/index.mjs:2244:26)\r\n at loadNuxtModuleInstance (.../node_modules/nuxt/node_modules/@nuxt/kit/dist/index.mjs:2435:90)\r\n at async installModule (.../node_modules/nuxt/node_modules/@nuxt/kit/dist/index.mjs:2408:47)\r\n at async initNuxt (.../node_modules/nuxt/dist/index.mjs:3238:7)\r\n at async load (.../node_modules/nuxi/dist/chunks/dev.mjs:205:9)\r\n at async Object.invoke (.../node_modules/nuxi/dist/chunks/dev.mjs:249:5)\r\n at async _main (.../node_modules/nuxi/dist/cli.mjs:49:20)\r\n\r\n\u003C/pre>\n```\n",[2080,2081],{"name":2057,"color":2058},{"name":2016,"color":2017},24185,"Usage of `import.meta` in nuxt modules easily breaks","2023-11-29T09:37:16Z","https://github.com/nuxt/nuxt/issues/24185",0.7188186,{"description":2088,"labels":2089,"number":2098,"owner":1991,"repository":1991,"state":2048,"title":2099,"updated_at":2100,"url":2101,"score":2102},"### Environment\n\nNuxt project info: 04:18:43\r\n\r\n------------------------------\r\n- Operating System: `Windows_NT`\r\n- Node Version: `v16.12.0`\r\n- Nuxt Version: `3.0.0`\r\n- Nitro Version: `1.0.0`\r\n- Package Manager: `yarn@1.22.10`\r\n- Builder: `vite`\r\n- User Config: `ssr`, `pages`, `app`, `css`, `plugins`, `modules`, `runtimeConfig`, `devServer`, `tailwindcss`, `postcss`, `vite`\r\n- Runtime Modules: `@pinia/nuxt@0.4.6`, `@nuxtjs/tailwindcss@6.1.3`, `@funken-studio/sitemap-nuxt-3@4.0.4`, `nuxt-swiper@0.1.6`\r\n- Build Modules: `-`\r\n------------------------------\n\n### Reproduction\n\nI don't think a reproducer is needed here.\n\n### Describe the bug\n\nThe `ViteImportMeta` type in the following file appears to be derived from an older version of Vite.\r\n\r\nhttps://github.com/nuxt/framework/blob/a9df4b75d622b21c1c0cc6f3e601722e42714b90/packages/schema/src/types/global/vite.ts#L34\r\n\r\nCurrent versions of vite have a generic that differs the return type based on whether eager is true or false.\r\n\r\nhttps://github.com/vitejs/vite/blob/main/packages/vite/types/importMeta.d.ts\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2090,2093,2094,2097],{"name":2091,"color":2092},"good first issue","fbca04",{"name":2057,"color":2058},{"name":2095,"color":2096},"bug","d73a4a",{"name":2004,"color":2005},15645,"ViteImportMeta `import.meta.glob` does not change types for the `eager: true` flag","2023-03-03T10:20:17Z","https://github.com/nuxt/nuxt/issues/15645",0.7215332,["Reactive",2104],{},["Set"],["ShallowReactive",2107],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"vVcXLhBQ7RB1-GvY5tqU2ZrFAf736vnMR5v3HS2V8-o":-1},"/nuxt/nuxt/21862"]