Path problem including graphql files

Hello,

When I try to simply import a gql file, I always get the error :

error: bundling failed: Error: Cannot find module './myQuery.gql'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:580:15)
    at Function.resolve (internal/modules/cjs/helpers.js:30:19)
    at PluginPass.exit (C:\Project\importGQL\node_modules\babel-plugin-import-graphql\build\index.js:72:66)
    at newFn (C:\Project\importGQL\node_modules\@babel\traverse\lib\visitors.js:193:21)
    at NodePath._call (C:\Project\importGQL\node_modules\@babel\traverse\lib\path\context.js:53:20)
    at NodePath.call (C:\Project\importGQL\node_modules\@babel\traverse\lib\path\context.js:40:17)
    at NodePath.visit (C:\Project\importGQL\node_modules\@babel\traverse\lib\path\context.js:97:8)
    at TraversalContext.visitQueue (C:\Project\importGQL\node_modules\@babel\traverse\lib\context.js:118:16)
    at TraversalContext.visitMultiple (C:\Project\importGQL\node_modules\@babel\traverse\lib\context.js:85:17)

My code :

import Query from "./myQuery.gql";

The only way to make it working is to use the absolute path to the graphql path. ex : C:\Project\importGQL\components\myQuery.gql

Reproduction

I reproduce it on a simple project : https://github.com/Kisepro/importGQLBug.git

Investigation

When I check in babel-plugin-import-graphql\build\index.js, it calls the function with the following parameters :

• importPath ./Query.gql

• jsFilename C:\Project\importGQL\node_modules\react-native\scripts\components\ComponentA.js

The ComponentA.js file is obviously not in under node_modules

[stephencaldwell]

I don’t believe this qualifes as a problem with this plugin but instead is a quirk of react-native/metro. You need to configure metro to include the .graphql/.gql files when it’s bundling up files to send to babel.

In metro.config.js you’ll need to add the following:

module.exports = { 
   ...
 resolver: {
    assetExts: ['graphql', 'gql']
  }
};

[detrohutt]

After seeing this mentioned in #48 as well, I believe @stephencaldwell is correct. I’m closing this. If anyone experiences this issue with the settings mentioned above, let me know and I’ll reopen.