Carlos Esteban Lopez Jaramillo

Hi @jerelmiller, by `wondering` I would like to see a full example project with the SchemaLink & the app router in use, if it can effectively skip the API request...

I see we have a new `ApolloNextAppProvider`, still have yet to see `SchemaLink` mentioned anywhere in the README. Also, the `neo4j-graphql` example I mentioned in the description was deleted, shame,...

May have something to do with this bug, I can't route using paths because the path ends up ignored by the JS driver: https://github.com/neo4j/neo4j-javascript-driver/issues/1091

After trying a lot of things in other issues, like updating Node and updating the TSConfig in multiple ways for the `module` and `target` properties, I couldn't get it to...

@elkay You mean you changed the dependency `package.json` or your projects one? I was in the middle of an interview test so I had no luxury time to try more...

Well that leaves me without much of a solution given I'm using an Nx monorepo, it would probably affect all my apps no?

I got an idea specifically for Nx monorepos, turns out the build process is different if you generate a new app with node+express preset, than if you use the `@nx/express`...

@m1daz Wait what? why are you using Next and Express together? you usually pick 1 or the other since you can also do APIs in Next, do you mean 2...

Ok so as far as I understand CommonJS modules cannot import ESM, but ESM can import CommonJS, which is why adding `"type": "module"` which turns your non-extension defined modules (`ts`...

To clarify, what I put above is a workaround, not a proper fix, I see `@auth/express` has an `exports` field so I would guess it's following the guidelines for modern...