oooplz

> This can be achieved with namespace importing > > ```ts > import * as NexusPrisma from 'nexus-prisma' > > const User = objectType(NexusPrisma.User) > ``` > > I am...

> Please open an issue on Nexus about how to support this. I think it would be less confusing if the building blocks for this were made in core. Otherwise...

```ts import { IntlifyModuleOptions } from '@intlify/nuxt3'; declare module '@nuxt/schema' { export interface NuxtConfig { intlify?: IntlifyModuleOptions; } } ```

~~Why do the feat still no be merged to master branch.~~ My apologies for the ask. I am using ``vue-next`` to develop a lib. And i have one component should...

liunx 设置环境变量 ``` export NODE_OPTIONS=--max-old-space-size=32768 ```

package.json ``` "build": "cross-env NODE_ENV=production NODE_OPTIONS=--max-old-space-size=32768 vite build && esno ./build/script/postBuild.ts", ```

Yes, it's make more sense.

Hi. The issue still open. And i'm useing ``vite2`` and `Vue3.0`. I had found a ``rollup`` plugin that works for me. [@rollup/plugin-graphql](https://github.com/rollup/plugins/tree/master/packages/graphql)

if you woking with ``Vite`` ```ts import vue from '@vitejs/plugin-vue'; import graphql from '@rollup/plugin-graphql'; import { resolve } from 'path'; export default (): Record => { return { plugins: [vue(),...

> I tried the rollup plugin above on a fresh installation of Nuxt Bridge with vite turned on and got the following: ``` npm install graphql or yarn add graphql...