Kevin Marrec

And my `token` property missing might be the issue mentionned in #119 and should be fixed by #140. I'm kind of confused as PR's are merged but not mentioning issues...

I agree with @sapkra that definining the `AuthPayload` in `types.ts` and refers to it in `graphqlgen.yml` to have finally `import { AuthPayload } from "../types";` in `generated/graphqlgen.ts` could be replaced...

@schickling Issue was referenced in #237 but I didn't clearly understand how is it related, and is there any thoughts about what me and @sapkra wrote ?

@schickling Any updates on this ? Without automatically generating these models It's gonna be a pain for big projects to maintain both the Schema `schema.graphql` AND their respectives model definitions...

@schickling Any thoughts ?

Hi @jscottsf , ~~I think that in your case it's totally fine having the module in `dependencies`, as you indeed need your production Docker container to install the dependency to...

@jscottsf See this new option (if you upgrade the module to **1.2.0**) : https://github.com/nuxt-community/vuetify-module#optionspath Defining options like this will make the Vuetify colors will be bundled by Webpack at build...

@morficus You're right but it's more likely `create-nuxt-app` that needs to be updated, could you please an issue there ? Thanks.

@morficus Well AFAIK, `^1.0.0` in `package.json` should install `1.x.x` so it should install last version for fresh projects if i'm right.

Using `optionsPath` is the way to go to not have Vuetify needed in `dependencies`. If you keep Vuetify imports in `nuxt.config.js` it's obvious you need Vuetify at runtime (so in...