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.

TypeScript: error TS6133: 'tw' is declared but its value is never read.

See original GitHub issue

If you use tw just as an element prop, TypeScript doesn’t think it’s being used if I have noUnusedLocals: true in my tsconfig.json.

I could disable this warning in TS, or // @ts-ignore, but is there a better way of dealing with it?

Issue Analytics

State:
Created 3 years ago
Reactions:2
Comments:10 (7 by maintainers)

Top GitHub Comments

2reactions

danielkczcommented, May 7, 2020

My solution is to get rid of noUnusedLocals and use ESLint instead for tracking unused variables which can be configured for exceptions.

rules:
  '@typescript-eslint/no-unused-vars': ['warn', { varsIgnorePattern: 'tw|css' }]

1reaction

danielkczcommented, May 18, 2020

It is not recommended to remove noUnusedLocals option in TypeScript as the main usage of it is not to allow building if unused local is found.

Relying on Eslint won’t get that done.

It will work if your CI runs tests & lint before building which is the pretty usual pattern.

Nonetheless, an unused variable is not a reason why build should fail. With tree shaking in place, it will be removed anyway from the resulting bundle. Not that it would matter in case of twin.macro at all since it doesn’t have any runtime footprint 😃

Ultimately, #70 will be a better solution, of course. Just pointing out that my workaround is pretty good for now.