Discussion: Export-based API instead of builder.xyz

[Max Stoiber]

I have the strong opinion that this is the much better API, as it more closely aligns with the common frontend mental model that Next.js's routes & API routes have:

export const LaunchNode = node({…}) # See #3 and #4

export const queries: Queries = (t) => ({
  …
})

export const mutations: Mutations = (t) => ({
  …
})

[Max Stoiber]

Jovi in Slack:

Export API can't work without Next helping us 😅 and honestly pothos bugs out very frequently with it

I mean, my point more so being that without us having a good way to plug into Next and create our own compiler we won't be able to use the exports. I had it working in the normal fuse CLI but for Next where everything is running independent of you that won't do. For exports you need a metaprocess that compiles on the fly and calls the pothos builder with the attained value

[Jovi De Croock]

Closing this out for now as we settled on our middle ground solution