Marco Wettstein

this used to work with meteor 1.6.1 but is now broken with meteor 1.7

what about the new api mentioned here? https://github.com/meteor/meteor/blob/30df020c9ddf8c62d2c49d7829cfe661aa9699eb/History.md

> @leungandrew Does this solution still work on `^0.26.0-next.14` I have the exact implementation and receiving error `nexus:server:graphql Missing multipart field ‘operations’` i also got this error. Could you solve...

@bkrausz no, i just use nexus inside nextjs (according to the example), maybe the middleware is missing in that setup?

how nexus uses apollo server in case of nextjs? It uses ``` const app = require("nexus").default; export default app.server.handlers.graphql; ``` so this handler is responsible for graphql and forwards it...

update: setting ``` export const config = { api: { bodyParser: false } } ``` on the nextjs api route does not trigger the `Missing multipart field ‘operations’`-error, but the...

ok i found the problems: first, this is required i the api rout: ``` export const config = { api: { bodyParser: false } } ``` second, the uploadMiddleware is...

yes, i always land on that old page. It could potentionally also confuse and scare newcomers.

Hi @srbdev I think you have to add the babel-root-slash-import plugin to your babelrc: ``` { "presets": ["es2015", "stage-2", "react"], "plugins": ["react-require", "babel-root-slash-import", ....] } ``` then, it can resolve...

I think you just need to customize the containers, which is already possible with mantra-cli. You can specify your container-template that uses redux or apollo. Maybe check if you need...