Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@shopify/[email protected]
Major Changes
#477
fecfb7b
Thanks @BPScott! - Useeslint-plugin-import-x
instead ofeslint-plugin-import
. This is faster, while retaing the same features - notably it avoids a large speed degredation when using the no-cycle rule witheslint-plugin-import
.Rule names are the same in
eslint-plugin-import-x
, but the plugin name isimport-x
instead ofimport
. You will need to change all rules and settings that define or referenceimport/THING
toimport-x/THING
. e.g. the ruleimport/no-cycle
becomesimport-x/no-cycle
and the settingimport/parsers
becomesimport-x/parsers
. You should check theeslint-plugin-import-x
documentation to see if the settings for any rules differ from theireslint-plugin-import
counterparts.Configuration of resolvers has switched from using
import/resolver
toimport-x/resolver-next
. Any configuration of resolvers shuld be done using the new setting per https://www.npmjs.com/package/eslint-plugin-import-x#resolvers. We now configureeslint-import-resolver-typescript
as the default resolver for typescript files so you no longer need to configure a resolver unless you need to override the default options.