Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

require-import fragment does not support module paths #2180

Open
jksmithing opened this issue Feb 15, 2024 · 0 comments · May be fixed by #2181
Open

require-import fragment does not support module paths #2180

jksmithing opened this issue Feb 15, 2024 · 0 comments · May be fixed by #2181

Comments

@jksmithing
Copy link

Is your feature request related to a problem? Please describe.

In monorepos it's a common pattern to organize code across multiple internal packages.

Currently it's not possible to import a GQL fragment using a module path to an internal package, e.g. #import '@company/graphql/FooFields.gql'.

Describe the solution you'd like

I'd like to add support for module paths.

Describe alternatives you've considered

Relative paths: These work today but are not ergonomic or consistent with best practices for imports in JS/TS files. Further, we cannot utilize the mappings provided by the package.json exports field.

Additional context

N/A

@jksmithing jksmithing linked a pull request Feb 15, 2024 that will close this issue
9 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant