-
Notifications
You must be signed in to change notification settings - Fork 18
Set up import parsers so import/* rules work in typescript #197
Conversation
It turns out you need some extra config in order for some of the import checking rules to do their thing with TypeScript.
b8add35
to
afd3c27
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is great, good find. I think we still need some more configuration for our default project setups (resolving packages/*
and so forth), but this is a great start.
Adding I just tried adding |
Oh, awesome. A great start and finish then :P |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice work!
will this be a point release? should i try and roll it into https://github.com/Shopify/sewing-kit/pull/1038 ? |
This feels like a minor release (26.1.0) - technically it's fixing a config that /should/ have always been working, but it's going to introduce a lot of new linting messages. Rolling it into the new SK release sounds like a good plan. |
Oh it's also worth pointing out that this also currently doesn't work for JS files when using the babel-eslint parser due to a bug upstream. but there's an open PR to fix that |
It turns out you need some extra config in order for some of the import
checking rules to do their thing with TypeScript.
To tophat:
yarn add --dev eslint-import-resolver-typescript