Glenn Reyes

Yeah, I think that'd would work for me. A PR would be awesome @gomesalexandre! 🙌

Hey! What are you trying to achieve by this?

Thanks @bernharduw! This seems related to https://github.com/prisma/graphql-import/issues/267#issuecomment-462808292. Any bugfixes on this highly appreciated.

I am not sure either. Can you please send a minimal codesandbox sample that reproduces this? Thanks!

Hi @glenndevenish! I only have limited time and can't look into private codebases atm. If you're still seeing the error please create an example with CodeSandbox so that also other...

@zvictor Thanks for filing this! Maybe worth to put instructions about `nohoist` to README.md? WDYT?

You can use import definitions in GraphQL SDL to achieve your structure: `schema.graphql` ```graphql # import Post from "posts.graphql" type Query { posts: [Post] } ```

Yep I would say so. Add your `.flowconfig` and: ```js // babel.config.js module.exports = { presets: ['graphpack/babel', '@babel/preset-flow'], }; ```

Oh good point! Well, since there's not much in `graphpack/babel`, you could just use what's in there and remove the TS preset: ```js // babel.config.js module.exports = { plugins: ['@babel/plugin-syntax-dynamic-import'],...

Ideally, Graphpack can detect whether there's a `.flowconfig` or `tsconfig.json` and adds babel presets accordingly. This way we wouldn't have to deal with babel config at all.