Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[0.18.x] generated `.tsx` files imports `types.tsx` from a wrong path

See original GitHub issue

Hi here,

I use graphql-let (an awesome tool by the way!) on an open-source project. The 0.17 version broke the Typescript Type Checking. The error says :

Type error: 'typeDefs' only refers to a type, but is being used as a value here.

I import the schema for a graphql server.

Here is the PR opened by dependabot. https://github.com/guillaumeLamanda/twitter-follow2list/pull/109

I read the changelog of the 0.17, but I am not sure if I’m concerned by the changes needed.

This project use NextJS 10.1

Issue Analytics

State:
Created 2 years ago
Reactions:1
Comments:6 (3 by maintainers)

Top GitHub Comments

1reaction

guillaumeLamandacommented, May 25, 2021

I totally missed it, my bad! It seems perfect 👍

0reactions

piglovesyoucommented, May 25, 2021

Thank you for the guide! The v0.18.0 release note also has a migration guide, happy if you take a look.

Top Results From Across the Web

Documentation - Module Resolution

Module resolution is the process the compiler uses to figure out what an import refers to. Consider an import statement like import {...

Auto import always suggests incorrect file type (tsx

When I import a React component in vscode, vscode suggests me to import the file xxx/index.js , but the source file has a...

Webstorm not resolving module imports using typescript ...

Hello there! I am using Webstorm 2019.3.4. I found it very problematic to configure "paths" option so that IDE does not show me...

ts-loader | Yarn - Package Manager

TypeScript loader for webpack. npm version build and test Downloads node version code style: prettier. ts-loader. This is the TypeScript loader for webpack....

javascript - Jest test fails with Unexpected token, expected ";"

The test file extension should be recognised as a file that uses the React syntax (eg. tsx ), and React should be defined...